yashsingh1/xdaforums huggingface dataset:
[G Pad 8.3 General] EdenGottlieb:
I've followed this thread since page 1 and never missed a single message (except for the that you were talking about. Ironic, right?

Because I am following this thread it felt natural for me to write it here but I shouldn't have, I should have opened a new thread. You're right. I'm sorry.
[G Pad 8.3 General] AndroidUser00110001:
For those that want to help with the porting of ROM a good place to start would be to download and install the GPE ported ROM and then start debugging. For you GPE users you can also try to install ROM and see if you have the same issues. If so then it could be that the permissions are not being set correctly in the eupdater-script. I have gone over it many times and it appears to be correct but more eyes on it may find the problem.

So a good test would be a GPE user to flash ROM and post the results.
[G Pad 8.3 General] thoughtlesskyle:
might also need some porting but i have a stock rom (LG UI 4.2.2) zip that may answer some things in reverse on the palman same issue as before though it won't flash without some tweaking. let me know if you need it, also it would be nice to have a stock rooted rom for flashing but you've already put in more than your fair share of work
[G Pad 8.3 General] Demetris:
Warning:Do NOT flash any rom! except its own on a Gpe device as the partitions are different and you may hardbrick your tablets
[G Pad 8.3 General] thoughtlesskyle:
this is just a system dump and boot.img, even in a worse case scenario you would just need to go to recovery and restore (nothing super crazy here)

but i agree and thank you for the PSA, this whole thread should be for advanced users

and like i said it would need to be patched for it (IE updater script for said device)
[G Pad 8.3 General] Demetris:
When he said ROM he was referring to the whole 10 yards.

If he was not, i think that was needed a big explanation so people don't get it wrong like i did :rolleyes:
[G Pad 8.3 General] thoughtlesskyle:
yeah he was talking about his port rom to my knowledge, he couldn't get wifi and BT working, but if somebody with a play edition flashes it and those things work, it would lend insight to if it's something in the ROM or in one of the other paritions
[G Pad 8.3 General] AndroidUser00110001:
Do you mean flash v500 ROM on v510? One of the things i planned on doing when i have both devices on hand.

It will not hard brick your device...flashing a ROM is just wiping the system and installing a new system folder and boot.img. It will not hard brick a tablet and you can just restore your backup or flash a different ROM as @ thoughtlesskyle pointed out.

Now flashing different img files from one device to another or flashing to wrong partition will hard brick your device.

I clearly stated to flash the GPE ported ROM...I did not mean the whole ten yards and for those that have been following thread know that there is a ported flashable ROM.
[G Pad 8.3 General] thoughtlesskyle:
yeah i have the zip together likely just needs the update script adjusted for the v510 because there is no loki business
[G Pad 8.3 General] AndroidUser00110001:
Use the updater script I have in the GPE ported ROM and flash it on your device to see if all the hardware works. Should help to narrow down if it is a permission issue. I am leaning towards kernel or hardware issue but hopefully as simple as permission issue.
[G Pad 8.3 General] sga999:
AndroidUser (and thoughtlesskyle and demetris), you may have already done this experiment, and if so, sorry to mention it. But I thought I'd try putting the GPE bluetooth apk onto the V500 and see what happened. It seems to be working fine, but let me describe how I did it, which wasn't as straightforward as I had hoped.

