yashsingh1/xdaforums huggingface dataset:
[Moto X Themes and Apps] phoenix_rizzen:
Ah, found Dynamic Notifications in the Play Store that supports changing the colour. Nice. Thanks.
[Moto X Themes and Apps] natezire71:
Should be noted you won't get particularly good battery though. The native Active Display is tied with hardware integration with the special cores. Using a 3rd party app to accomplish this doesn't use hardware integration--thus, it will kill your battery faster. Just an FYI.
[Moto X Themes and Apps] phoenix_rizzen:
True. I'll be sure to test with both versions to see if colour optimizations affect the battery enough to be worth it.
[8125, K-JAM, P4300, MDA Vario General] Deleted member 265814:
Is there any way to force the history of the last used programs in the start menu? A Reg tweak or something? Or a way to delete the entries? That would be very nice.
[8125, K-JAM, P4300, MDA Vario General] vijay555:
I've put this into a new version of VJEschaton.. but check out

HKCU > Software > Microsoft > Shell > TaskSwitch

V
[8125, K-JAM, P4300, MDA Vario General] Deleted member 265814:
thanks for the tip.

I tried to delete all the entries in the reg key, but WM simply writes it back, even if i don't make a soft reset!

EDIT: I got it. Delete TaskSwitch, wait a few seconds and soft reset. you must wait long enough that windows can write changes into rom but if you wait too long windows writes the changes back :lol:
[Sony Xperia P, U, Sola, Go] awaisthebest:
I wanted to unlock my bootloader and install a custom rom but my windows won't recognise the fastboot mode so I started up with linux :(

I saw tutorials of recoveryX.exe and flashtool which only works for windows so I was searching for a manual way so that I could do it in the terminal ..

so I found some tutorial online which told me to flash some file something like

fastboot flash boot xyz.inf I don't remember the extension perfectly but it wasn't a zip or an img ..

and after that my phone turned off, I can still go for fastboot mode but I don't see anything on the screen please help me :(

I do not have windows so I cannot use flashtool or recoveryX.exe
[Sony Xperia P, U, Sola, Go] bharathbondfire:
using flash tool flash the boot.img present in the rom zip

and install the rom
[Sony Xperia P, U, Sola, Go] ChikeD:
Congrats for the brick.

Can you still get into fastboot/flash mode?

I've yet to hear about someone who used rexoveryx and it worked, forget all about it.

There is flashtool for linux, you can use it.

BTW, the only files you flash with fastboot, are with img, elf or sin extention.
[Sony Xperia P, U, Sola, Go] awaisthebest:
yes yes I can still get into the fastboot and flash mode both!

and yes the file was elf format I remember now.

P.S : I'm downloading the flashtool for linux right now, I just hope it works, its of my friends' and I took it with a guarantee that I'll give you with a better firmware :/ He's been calling me since morning lol .. I'm doomed :/

guys? is there any hope?
[Sony Xperia P, U, Sola, Go] awaisthebest:
Thank you for your reply :)

I'm downloading flast tool for linux right now and I'll then flash the boot.img present in the rom itself..

anything else that I can try if this doesn't work?

can anybody give me a link to CWM recovery's file and a way to flash it :/

P.P.S : I'm really really sorry for being sucha noob/dumbas* :/ but I just finished downloading flashtool and I cannot seem to install it :o I mean gosh! Linux is soo complicated.

I have downloaded a 7z file .. in which there's a file of tar extension which after I double click directs me to a folder named Flash Tools in which there are multiple forlder that include custom, deviced, drivers, firmwares etc
[G Pad 8.3 Android Development] sleekmason:
If you are a v500 user and want to build your own kernel!

First, read the above post as you will be following the steps listed there.

​

There are just a couple of changes that you will need to do, and maybe a riddle to figure out as well. Read on.

You will need to download the v500 source from here: https://www.lg.com/global/support/opensource/opensourceList?superOsCategoryId=CAT00000001&osCategoryId=

Look for the LGV500 kernel source.

Where it says "palman" for the defconfig items, you will want to replace that with the defconfig for the 500, so replace palman with awifi-perf,

like this:

export KERNEL_DEFCONFIG=awifi-perf_defconfig

make awifi-perf_defconfig

Important

Follow the guide and build with the Google Toolchain eabi4.6 first

