yashsingh1/xdaforums huggingface dataset:
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] Dev!n:
oh ok thanks, downgrade to 12.1 :)
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] Alias X:
Nice, nice, nice! Finally an alternative to CM13. But I guess it has the same bugs as CM? I wish I could avoid its YouTube-Bug...
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] Abrewanana:
Pls can you develop for the v410 also?
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] Guest1000:
can you make one for the lg g pad v410 please
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] amdev0101:
RR N is up http://xdaforums.com/g-pad-10/development/rom-resurrection-remix-os-5-8-0-t3515005
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] kream21:
I didn't make this, but here is nougat 7.0 for the LG G Pad 7.0! Adam Myczkowski is tagged in the article. http://www.cyanogenmods.org/forums/topic/lg-gpad-7-0-wifi-cm14-cyanogenmod-14-nougat-7-0-rom/
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] oldschool63:
I just installed RR 5.7.4 on my v400 - everything looks great but gps does not seem to work. Is this a known bug - or in other words, will there be another (newer) Marshmallow build for the v400? I think that CM fixed the gps sometime at the end of Nov 2016. RR 5.7.4 was built before that.
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] amdev0101:
MM development has been dropped for N. Gps seems to br working on mine but I never actually fully tested it. I will check sometime on N builds and let you know.
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] oldschool63:
Thanks Adam. I actually had CM13 on my v400 before I switched to RR and under CM13 my gps worked. But the CM build was from the beginning of Dec 2016. Under RR 5.7.4 my gps is not working at all - no matter what I do. Gps activity is shown in the status bar for a few seconds right after power-on is completed but after that there is no further gps activity anymore. All diagnose apps I have say it is not working.

I might try to rebuild RR 5.7.4 based on the last available CM13 sources. We'll see.
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] oldschool63:
Adam,

OK, did some tests. Used the last published CM13-NIGHTLY (12/19/16) and current "nano" GApps. Installed after full wipe and then installed GPS Status from Play store. GPS is set to "device only" and works good. No problems at all.

Same test with RR-5.7.4 (09/21/16), same environment (just nano GApps & GPS Status): GPS does not work at all. It's not that it cannot get a lock, the GPS icon does not even show up in the status bar. It shows up for a few seconds after a power-on event but that's it.

So yes, it can easily be reproduced. If you want to have a copy of the last CM13 Nightly, let me know and I'll set it up for you.

I tried to rebuild RR-5.7.4 based on the last published CM13 sources, pretty much standard procedure. I did use the the device files from CM Github too (breakfast v400). I had to exclude gello from the build (because of build errors) and the build went through with the final success message. However, the build does not work. The v400 is stuck at the boot screen. I don't know what I may have done wrong but I am sort of a newcomer to building Android, so just maybe something stupid. I don't know.

If you could take a look at the problem so that we could get a "final" RR-5.7.4 build with working GPS that would be fabulous. Or, if you could drop me some hints about what I might have done wrong rebuilding RR I will gladly try again.

BTW, I also have RR-5.7.4 running on my Samsung Note 8.0 (n5110) and GPS is working great on that device. The Samsung build, however, is dated 12/26/16.

Let me know if I can be of any more help.

Thanks,

Markus
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] amdev0101:
You probably didn't sync lg blobs from TheMuppets github and that's the reason it does not boot, I will rebuild it soon and test.
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] amdev0101:
GPS icon is showing up in the new build but GPS signal cannot be found. I would recommend moving onto Nougat. I am not going to attempt fixing it since Nougat is more important.
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] oldschool63:
Adam,

First of all I want to thank you for the hint about the missing LG blobs from TheMuppets github. I was able to build my own RR-5.7.4 based on the "current" CM13 sources. I experienced the same problem you had: the GPS icon is showing up but it still does not work. So, after checking out the usual suspects in case of GPS problems, I realized that this RR build does not a /etc/gps.conf at all (this also applies to the original 09/21/16 build)!

I copied the gps.conf from my Samsung Note 8.0 (RR-5.7.4) to my v400 and voilà - we now have a working GPS! :highfive:

I dirty flashed my build over the installed official RR-5.7.4 build and everything works fine. Now if you could give some more "helpful hints":