In ES File Explorer, I set Root Explorer ON and both / and /system to RW. In /system/app, I was able to rename bluetooth.apk and bluetooth.odex (with prefix bluetoothok). But! I was unable to copy the GPE versions of those same files (from AndroidUser's .zip) into /system/app because ES File Explorer kept getting 'permission denied'. So instead, I booted into TWRP recovery, and I used the File Manager to copy those files (after mounting /system).

Does anyone have an idea about why I couldn't do the copy with ES File Explorer? That works just fine on my other devices (like Nexus 4).

After rebooting the system, I turned on bluetooth on the V500. I thought sure it would FC, but it was fine. Then I proceeded to enable bluetooth on another device, connect them, and successfully send a file to the G Pad.

This may have not helped any of you at all. But at least it says that the bluetooth apk itself is not the problem. AndroidUser, I wonder if this does point to permissions being incorrect, as you keep thinking. I don't know about wifi and if something similar could be done to see if it will work. Unlike with bluetooth, there is no obvious apk to try to install.

Someone (or I) could also try doing the same thing with the camera and settings apk's (since security seems to be broken), though I'm not sure...the V500 has ones that start with LG, while those from the GPE .zip do not. That might complicate things a little. I'll quit talking because this may not be interesting to any of you!

EDIT: I see apk files for the V500 for camera and settings in /system/app starting with LG, but I do NOT see the corresponding ones without LG in the same folder for the GPE. In that prior paragraph, I was just assuming I'd find them there, but I don't see them.
[G Pad 8.3 General] geonahta:
Twrp has a "fix permissions" script. If it is not enough, maybe more directories can be added to it?
[G Pad 8.3 General] solnyshok:
I hope you guys succeed in converting v500 to GPE. In the meantime, I got myself iPad Mini Retina WiFi64. After only one day with it, I already hate it. Lack of filesystem, arrrgh!... But it is 4:3 and good for 10 hours of pdf reading outdoors, which were my main requirements. I will keep an eye on this thread. If conversion happens, I might just by v500 as 2nd tablet.
[G Pad 8.3 General] thlorin:
AndroidUser00110001 I have been following your work in this thread and I'm excited ? donated 10 bucks to help you kick along
[G Pad 8.3 General] woody1:
Sorry, this was off-topic, so disregard it.
[G Pad 8.3 General] AndroidUser00110001:
Thank you very much!!!

-----

Permissions are set in updater-script when ROM is installed. I even used the same setup for the permissions that comes with the OTA 4.4.2 update.

Thanks for the bluetooth suggestions and everything else.

Once I have both devices I can compare more and see if we can get this going.
[G Pad 8.3 General] sga999:
For other devices, I've always been able to set permissions with the root explorer options in ES File Explorer. Maybe that isn't enough on this device, and I do need a TWRP script, but I just don't know. Thanks for the suggestion.

EDIT: AndroidUser, when I had this problem with permissions, I was not running your rom, so your updater-script had not run. So writing to /system/app may have worked with your rom, but that's not what I was trying.
[G Pad 8.3 General] AndroidUser00110001:
You can always use an updater-script from a ROM and modify it to not install anything or wipe anything. Basically delete everything from script but for the permissions and mount options.

I am not saying it is permissions for 100% sure. Even when I flashed system.img file extracted from official tot file it still gave the same errors and when the img file is flashed it should set all proper permissions. I just tried to flash my ported GPE ROM on to GPE device but still have same issues.

I am going to dump my system files from GPE G Pad and see if any files are missing from the system dump I was using to make ported ROM.

Some of what is going doesn't make sense and I am too stubborn to just put it down and walk away from it :)
[G Pad 8.3 General] sga999:
AndroidUser, sorry to confuse things above. My permission problem while trying to copy the bluetooth apk to /system/app is completely unrelated to whether your rom port problem has anything to do with permissions.

For MY permission issue, I just used ES File Explorer, changed the root explorer options AGAIN, and I am able to copy to /system/app. But it did not "remember" that I had set the option that way in a prior boot. I don't know why ES File Explorer is working that way, but it's no longer an issue for discussion here, so sorry to bother you with it.

This is probably too convoluted to try, especially since you'll be able to do more when you have both devices in hand. But would it be "interesting" to take the V500 (which you don't have right now!), leave its kernel as is, but flash the GPE system? This is similar to what I was trying with the bluetooth experiment. If this worked, it would show that the problem is not in the GPE system. I'd try it, but I only have the GPE system that you have provided which is 4.4.2, while my V500 kernel is 4.2.2, and I'd rather have them in synch. Is the original 4.2.2 GPE kernel and system that others were first providing for you out on a server somewhere? Sorry if I'm overlooking it in this thread.

Of course, this "mix and match" combo may not function well together at all! If you think this is a silly experiment, just let me know.

EDIT: I completely understand it that you can't put this down and walk away. I'm the same way.
[G Pad 8.3 General] AndroidUser00110001:
;)

I have tried every kernel combination and everything else I can think of. I did what you suggested before I bricked my v500.