LG compiled for the 500 and 510 using the eabi4.6. It works, and will give you a feel for the process, and allow you to use your kernel.

Note*

I use the google toolchain eabi-4.7 for the sleekai kernels as it changes the gamma to reasonable defaults on the 510 without further tweaking. After compiling a kernel or two to get a feel for it, you should try using the 4.7 toolchain. To do so, you will probably need the libglibc libraries from the "testing" branch. Look it up.

caveat: I recieved a compile error for the v500 when I used the eabi-4.7 . . . . . yeah. You'll have to work that out.

There is a modified anykernel script for emmc devices out there (Search Google or here in xda). You will have to use the anykernel script after making your boot.emmc.win image as fastboot won't work on the 500. There may be another way .... But I don't know what it is.

Edit* There are now two different kernels for the LG GPad 8.3 V500(awifi) located in the development section of the forum.

Best of luck! -sleekmason
[G Pad 8.3 Android Development] Canadoc:
Can this be used to create a kernel for the non Google Play Edition Gpad to be able to allow us to install the Google Play edition ROM on it
[G Pad 8.3 Android Development] sleekmason:
I would think so. I edited the above to show how to put the image back on your device. You should be able to use any source you wish to compile with. My thoughts are that you might wish to examine the differences in the ram disk if any.
[G Pad 8.3 Android Development] AndroidUser00110001:
Thanks for the guide. Making GPE kernel was my next step in trying to get the GPE ROM to work on v510.

I just made guide for getting your Android build environment going if you want to use it on your blog or where ever.

http://xdaforums.com/showthread.php?t=2629008

The problem with v500 is that it does not have fastboot so we can not flash kernel like how you can on v510.
[G Pad 8.3 Android Development] sleekmason:
@ AndroidUser00110001 Hi! I know that somebody tweaked the Any kernel to work on emmc devices... Maybe it could be adapted? Actually getting the menuconfig and make should be the same process as well as repacking the image. I take it just getting it back on the 500 device is the problem?

I will add your link to this post for setting up a build environment if that is okay.
[G Pad 8.3 Android Development] AndroidUser00110001:
Is that the koush any kernel? I was going to mess with that too. I just need a small break now. Took a few days to get new system exactly how I want it.

Go ahead and use guide...mo problem at all.
[G Pad 8.3 Android Development] sleekmason:
Yes, from here: http://xdaforums.com/showthread.php?t=847265

I noted that boot was on block nncblk0p21 on our device, and not 22? better double check that. I tried it Anykernel as well to no avail when getting this set up. Fastboot is Awesome!

It's taxing to get it set up right. Seems like things change very often for the dependencies based on other package changes. I ussually go with testing but redid two partitions with stable. The 32 bit is just going to sit there, which seems kinda silly due to the need for extra packages in 64 to compile for 32 but whatever. Yeah.
[G Pad 8.3 Android Development] ayziaa:
I don't understand, what are the differences bettween the v500 and v510? they both have the same hardware, but not the same boot partition or something like that?
[G Pad 8.3 Android Development] sleekmason:
The boot on the 500 cannot be fully unlocked.

This is not the appropriate place to ask that kind of question should be asked in general or in troubleshooting. Also, there are already many threads about this same question please use the search utility to find them. Thank you.
[G Pad 8.3 Android Development] darkassain:
i was thinking of writing a tutorial about this as well for the v500 but this better than i would have done Well done...:D

Another tool that i ported to the lg g pad a bit back along with loki-doki...;)

Quick hint, dont bother with direct mmc naming as qcom (i dont know if the other chip makers do the same thing, as i have only had qcom devices) has given us a simple naming scheme...:)

should only be used by people who know how to use this,
[G Pad 8.3 Android Development] sleekmason:
Thank you! Have you successfully used your script to push a kernel onto the 500 Or 510?