How do I officially add a gps.conf to my build?

How do I officially add a prebuilt apk (Gello) to my build (because maven can't download Gello)?

My build currently uses the CM kernel (seems to be the default). How do I get the "cake" kernel?

If I can get this sorted I would be able to publish this ROM for other v400 users who might still want to wait a little more before upgrading to Nougat.

Thanks again for helping a "ROM builder newbie" to get into business.

Markus
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] amdev0101:
I would not recommend gps config from different device - it's different hardware, vendor and firmware so might cause bugs. I see sultanxda is using config from V40010C so you can try cherrypicking this commit. About Gello I built from a server so I simply never include it (*F CM Policy*..). Cake kernel is available here originally made by Paul Keith from Candy Team but team broke ROM died and I'm updating the kernel on my own now. I'm planning on adding new features and optimisations when I finish bringing up other ROMs. To build cake kernel simply sync it build.
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] oldschool63:
Adam,

The gps.conf I have provided does not contain any information which is hardware dependent. Just some server information (NTP_SERVER, XTRA_SERVERs and SUPL_HOST and SUPL_PORT). I cannot think of any problems this might cause. The absense of this information, however, seems to leave GPS in a non working state due to a lack of useful hardcoded defaults.

Anyway, I am still trying to build another version of RR-5.7.4 using your cake kernel repository and I have failed so far. Please bear with me as I am new to the process of building Android. I have tried to modify ~/RR-5.7.4/.repo/local_manifests/roomservice.xml, replacing the project line which refers to the CM kernel with one that refers to your cake kernel repository. Then I tried "repo sync" but it fails. So I am at my wit's end on how to modify the repo configuration to integrate your cake kernel. Can you be a little more specific than "To build cake kernel simply sync it build."?
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] amdev0101:
repo sync --force-sync
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] oldschool63:
That's what I tried too. No matter if I try the simple "repo sync" or the "repo sync --force-sync" version, these are the last lines of terminal output before repo aborts:

Fetching project CyanogenMod/android_packages_wallpapers_Basic
Fetching projects: 96% (517/538) Fetching project platform/prebuilts/gcc/darwin-x86/x86/x86_64-linux-android-4.9
Fetching projects: 98% (528/538) Fetching project CyanogenMod/android_hardware_qcom_media
Fetching projects: 99% (533/538) Fetching project CyanogenMod/android_hardware_qcom_media
fatal: Couldn't find remote ref refs/heads/cm-13.0
error: Cannot fetch MyczkowskiAdam/android_kernel_lge_v4xx

error: Exited sync due to fetch errors

Like I said ... I am probably doing something wrong. Just in case, here's my roomservice.xml:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_lge_v400" path="device/lge/v400" remote="github" />
<project name="CyanogenMod/android_device_lge_v4xx-common" path="device/lge/v4xx-common" remote="github" />
<!--project name="CyanogenMod/android_kernel_lge_v4xx" path="kernel/lge/v4xx" remote="github" /-->
<project name="MyczkowskiAdam/android_kernel_lge_v4xx" path="kernel/lge/v4xx" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" />
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" />
</manifest>

Thanks again for helping me get up and running.

Markus
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] amdev0101:
After "remote" in kernel line add ' revision="c7.1" '
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] amdev0101:
Ughh my bad, revision="c6"

[MENTION=6337290]oldschool63[/MENTION]
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] oldschool63:
Adam,

Using revision="c6" did not work (repo terminated with errors again). I checked your repository by directing my web browser to it and it says there is only one branch which is named "c7.1". So I tried again using revision="c7.1" and this time repo actually went through and finished the job.

Before I go ahead building a rom ... can you please confirm that your "c7.1" branch is a kernel which is actually suited to be used with Marshmallow? If "c7.1" refers to a Nougat kernel, then where is the "c6" branch?

If you could help to clear this last confusion, then I think I'm ready to build :fingers-crossed:

Thanks,

Markus
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] amdev0101:
I forgot i deleted this branch, use c6 branch from original repo in candy devices sorry for the confusion https://github.com/CandyDevices/kernel_lge_v4xx
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] oldschool63:
Adam,