The kernel and driver modules are different between both devices and I am wondering if each model is using the two different Snapdragon 600 models.
[G Pad 8.3 General] sga999:
The OP for your rom says "ROM is rooted and has busybox". That doesn't seem to be true for me. Was that comment for some earlier version you made, but then you removed it from this version? I definitely do not have root (I ran Root Check Pro that you installed), and there is no BusyBox. Is it "safe" to get root by installing the latest SuperSU zip in recovery?

I'm asking because I think catlog is not giving much information without being rooted.
[G Pad 8.3 General] thoughtlesskyle:
yeah it would be safe to flash the superSU.zip in recovery
[G Pad 8.3 General] sga999:
I just saw this about the V500 having an 8064M. It says that the 8064T goes up to 1.9GHz. I have no idea if this information is correct, but if it is, the GPE version specs say it's also 1.7GHz, which would imply that the processors on the devices are the same.

http://www.compikusa.com/best-pcs/best-tablets/lg-pad-83-review-alternative-google-nexus-7.html

As far as the differences in drivers (MSM8930 and MSM8960), those names seem to refer to SnapDragon 400 processors. Maybe the drivers didn't need to change when the 600 came along? But it is really baffling to think the V500 has both drivers, while V510 has only the latter.

EDIT: Differing idea here. This says the V500 uses 8064T.

http://www.devicespecifications.com/en/model/734b291d
[G Pad 8.3 General] DontPushButtons:
Touch boost at the very least is not device specific; I get them on my n4 constantly..
[G Pad 8.3 General] sga999:
I'd be able to read the log more easily if they were gone. It's not that I think that fixing this will help the "big issues", like wifi and bluetooth. See another EDIT in my post about what I've learned about bluetooth..
[G Pad 8.3 General] AndroidUser00110001:
[MENTION=4541967]sga999[/MENTION] I believe the files you are missing are being created once the hardware gets turned on. That's what it looks like by digging around the .sh files. They are not part of the system dump and created once hardware is on.
[G Pad 8.3 General] Demetris:
Did anyone tried copy a300_pfp.fw from v500 to v510 /system/vendor/firmware/ ?

UpdateOn stock v500 you can find it here:

system/etc/firmware/a300_pfp.fw

When you crossflash the v510 look at system/vendor/firmware/

In the ota file v510 package i could see only a300_pm4.fw but maybe the other firmware is not there.

Just a thought because i don’t have the device :)
[G Pad 8.3 General] AndroidUser00110001:
Yeah I did not include SU this time around so just flash it...
[G Pad 8.3 General] sga999:
AndroidUser, as I mentioned in my update above, those files do not exist under /persist, even in the original V500. You may be right that they get created later, but if so, they certainly don't have the same names.

If you compare the logcat from the original to one from your ported rom (immediately after booting, I run catlog, hit pause, save the file), things look completely different about how bluetooth (and many other things) are initialized. So it seems like it's "confused about who it is". How technical is that?!

Because of all the keymaster errors (as I mentioned in my post above), I was looking at /vendor/firmware, but I had no idea what it was about. Now I see Demetris' question. Hmmm.....the ported GPE rom DOES contain /vendor/firmware and the file that Demetris mentioned. But the original V500 rom does NOT have a firmware subfolder under /vendor at all. (Or maybe it's hidden, and I didn't ask to see hidden files?). /vendor only contains etc, lib, media, and pittpatt.

Also, one thread I read mentioned that /vendor should have a symlink to /system/vendor (or maybe that should be reversed). I don't think I saw that in the updater-script. But what I read was for another device, so I have no idea if that's required here. Or maybe it is being symlink'ed in some other way because I do see both /vendor and /system/vendor in the GPE rom, and the subfolders of each seem to be identical.

---------- Post added at 10:04 AM ---------- Previous post was at 10:01 AM ----------

I did flash the supersu zip, as I mentioned in the post above. Without it, I was not able to use catlog, ES File Explorer, etc. effectively. I also installed Busybox, which was missing.
[G Pad 8.3 General] AndroidUser00110001:
[MENTION=4541967]sga999[/MENTION] The ROMs are built different and that's why some folders are different. It really just depends on how everything outside of original source was incorporated into source.

Grab the OTA 4.4.2 update and look at the updater-script there...
[G Pad 8.3 General] sga999:
Primarily, what I was trying to say was that Demetris asked about copying a file from the V500 /vendor/firmware to the V510 one. That is impossible because the V500 does not have that folder. Again, I haven't gone back to see if it was hidden, but I don't think so.