I would think this could be very handy for sharing a custom kernel for the 510, but would like to see somebody report a positive test result. Very cool!
[G Pad 8.3 Android Development] darkassain:
yes back before when there wasnt a overclocked kernel i basically used this to push it when i would compile just the kernel (didnt maintain so i now use dyn's)...

yes this is only for the v500 as this has the extra loki step, but it shouldnt be hard to modify so it does not do that extra step
[G Pad 8.3 Android Development] poondog:
Hi, can you just use a generic anykernel updater script too?

For example to flash a packed boot.img

run_program("/tmp/busybox", "dd", "if=/dev/block/platform/msm_sdcc.1/by-name/boot", "of=/tmp/boot.img");
run_program("/tmp/unpackbootimg", "-i", "/tmp/boot.img", "-o", "/tmp/");
run_program("/tmp/repack-ramdisk.sh");
run_program("/tmp/mkbootimg.sh");
run_program("/tmp/busybox", "dd", "if=/tmp/newboot.img", "of=/dev/block/platform/msm_sdcc.1/by-name/boot");

mako and flo can do like this.. I think HTC One as well, since they are all similar qcom chipsets maybe this device can too
[G Pad 8.3 Android Development] darkassain:
thanks for reminding me the any kernel uploaded by me won't work as it doesn't parse Loki images xorrectly, I'll upload the correct one once I have access to my pc
[G Pad 8.3 Android Development] sleekmason:
could you please re-post to a different thread rather than hijacking this thread, as your script does not work with the 510 currently and I do not want to go to get confused with my kernel how to. what started out to maybe become relevant apparently will not and so shouldn't be confused with what I'm doing here. I will be happy to try working with your script if you would open up an appropriate thread. Thank you.
[G Pad 8.3 Android Development] gunnyman:
Installed kenel and booted. Now to install trickster mod and fix the dang gamma. :)
[G Pad 8.3 Android Development] sleekmason:
Excellent!! Pleased to know that you are able to use it. Have you changed your gamma settings?

I did on mine and am pleased with the result. I'm using 248, 252, 255 using trickster mod What are you going with?
[G Pad 8.3 Android Development] gunnyman:
havent messed around too much.

I had a thought about this and I think it would be awesome if we could incorporate faux123's bits for gamma and color control. His fauxcontrol offers much more granular control than trickster.

I'm thankful to have what we have, and THANK YOU for sharing it, but like any good geek I WANTS MOAR!!!!! :p
[G Pad 8.3 Android Development] sleekmason:
me too! I'll look into it. There are other apps besides trickster to give you more control. I think at the kernel level everything we need is unlocked. And yeah, he knows his business like nobody else eh? I'm just persistent.
[G Pad 8.3 Android Development] gunnyman:
I mentioned Faux123 because I installed faux control and it said it didn't find a gamma adjustment enabled kernel.
[G Pad 8.3 Android Development] sleekmason:
Huh, strange. I'm guessing that there may be other parameters specific to his kernel the lg doesn't have in theirs. I know that trickster is working on this kernel, maybe another app not written by the kernel developer of the same? He may very well have his gamma tool only work on his kernels, or the lge adjustments are more limited in their ability.

Anyway, it most definitely is nice to make any improvement over stock.
[G Pad 8.3 Android Development] whoamigriffiths:
I use faux123 control on a v500 using a tweaked kernel and I too took what the app says about not being able to alter the colour.

So I just decided to try it anyway and it works.

So I'd suggest just having a play around with the app and see if it works for you too

All the best Rich
[G Pad 8.3 Android Development] Canadoc:
Which lv500 tweaked kernel?
[G Pad 8.3 Android Development] whoamigriffiths:
Taken it to pm, sorry Op I had no intention to derail the thread.

All the best Rich
[G Pad 8.3 Android Development] sleekmason:
Whoamigriffiths is correct. Faux gamma control

does

work! :)

My guess is that his program looks for a particular marker that our ROM doesn't have.

Edit: Won't save settings... Hmm. Trickster keeps them.
[G Pad 8.3 Android Development] AndroidUser00110001:
I did not get errors but it did not state zImage is ready but file is there. Lets see if this works :)

NVM...I got it to disply...I used the make -j8 switch and it displayed when done.
[G Pad 8.3 Android Development] sleekmason:
This guide is completely copy and paste now, from start to finish, from setting up dependencies and adb, to compiling your kernel and pushing it back onto your device. The only caveat is that you must have a debian system, or figure dependencies for yourself.

If all you want is the kernel, it is available in the second post!

There were some unclear directions about how to get the tools and get them installed. This has been taken care of. Just follow the code!

I really want somebody to complete this guide and tell me how it went!
[G Pad 8.3 Android Development] schalmers:
Hi Sleekmason,