So I tried the CandyDevices Repository. repo works fine and I can start a build. Unfortunately when it comes to building the kernel the process is aborted because the kernel is not configured. Looks like the CandyDevices repository does not supply a usable default config for the kernel.

I think it's time to throw the towel. The whole point of using a kernel from a third party is to make use of the third party's experience and their conclusion to come up with a good kernel config.

It is sad when good work is basically lost because of incomplete repositories and/or missing documentation. Unless you have an idea where I can download a useful config for the v4xx cake kernel, I might have to stick with the CM13 kernel that comes with the CM13 RR is based on. I do not have the expertise to make smart decisions during the configuration process of an Android Linux kernel. I did configure a lot of desktop kernels for various x86 and x64 computers, but that's a whole different game.

One other solution might be to extract the existing kernel out of your RR-5.7.4 build (09/22/16). Can you give me a link on how to do that? I could then use that kernel image as a "prebuilt" component for my build.
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] amdev0101:
What errors are you even getting? Kernel is 100% working...
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] oldschool63:
Adam,

I have no idea what went wrong but after deleting the whole build tree and starting all over it now works. Build is successful with the Cake kernel from CandyDevices! :good: I'm now making changes to get gps.conf included in the build. Various gps.conf files are there, but no *.mk file includes them. This ROM will make a great daily driver until Nougat is ready to take over.

BTW, the Cake kernel makes quite a difference. My first build used the CM kernel but that seemed to cause crashes now and then and battery optimization also did not work right.

Thanks again for all your patience in helping me to get going.

Markus
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] amdev0101:
To include gps config u need something like this https://github.com/MyczkowskiAdam/a...aa0#diff-6e75e450e035b5e143459b2209a6fa83R117
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] oldschool63:
Thanks for the link but I had already figured it out in exactly the way it's in the commit you mentioned. That actually was the easy part ;)

I now have a good stable daily driver. The only thing which does not work (and which never ever worked in CM roms for the v400) is the recording of video. The camera is not great anyway but in my opinion that still is no reason to not make it work. I'll look into it and try to find out what's wrong - I just want to know what kind of bug can be so complicated that none of the CM developers involved with the v400 could ever figure it out.
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] fdgfgf:
Funiona no galaxy tab t113nu? ele tem as mesma carecteristicas desse tablet da lg 8gb de memoria e 1gb de ram
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] amdev0101:
English please?
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] amdev0101:
AFAIK camcorder is working, it only doesn't work on N ( But it does work on v410 this is even weirder...)
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] oldschool63:
Camcorder does not work on the v400 ever since CM12.1 - I filed bug reports years ago but nobody ever cared. So if you are saying that it does not work on "N" - well, that bug is ancient, dating back to CM12.1 ;)

It is true that the camcorder works on the v410. But it is also true that the v400 and v410 have different cameras. The v410 can handle higher resolutions. The cameras are different and I am sure that the reason for the nonworking v400 camera is that the software treats it the same way as a v410 camera. I cannot compare logs though, I only have a v400. But I would love to tackle this bug with the help of someone who owns a v410.

Markus
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] amdev0101:
Hmm I dunno, I never had problems with camcorder on M tbf, even before I started deving. But now you told that they use different cameras you pretty much told to fix it! I never had v410 so I though they both use exactly the same hardware for cameras! I had few logs and rushing through it I noticed something wrong with resolution but I didnt have time and good ideas to tackle it.. Now I know exactly what do to - update cameras and probably separate blobs. Expect this bug to be fixed in few days! :)
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] oldschool63:
Adam,

Here are the camera specs:

v400, still image: max. 2048x1536 px (3.15 Megapixel)

v400, camcorder: max. 1280x720

v410, still image: max. 2560x1600 px (4 Megapixel)

v410, camcorder: max. 1920x1080

As you can see, the v410 has a full HD camcorder while the v400 does not. However, manually setting the v400 camera app to 1280x720 does not solve the problem. Once you hit the record button, the red record indicator comes on for a few seconds, then turns itself off. No video is saved. There were many variations of this v400 bug since CM12.1, I remember a version where the recording indicator stayed on and the app pretended to record and there were versions where the app actually crashed. But it never worked correctly. I also assume that if the v400 build uses the v410 blobs that that is probably the root cause. /etc/media_profiles.xml might need tinkering too. All the while taking still images has always worked on the v400.