One other issue that confuses this is that I'm kind of comparing apples to oranges....I have 4.2.2 on V500 rom, 4.4.2 on V510 rom, so I can imagine there are changes in folders, etc. I asked yesterday if there was a 4.2.2 build for the GPE port out on some server somewhere...maybe someone gave it to you early, before updating to 4.4.2. That might make comparing logs a little more understandable, but that's just a guess.
[G Pad 8.3 General] AndroidUser00110001:
The file that was mentioned can be somewhere else in v500 ROM. There was no 4.2.2 for GPE. It came with 4.4 and got upgraded to 4.4.2 a few days after release.

The folder structure for modules and/or drivers can be different depending on how LG employee who is in charge of ROM setup his build environment.

I just thought of something else that I can try when I am back at home...
[G Pad 8.3 General] sga999:
The file certainly may exist elsewhere, but again, I was just trying to say that Demetris' question related to copying it from /vendor/firmware. Since that doesn't exist, he or someone who knows would have to tell me where it is in order to try that. I could search, but I think I'll wait for those more familiar with it to tell us if it exists elsewhere.

Oh, I had the wrong idea that V510 came with 4.2.2, like V500. Thanks for enlightening me.
[G Pad 8.3 General] Demetris:
I have updated my other post to clear out any confusion.

Regards

Edit

By the way as long as there is a Gplay edition of this tablet we can always update to the same kernel/system/etc without any real problems ;)

We don’t actually need gplay edition on this, the only real problem we might face is the need for a bootloader update if gplay edition in future makes it like that so we cant follow them :)

Then is a door stop for us, but there are always windows we can enter and lg might release a bootloader unlock for this device in the time being who knows....
[G Pad 8.3 General] sga999:
Demetris, I compared the a300... file from /system/etc/firmware (V500) with the one from /system/vendor/firmware (V510), and they are identical.
[G Pad 8.3 General] AndroidUser00110001:
It might be easier to hack the DLL needed with the TOT file...

But once again we need to find out if hardware is identical.

This is all too strange...like what I said before if you flash the system.img and boot.img files through recovery you still end up with the same issues. The image files linked in OP. So that should clear the permissions issue of there was one.

The GPE kernel may work enough to boot up but it may not be talking to the hardware properly.

If my desktop system was worthy enough I would through Ubuntu back on and start working on a kernel and/or AOSP build. It shouldn't be too hard getting a fully functional AOSP build. Maybe use v500 kernel source and patch it up to the latest kernel version.
[G Pad 8.3 General] sga999:
Can anyone get a logcat (with catlog or other app) for the V510? I'd like to compare what I see at initialization of the GPE ported rom with the V510 rom. I believe it has to be rooted to get catlog to give enough information. I don't know about other logger apps...they may not require root.

What I need is just the beginning events, so you have to pause the logging soon after the system boots up. If you wait "too long", the beginning of the log buffer gets overwritten. I guess there are ways to make the buffer bigger, but there's no need for that in this case. Here's what I did for the GPE ported rom. Boot, and as soon as possible, swipe lockscreen, click catlog app (it's right on the home screen where I can get to it quickly). As soon as it starts displaying events, click the pause icon at the top. Then menu, save. If someone can put that saved file on a server, that would be great (it may be 1000-2000 lines, so it's not a good idea to attach it here?). Thanks.
[G Pad 8.3 General] Demetris:
[MENTION=4218641]AndroidUser00110001[/MENTION]

I would take a different approach :)

1.Ditch v500 kernel as a whole rm -rf v500 ;)

2.Take v510 kernel/device_tree/blobs

3.Fix V510 kernel so it works with V500 and V510 device_tree and v510 blobs voilà you got your self a Gpe clone ready to rock :cool:
[G Pad 8.3 General] AndroidUser00110001:
So why not try that? LOL it takes my machine like 7 hours to compile first build :D
[G Pad 8.3 General] sga999:
AndroidUser, no one has answered about getting me the logcat I wanted from the V510. So I'm wondering if you can possibly get that for me? I realize this project may be taking a different turn due to what Demetris suggested. I think it's great that there are other ideas and possibilities. But I'm a "curious cat", and I'd really like to see the differences in the log I have from your GPE ported rom (during initialization) and one that is for the actual V510.