Thank you for developing for the v510, you are in the minority here for the moment.

Would it be possible to post in the 2nd post of the thread a fastboot flashable stock default kernel? I know we can back-up the boot from TWRP but it would be nice to have a fastboot flashable kernel just in case we need it or can't get back into TWRP, for the moment I only sideload TWRP to keep the stock recovery on the device.

Coming from Nexus devices I though I would have factory images I could flash but it seems it is a bit more complicated on the GPE devices.

Thank you,

Shaun
[G Pad 8.3 Android Development] sleekmason:
howdy,

If I understand you correctly, you are wanting the factory kernel image that comes with the GPE. That is, the kernel image without any changes? Yes, I think that would be a good idea. the image I post will still be one compiled from the LG sources.

for those that do use TWRP I recommend to make a boot back up to store on your device SD card, or on your personal computer anyway.

If you want the Numbering scheme under the kernel name, I will need somebody to send me a backup of their boot.emmc.win image, as mine was destroyed when I decided to install ubuntu, and it changed my partition scheme and destroyed the info on my backup partition. yeah. wtf. Post it here and will move it to the second post.

Anyway, the source is the exact same thing, but will change the date. If that doesn't matter, let me know and I will compile one.
[G Pad 8.3 Android Development] schalmers:
Hi,

Yes I am looking for a Fastboot flashable factory kernel image for the v510 (GPE) just incase it is needed someday ...

I don't fully understand what you mean by "backup of their boot.emmc.win image", what I think you would need for this is the file that is created from your OP where you write:

In TWRP, Only tick the boot

make a backup to your sd card. I changed the name to boot.bac to keep it simple

If I understand correctly the "boot partition" is the kernel, and I would like that to be flashable from fastboot that way if I become brave enough to try your kernel and there are any issues I can just return to "Stock" by flashing the original kernel like I have done many times using Nexus devices.

Up until now I have been hesitant until now to make too many changes on the GPE as there is not an easy way to return to stock like the Nexus

Thank you
[G Pad 8.3 Android Development] sleekmason:
Hi, The actual file that you flash onto your device is the "boot.emmc.win" that will be in your boot backup, were you to make one from twrp.

The boot.emmc.win file contains the kernel and the ramdisk for your device. Basically what we are doing is taking the whole file out of your device, separating it into its parts, (kernel and ramdisk), replacing the existing kernel inside of the boot.emmc.win file with the kernel you compile, and then puting it back together again to flash onto your device.

If you make a copy of the original boot.emmc.win file, and store it on your computer, that is all you will need were something to go wrong.

On top of that, If you only do the "flashboot boot" command rather then the "flashboot flash" command, the kernel is simply stored in memory, and upon reboot will revert back to your stock image.

Does this answer your question? Basically you can do the whole guide if you want, or just flash the kernel in the second post to try out without threatening anything on your device :cool:
[G Pad 8.3 Android Development] schalmers:
Ok thank you things are more clear now, I appreciate your patience with me :)

So if I extract the boot.emmc.win from my TWRP Boot backup then all I need to do to flash the original stock GPE Kernel is:

fastboot flash boot boot.emmc.win

I was looking for a file more like boot.img which I am used to using on the Nexus devices

Once last thing, in your guide after we flash your custom kernel, you mention to do:

then immediately after (fastboot flash boot boot.emmc.win):

fastboot boot boot.emmc.win

##This will force your device to reboot.

Wouldn't in be enough just to do a : "fastboot reboot" as the kernel was flashed so rebooting would of course boot it?
[G Pad 8.3 Android Development] sleekmason:
Heh, Always learn something new. I didn't even try that because after a fastboot boot it does automatically and when it didn't after fastboot flash, I just figured the easiest thing to do was another fastboot boot as it was already "flashed" onto the device! Could you confirm the command fastboot reboot does the trick? I'll change it in the op.
[G Pad 8.3 Android Development] muiriddin:
Thank you for this guide. I am working to take the plunge in building my own v500 kernel and already have a Debian box in the house. This will definitely help me get started. For the Dev setup and compilation.
[G Pad 8.3 Android Development] sleekmason:
Good! Feel free to ask if you have any questions.
[G Pad 8.3 Android Development] sleekmason:
Some notes for the v500 make:

You will want to download the v500 source from here: https://www.lg.com/global/support/opensource/opensourceList?superOsCategoryId=CAT00000001&osCategoryId=

You will want the LGV500 kernel source.

Where it says "palman" for the defconfig items, you will want to replace that with the defconfig for the 500, so replace palman with awifi-perf,

like this:

export KERNEL_DEFCONFIG=awifi-perf_defconfig

make awifi-perf_defconfig

Now, I have the 4.7 eabi listed for download as it changes the gamma to reasonable defaults on the 510. You will probabably need the libglibc libraries from the "testing" branch to use 4.7

I'm going to update this in a minute to show 4.7 as an option, and 4.6 as the default.

I WOULD TRY WITH 4.6 FIRST ( It's easy to change out the 4.6 eabi folder for the 4.7 when you want)

caveat: I recieved a compile error for the v500 when I used the eabi-4.7 . . . . . yeah. You'll have to work that out.

There is a modified anykernel script for emmc devices (Search Google or here in xda). It didn't work for the 510 and will need a minor tweak to work with the 500. You will have to use (I think) the anykernel script after making your boot.emmc.win image as fastboot won't work on the 500. There may be another way ....

Don't be discouraged by reading all of this. It really is easy once you are set up!
[G Pad 8.3 Android Development] muiriddin:
Thanks again for this,

I've managed to build a stock kernel (I did this primarily to test that the environment was set up properly) so then I decided to try building from the mahdi kernel source(the rom that I am currently running on my V500). I found it, downloaded it and am building it now.
[G Pad 8.3 Android Development] sleekmason:
So can you confirm that the guide as posted worked for you? Yes? Good!

Be aware that in order for the gamma to be changed, you may well need the original source from Lg. Also, look in my kernel thread to find all of the settings that I changed, as you may find some useful for you! The config for my latest kernel is also available on github.

Again, if the guide worked for you as posted, please state such as you are the FIRST to try it!! (Or at least post you did!)
[G Pad 8.3 Android Development] muiriddin:
I can confirm that I can get all the way to a zImage file with the LG stock kernel source and your guide and the changes to the process you document in the second post. I haven't gone any further using your guide yet than the step which pulls the boot.bac file down to my machine. I still do need to review what you changed in your GPE kernel and do some further reading on the anykernel script/process...

Correct me if I am wrong but I think to go further with the stock kernel and test what I've built I'd have to flash my tablet back to stock and then reroot it to then test booting the LG Kernel I have built. My thought was since I'm running Mahdi to use your guide with the Mahdi source and see if that boots... however the gamma fixes are tempting me... (although as you have mentioned that would require me to figure out the 4.7 puzzle) I may flash back to stock and try that... I can always recover to Mahdi from a nandroid... *grins*

Time for some sleep though I am running short these past few days... due to this lack of sleep my above post may seem a bit discombobulated...
[G Pad 8.3 Android Development] sleekmason:
Excellent! I would think you could use the lg source with no issues, as the important part would be your ramdisk and the actual parameters of the make itself i.e. ramdisk offset etc...

This being said, I would complete a total image using 4.6, download the anykernel script and see what needs changing. The paths you need should be shown in your ramdisk. Put the ramdisk after you "unmake the bootimage" into a separate folder in home where you can open it up and see the files. I just made a directory called ramdisk in my /home to examine the ramdisk files, and another named "sandbox" for changing the contents and repacking with my zimage. (all of this will make sense once you complete the guide)

Here are the commands to unpack and repack the ramdisk.

##unpack and repack the ramdisk

gunzip -c ramdisk.cpio.gz | cpio -iu

##Put something in it

touch it_works

## The file "it_works" or copy and paste using file manager.

##Put it back together

find . | cpio -o -H newc | gzip > ../myramdisk.cpio.gz

Note* I wouldn't modify that last bit. It will put the image in your homer folder, and then you should rename it back to ramdisk.cpio.gz if you incorporate changes to the ram disk. (see sleekai4 for examples of that.

I'm really glad you are trying this. it can be hard work but very rewarding in the end! Regards,
[G Pad 8.3 Android Development] sleekmason:
[MENTION=2495588]gunnyman[/MENTION] just shared a snippet with me you may find useful for the zip image for the 500. I will look into it for the 510 as well. The post is here:

http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source