Markus
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] StangBear:
ir functionality

Hey can someone verify that this ROM has alll the ir blaster API, and that its full functional??

thanks for the help
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] enxx:
Hi Adam and Oldschool

Hi Adam and Oldschool, I just got this tablet LG G Pad 7.0 V400 almost for the only reason to use the IR blaster to control my TV and Cable box, downloaded a 3rd Remote app and didn't work, then did some research and I found out that the IR blaster is locked :( can't be used with 3rd party apps :( the QuickRemote app is almost useless, doesn't have my tv brand neithe cable box brand, so my question is, if I root it and install your ROMs, will the IR blaster work? because if not, I'll have to return it, thanks for your response :)
[LG G Pad 7 ROMs, Kernels, Recoveries, & Other Deve] oldschool63:
I cannot name any app that works with GPAD's ir blaster. I don't know about the specific problem, but take a look here:

https://xdaforums.com/showthread.php?t=2532249

LG's decision to “lock” the ir blaster hardware is :rolleyes: - I don't know if there is a solution for the GPAD.
[G 2014 Q&A, Help & Troubleshooting] Anumit:
Hello guys!!

I want to root my moto g 2nd generation without bricking it and with kingroot .

Please tell me the correct method
[Android Q&A, Help & Troubleshooting] arcticnights:
Hey guys,

The XDA forums recently stopped loading for me, whenever I try to load a page it does not fully load (only the top banner loads, like http://imgur.com/vIRJAvY). It worked last night, but suddenly stopped working today.

Weirdly enough, the forums work on my mobile data (on a different carrier from my home wireless), and when tethering to my mobile but not on my home wireless. They also work while using a VPN (Zenmate, from Germany apparently). However this is a temporary solution and I would like to find a more permanent one, after a number of frustrated hours trying to fix it.

I've tried switching DNS and ip bands to no avail. Also tried turning my router on and off, and different browsers. Any idea as to why? :/
[Android Q&A, Help & Troubleshooting] JarellLama:
I have the same problems. What carrier are you using? Mine is Singtel in Singapore.

---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------

And also is your phone rooted and do you have any build.prop tweaks?
[8125, K-JAM, P4300, MDA Vario General] jimscby:
hi every one.... i'm using a mda vario from uk.... recently i had problem with my mda vario where the phone signal were very weak and unstable..... my phone signal always shows "searching......" and sometimes drop call when i make a call or answering call......

and i had try to flash the radio rom from 2.19.11 to 2.61.11, 2.69.11....... but still the same problem i face.....

is it possible the problem cause by the cid??

or any suggestion for me how to solve this problem??

ipl : 2.21.0001

spl : 2.21.0001

radio : 2.19.11

os : 10.1.0.811 wwe

protocol : 4.1.13.09

extrom : faria v5.0
[8125, K-JAM, P4300, MDA Vario General] irisiris:
use wizard service tool WST ..search forums for it..check if its CID locked..if it is locked unlock it using WST.

then flash it with T-mobile ROM ruu_2.26 IPL/SPL/GSM radio

then down grade GSM radio to 2.19 UK

now u get IPL/SPL 2.26 and Radio 2.19UK

now install faria ROM

once u r done u will have a working system with no hangups or signal issues.
[8125, K-JAM, P4300, MDA Vario General] jimscby:
Fail to unlock CID

Thanks guys, i try to unlock the CID using wizard service tool....

But the tool show that the DOC write protected........
[8125, K-JAM, P4300, MDA Vario General] zabardast_1:
ipl : 2.21.0001

spl : 2.21.0001

radio : 2.19.11

os : 10.1.0.811 wwe

protocol : 4.1.13.09

extrom : faria v5.0

You cannot CID unlock your phone through WST tools. As it's a G4 DOC chip device with IPL/SPL 2.21.0001.Infact it cannot be CID unlocked at all.I'll advise you to never try to unlock your phone.But from looks of your post it's already flashed with a custom build Rom 'Faria v5.0 version',it's a wm5 version Rom.Perhaps it's already got 'HardSPL' or flashed through 'SoftSPL' method,If it's already 'HardSPL' then just download any latest wm6 custom build Rom (G4 Safe Rom) and flash,but first be sure it's got HardSPL.

However if you are interested to upgrade your phone to the latest wm6 custom build Roms,there's a procedure called "SoftSPL" & "HardSPL" to upgrade a G4 device.Read the stickies on G4 subforum to understand and do the procedure correctly.

Good luck
[8125, K-JAM, P4300, MDA Vario General] jimscby:
I bricked my pda!!!!

Guys, yesterday i try to flash the ipl/spl 2.26 to my g4 mda vario..... What had i do are:

1) i extract the ipl and spl from t-mobile 2.26 rom and pack using the nknbf tool.