I don't have a powerful desktop (or laptop) and no ubuntu experience...if I did, I'd be glad to help you. But my expertise is in coding and debugging (30 years mainframe, mini/micro) and not giving up.
[G Pad 8.3 General] AndroidUser00110001:
When I restore the stock software I'll check the logcat.
[G Pad 8.3 General] darkassain:
it must be really slow machine, you dont use ccache?
[G Pad 8.3 General] AndroidUser00110001:
Ha that is with ccache. After first build it is a little faster but depending on what changes are made.
[G Pad 8.3 General] Poke_N_PDA:
I wonder if anyone would be interested in starting up a bounty for this. I would offer $20.
[G Pad 8.3 General] joshuadjohnson22:
Maybe you should start a new thread with it id be willing
[G Pad 8.3 General] titooo7:
Hi guys,

I'm thinking about buying a LG G Pad 8.3 but only if the Google Play Edition is 100% compatible and functional (otherwise I prefer to ask a familiar to send me the GPE from U.S even if it's more expensive).

In the "G Pad 8.3 Original Android Development" sub-forum there are some 4.4.2 roms and some of them claim that there are not bugs, is it really true?

I basically prefer to use a GPE rom instead of CM or similar because the device would not be only for myself and someone would kill me if I have to update it every few days...

thank you
[G Pad 8.3 General] DrDeeJay:
i would also be willing to donate to the one who makes it and also keeps making a new ROM after each official update ... coz its unfortunately impossible to get the original GPE in Europe.
[G Pad 8.3 General] EdenGottlieb:
Latest CM 11 nightly is wonderful, I found no bugs, It is very stable, performence is great, and the battery is long-lasting.

I have also tried CMB which was the same but had horrible battery life. Haven't tried any other roms, didn't need to.
[G Pad 8.3 General] joshuadjohnson22:
I only have very minor bugs, smart cover doesn't work, you lose the Icon on the far right of your dock when you reboot. Other than that it is great. Daily driver status, they've done good
[G Pad 8.3 General] GTabJosh:
Hey my friend, I would be happy to compile code for you all day (literally -- refer to avatar). I am in learning mode so this is an opportunity I would appreciate. I have done a little work on kernels -- basically chopping out oc/uv/governor/scheduler mods and fitting them from one device into another. I can read code much better than I write it!

I have the V500 source as well as the V510. I am trying to compile the ROM (no experience there btw), but I am embarrassed to say that I have not been able to get the correct version of Java on it. I was sure I found an Oracle 1.6 version, but no, it still reads as Oracle 7 (I forget the nomenclature).

Anyway, I am new to Linux and Android coding, but I think I have enough knowledge to help. It would be my pleasure.
[G Pad 8.3 General] AndroidUser00110001:
Thanks!

If you go to http://source.android.com and follow the instructions step by step then you should be OK. Download the latest source and compile a test build to see if it builds. If so then I can start working on a device tree to build a GPE ROM.

Don't forget to setup ccache too. Saves a lot of time after your first build.

You may also want to check the CM wiki for more info on setting up your build environment but the AOSP site should guide you right through.

----

On a different note LG turned down my warranty claim and will not fix the G Pad I bricked :(
[G Pad 8.3 General] afrikanac:
Sorry to hear about the warranty turndown Androiduser
[G Pad 8.3 General] AndroidUser00110001:
Ah crap happens...thanks.
[G Pad 8.3 General] EdenGottlieb:
I'm sorry hear that, those bastards.

I remember somebody wanted to buy it from you, maybe its still relevant
[G Pad 8.3 General] titooo7:
Thanks I was always have lot of respect for people who work with aosp based roms but I never used them because there was always something not working due to proprietary drivers and things like that.

I feel tempted to buy the LG G Pad 8.3 as I find 8 inches the perfect size (nexus 7 is too small, 10" tablets are too big and Apple Mini is not an option).

The LG G Pad 8.3 also motivates me because it's a nice challenge to make the GPE rom work 100% on "normal" G Pads.
[G Pad 8.3 General] joshuadjohnson22:
They didn't offer to fix it for a cost?