2) with using the softspl tool i flash the ipl/spl 2.26 to my device and it was done....

3) after the device soft reset, it start to tri color screen and show ipl 2.26 and spl 2.21 olipro.

4) before i trying to flash the os and radio rom to my device, accidently i had remove the battery......... the nightmare start, my device not function anymore.........

dear all, could any one can teach me how i can save my device......?

how to heard from all of you soon.
[8125, K-JAM, P4300, MDA Vario General] xeno1:
When you extracted the IPL/SPL from the t-mobile ROM, and repacked them to flash to your phone, did you use the files labeled 90000000-IPL_1 and 91000000-SPL_1 or did you use the ones labeled 90000000-IPL_2 and 91000000-SPL_2? If you used the _1 versions you flashed the IPL/SPL for a G3 and may very well not be recoverable. The only thing I can suggest you try is to reflashing the entire ROM so that it attempts to flash the right version of the IPL/SPL or since you did it once already, extract and repack the _2 versions and flash them. If that doesn't work, you may have a nice shiny brick on your hands.
[8125, K-JAM, P4300, MDA Vario General] zabardast_1:
Voilla!!!

Sry to say but I very categorically tried to explain to you that you got a G4 device.you gotta be very careful with it while flashing.

Anyway ! try to get the phone into Bootloader mode (multicolor screen) by pushing and holding down the 'Camera' button and push the 'Power On' button,while keep holding down the camera button till the screen wakes up and goes into bootloader mode.if it gets into a bootloader mode,than do the procedure xeno1 has already explained in his above post.Hope it recovers.....:(
[8125, K-JAM, P4300, MDA Vario General] jimscby:
Try already.....

Guys, i hv try all the step above but..... still cant get into the bootloader.

i think i need to send my devices to repair...

anyway, thanks alot guys.
[P8lite Q&A, Help & Troubleshooting] ssuela:
So, my father's P8 Lite had some connection issues, so he decided to perform a factory reset.

So far so good, except that the play store isn't reachable directly. It's installed and updated, it shows in the app list, but it's not in the laucher, nor I can find it with the search tool. It's definetely there, because I can open it via widgets, but it's very annoying that the icon isn't there.

Is there a solution, besides trying another factory reset? I've already tried to download the apk from the web, but the issue remains.
[P8lite Q&A, Help & Troubleshooting] PCSE:
Have you tried installing a different launcher? That might resolve your problem. If it still doesn't work you could uninstall all updates to the app and see what happens.
[P8lite Q&A, Help & Troubleshooting] Aliraza70000:
I have p8 lite ALE-L21C185B160

My question is suddenly my play store cannot work

So tried solve this problem and I reset my phone ..

And I was enter my google account it says

Coultn't sign in

There was a problem to communicating with the google server

Try again later.

Any body knows how to solve this problem

Please help me..
[P8lite Q&A, Help & Troubleshooting] Lordbannakaffalatta:
on your homescreen swipe with both fingers away from each other. then you can see the hidden icons. if its not there go onto your homescreen and make a folder by dragging two icons to each other. go into that folder and hit the + sign.

after that you get a list with apps.

could you check if the play store is in there?

if not boot into recovery and try cleaning dalvik cache... (you won't lose anything)

try a factory reset?
[P8lite Q&A, Help & Troubleshooting] Aliraza70000:
I already reset my factory many time

But again problem.

Couldn't sign in

Please help me

:crying:
[P8lite Q&A, Help & Troubleshooting] Lordbannakaffalatta:
there's not much i can do... what build are you on?

mayby a stupid question but do you have internet connection?

did you ever changed your dns or something?