Database Users

[DEV] Suggestion for ICS Hardware Drivers

First off: I am not a programmer. I have only very little experience in C/C++ and that's it. I am here to suggest something, and I am not sure if it would work, but I'd rather have a stupid idea up here than a good idea not up here.
We all know that the developers are having trouble getting hardware drivers for ICS on our HD2s to work since the drivers' sources aren't being released. However, I know that for example Gingerbread ROMs have hardware acceleration just fine.
Android, though, is open source. And so I got an idea: What if we stopped looking at the driver, and focused on Android itself? What if a developer looked at how the driver framework has changed, and wrote some sort of dynamic bridge, so that ICS could use the driver of Gingerbread? Some kind of layer inbetween the driver and the driver framework that would reverse/translate the changes made between Android 2.3 and 4.0?
Again, I'm not a developer or programmer, so I wouldn't know how effective this would be. I'm just throwing this out here; if it's a bad idea you can just ignore this.

If its a dev question den.. remov suggestion and change it to dev
Sent from my HTC HD2 using Tapatalk

sam razzy said:
If its a dev question den.. remov suggestion and change it to dev
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
I have done so; would this be correct?

joeyvanhummel said:
I have done so; would this be correct?
Click to expand...
Click to collapse
That is what ramv87 did I think cause he uses gingerbread files. I dont know where he got the files from but if we knew what device he took the files from and how he modified them. That would be a start.

Xubuntop - A full XFCE4 desktop

The stock Webtop sucks in my opinion. A outstanding concept, but poorly executed.
I'm working right now in a "revamped version" of the stock one. I call it Xubuntop - A full XFCE4 desktop.
Xubuntu is originally a Ubuntu with XFCE4 environment and some optimizations. Check the original Xubuntu project (Google it)
I'm thinking in two versions: Lightweight and Full
Lightweight: flashed in Osh and ready to go!
Full: flashed in Osh and uses Webtop2sd to expand the internal disk space.
I know that many tried to do this and I warn you guys, I'm not rediscovering the wheel. It's just a "easy way" to get those extra applications using the Xubuntu as a base.
It will feature optimizations to make the environment as lightweight as possible, giving the CPU more room to process whatever you want to execute.
I'm working two weeks on this and maybe this will be ready Saturday, but I can't promise nothing
Maybe I'll need help to make the zip to use in CWM.
So... let's go back to work

I have a questions.
Is Xubuntop for cm7/9 roms or blur/stock roms ?

Will it be dependent on the broken/outdated Motorola packages?
By this I mean, will we be able to make full use of the repos to install newer versions of software that are dependent on newer versions these packages. (E.g. the latest verision of Chromium that I can get working now is version 4 due to its dependencies breaking webtop, even when apt-get has been fixed.)

xateeq said:
I have a questions.
Is Xubuntop for cm7/9 roms or blur/stock roms ?
Click to expand...
Click to collapse
Xubuntop should work fine with the Blur and Stock roms.
CM7/9 boots the Webtop from the Webtop2sd? If yes, then I guess the "full" version can work.
Ollonk said:
Will it be dependent on the broken/outdated Motorola packages?
By this I mean, will we be able to make full use of the repos to install newer versions of software that are dependent on newer versions these packages. (E.g. the latest verision of Chromium that I can get working now is version 4 due to its dependencies breaking webtop, even when apt-get has been fixed.)
Click to expand...
Click to collapse
In some parts, yes, it will be dependant.
My intention is to hold the core packages and add the lastest (and functional) repository with Arm support, 10.10 I guess.
The other alternative is get the source code and rebuild them in Arm architeture. This demmands a lot of work and I can't do it all by myself. But with more time and people, it can be done.

If it will run the latest available version of Chromium from the repositories (It was version 14 last time I checked) that's all I'm really concerned about. Good luck!

I guess it's impossible to squeeze a light version to fit inside the 0.8gb osh reserved space. Crap!
By the way, the system is more fluid than before. I'm trying to remove all non-essential packages right now.
With AT&T stock kernel (1Ghz) GtkPerf test run now in 13s. A huge difference.

Please give WebTop2SD a try to have a much bigger osh partition .

qaplus said:
Please give WebTop2SD a try to have a much bigger osh partition .
Click to expand...
Click to collapse
I'm using it since yesterday, only OSH it's impossible =(
The system have ~1gb right now
Edit:
I'm having a hard time trying to port the lastest Chromium-browser. I need to re-install ArchLinux in my desktop first and see if I can make it work there. I'll delay Xubuntop a bit trying to port it.

I did installed xfce4 after using webtop2sd. But i ended up with a lot of stuff laying around not used, i'd like some more integrated!

Night Walker! said:
I did installed xfce4 after using webtop2sd. But i ended up with a lot of stuff laying around not used, i'd like some more integrated!
Click to expand...
Click to collapse
Like what? aumix? Did you installed xfce4 or xfce4-desktop or even xubuntu-desktop?
I'm manually installing each software from the 'original' xubuntu distro to make sure we don't end with useless software. Is that what you want?

I'm a experienced C++ developer and I have some experience with Linux. Please let me know if you want some help.
Sent from my MB860 using XDA

mfragoso said:
I'm a experienced C++ developer and I have some experience with Linux. Please let me know if you want some help.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Oh, that would be great! I'm trying to port the latest Chromium to ARM.
Do you have experience in cross compiling? I'm stucked on this...

Would this run any faster than the current webtop with xfce4 interface? My webtop functions, buts slow as hell off my sd card sometimes. Its a class 10 pny card.

Only on windows (we use windows CE and its variants at work) but let me know how we can work.
Sent from my MB860 using XDA

teeth_03 said:
Would this run any faster than the current webtop with xfce4 interface? My webtop functions, buts slow as hell off my sd card sometimes. Its a class 10 pny card.
Click to expand...
Click to collapse
Hmm, it should run a little bit faster, but not too much. I'm trying to implement swap.
mfragoso said:
Only on windows (we use windows CE and its variants at work) but let me know how we can work.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Ok, I will =)
---
I'm working very hard to port the Chromium-browser 18.0.1025 (latest official), I've just bricked the webtop attempting to upgrade some core files... Not a problem... I was expecting this.
I'll not give up.

I broke my webtop so many times trying to get newer software to work that I just made a disk dump of a working partition that was configured how I want it. If I ever have problems, I just restore the disk dump, and within a few minutes I have everything working again.

this has me VERY excited, but XFCE still isn't lightweight enough IMHO.
What are your thoughts about Fluxbox? I remember having DamnSmallLinux on a 200mhz machine with 128MB of RAM, that was very responsive...
That said, we don't have a webtop subforum.
Which we really need, to collaborate efficiently.
Any ideas? This forum is way to frickin busy.

dev activity

this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull

demonoid phenomenom said:
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.

jeah thats right, i was wondering because my expirience with atrix 2 , previous to the ics update, i was using supercharger rom series, but again i understand that they got a leak to work on, and a bootstrap to flash the restores they where creating, and that stock leaked rom was awesome
sent from the gray stuff inside my skull

mattlgroff said:
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
Click to expand...
Click to collapse
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?

Le_Poilu said:
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Click to expand...
Click to collapse
Would be nice to know for sure. The current methods cannot find 'Android Magic'.

I'm looking forward to seeing this forum get some custom ROMs too...

Looks like progress is getting on with it now

Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.

tiberiu24 said:
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
Click to expand...
Click to collapse
You won't be able to build a full android system from that source. The most you can do is
Code:
$ . build/envsetup.sh
$ lunch generic_x86-eng
$ make [I]target[/I]
Where target is something like out/target/product/generic/system/bin/bluetoothd or bluetoothd

I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Sent from my GT-I9300 using xda app-developers app

hiemanshu said:
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Click to expand...
Click to collapse
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either

turl1 said:
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
Click to expand...
Click to collapse
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H

hiemanshu said:
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
Click to expand...
Click to collapse
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom

turl1 said:
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
Click to expand...
Click to collapse
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me

hiemanshu said:
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
Click to expand...
Click to collapse
Let's continue talking on PM then
re. 2, I actually did need to patch build on AOSP after all . CM on the other hand, has BOARD_CUSTOM_BOOTIMG_MK from the tf tablets.

Hey I posted a rom over at droidrzr.com for use till aosp is ready. This should be enough till we get a jb leak
Sent from my XT890 using Tapatalk 2

Hi Folks
While I don't own a RAZR I , I have been Jaffing around with building CM10.1 and AOSP for x86, I've been getting in going on my FX8120, just need to sort the OpenGLES MESA drivers out.
Anyways I've got CM10.1 built for x86 using the mr1-staging branch ( I think it's been merged to cm10.1 ) and an edited mini-x86 device tree .
Busybox was a B**stard to build though, although on one of the branches there is an .config-minimal-x86 .config-full-x86, still needed tweaking tho.
I submitted my patches http://review.cyanogenmod.org/#/c/27377/ and http://review.cyanogenmod.org/#/c/27373/, however It seems x86 isn't top of cm's agenda.... or I'm missing something about assigning reviewers.
Obviously a base x86 build is only part of the story for you guys as you'll face all the regular problems that emedded devices have, not checked the specs for the RazR but I'm sure there's some binary blobs in your future,
Hack On Folks! :good:

Moto XPRT Gingerbread Modding HERE!

Hello everybody, It´s been like a week since I last posted, a lot of things went wrong in my house and I somehow lost all my computers
anyway, back in business again, Last night I had to install the stock Sprint GB sbf, to my surprise it worked Really, Really good.
I´ve had a Defy+ and a Milestone 2, And I remembered having lots of issues with modding aka. no signal, wifi issues (like the cm7 and 9 ones) data issues, system lags, poor battery life, kernel errors on development, Overclocking settings not being saved, recovery mess-ups, and a lot of depicable stuff, most of all kernel-related.
Anyway, last night I flashed the stock rom over cm7 and noticed a real speed, functionality and battery boost, so I thought of just theming, de-bloating and optimizing the stock Sprint ROM.
Please follow me here:
We will never be able to flash custom kernels (not w/o the help of a reaaaaal good DEV)
CM9 &10, though they are eye-candy, are based actually on Gingerbread kernel, so no new features can be added besides the ones you can get withg new apps.
CM7, though stable, lacks the performance and functionality of the stock rom.
Finally, the stock rom as I said, (and I´ve tested TONS of ROMS in different motorola devices) is the one with the best responsivenness, snappiness and battery life, plus It's almost clean (eg. bloatware is easily removed.)
How will it be done?, you may ask.
Well Our first step, will be deodexing the stock GB SBF.
After deodexing we will be optimizing the build.prop on our phone, to trick apps into installing on our phones, and to make some quick optimizations.
Once we have deodexed our rom, we will be able to run,autorun and theme /system/apps.
Apps like Gnow, the statusbar and other tweaks can be easily (RELLY EASY) ported to deodexed ROMS
So this is the challenge guys, Let´s build our own stockcustom ROM.
So far I´m re-flashing stock sprint GB to continue testing only the essential apps, so we can build from there.
And just for a tease; here is my latest build.prop, with some tweaks and tricks taken from other roms and my personal experience, just make sure you have root access, fire up a file explorer and replace your build.prop
Please Refer to next post for links on how to maybe help me with deodexing the full rom.
And please, developers, dont take this as a shady move towards your development, I just think that the best way to make something is to start from scratch..... there are too many source files, modded files and crap files on cm7,9&10 specially when not officially supported (Because everybody messes with the files and re-distributes them, so a lot of clutter and unneeded files, references and code are injected on some releases....)
So my friends, we have a common goal, By now I have succesfully overclocked/undervolted the phone to 1350/233 mhz (not on recovery!!)
I´ve deodexed system/framework/
and Im stuck trying to deodex system/apps/
Xprt Owners of the world, please come on over here, we can do this...
I´m an architect/artist so I really want this to have a sleek look, but not copying a specific stock look, if you know what I mean....
From now on refer to the "wished features post" for features you´d like
And now my final statement:
Though it IS possible to compile JB or ICS from source to our phones, my experience with this somehow outdated android motorolas, is that you will not get significant performance boosts or super cool functions with new software. The only way to get this functionality is by upgrading the kernel which I again declare IS NOT POSSIBLE on our phone. CM9 and 10 my look like JB and ICS, but run straight off a GB kernel.
Yes you will get a lot of new stuff like menus and graphics, but the functionality will be the same, plus all the eye candy will trade off your new features with lags and possible errors.
Software is built in time with devices, and it doesn´t matter how much you say "but the hardware is capable of more!!", incremental software updates "ignore" some HW features, so they have to be forced or modified to run, which adds more procesess/tasks to the kernel and this will suck your speed and battery.
Let´s build something pretty...............:laugh:

Hello everybody, and welcome to the world of modding.
From today, we will be coordinating an army of people to work towards a common goal: Having the best ROM for our phones, and surviving the day.
The tools you absolutely need:
Brain
Hands
Eyes
Text-comprehension.
Be a self-troubleshooter
Advanced Google skills
Patience
Some Weed
First of all I will just oversee the topic: ODEXED vs DEODEXED
In simple words, Odexed systems have XX.apk and XX.odex, which store certain app properties (like icons, colors, fonts, menus) so that they wont be messed up with, thus making the system more stable, Deodexed systems, have only APK´s with their icons, colors and behaviors packed on, thus making theming, modding and using alternative system apps easier.
If you would LOVE to read about the subject, please refer to this: http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
Well, now that you are totally aware of the odex-deodex situation, you might ask yourself..
-how the phuck do I deodex my system??????
Well, deodexing implies merging the .odex properties onto the apk.
Hey!!!! but how???
you need brains, patience, Java SDK7, Android sdk, and music.
http://forum.xda-developers.com/showthread.php?t=1852322 this instructions are for deodexing.. good luck....
To save your time, you need Android SDK and JSDK properly installed, you need xUltimate (Try and find the version that works on you), and you need the patience and willingness of Sidharta.
Ive tried already 5 versions of xUltimate to find out errors on different files!!!!!!
http://forum.xda-developers.com/showthread.php?t=2065270This will tell you some other basics on the xultimate deal.
There are other ways to deodex, help me google that.
We will be based on the stock 1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-110-KNS-46-49-test-keys-signed-Sprint-US SBF....
I would love to develop something good to both sprint and boost, but I have a Sprint handset, so I cannot assure our development will work on boost handsets, so please just sprint handset owners only for now.

For xultimate errors and troubleshooting, please refer to Google.com!
Ive been up all last night deodexing my system apps, and found out that most google related apps cannot be deodexed...
maybe that's why you need to install gapps in cm7 or other custom roms...
anyway people, let's get fully deodexed.
Make sure you have both Android SDK and Java SDK 7 PROPERLY installed oin your pc before trying this.
Cheers, luck and please reply

One last thing, I dont know if it is related somehow, but try to flash your stock rom without a SIM card inserted

Quick update: I Think I´ve got it figured out....
You need full Android SDK, and Java development kit, Android sdk tools alone wont do it, and java alone wont do it, you need developer runtimes and libraries for some programs like xultimate to run right.....
And you need not to activate, use or anything your phone before trying to deodex, I guess just starting up and entering simple things as the time, or having a sim card installed, or your google account can write data on the phone and mess up with the deodexing process.....
xultimate has already deodexed full framework and has passed from the yesterday´s troublesome google quick search box...(first thing to fail last night) so let´s hope it goes well.. it is indeed a loong process...

and just another error, but now I think I have it figured out, you need smali-baksmali assembler/disassembler for some specific .jar packed files... I´ve just installed it, and hopefully will post a fully deodexed stock rom today or tomorrow, for you to test and for us to start theming.
remember if you want to try... you need jdk not just java, you need full android sdk bundle, and you need smali/baksmali on your jdk installation for it to work properly...

%#%"!!!
This completely sucks, I´ve been trying to troubleshoot the errors xultimate is throwing at me on specific files, that lead me to download A LOT of java JRE and JDK versions, and both in x64 and x32 flavors, which apparently caused a major mixup on my PC´s guts....
Now I´m freaking trying to clean up my dev enviroment, trying to re-set the appropiate paths and classes, but hell with it...
Anyone succeeded??? please let me know if you´ve tried and if you get into any error can you please upload a screenshot???
thanx

Sounds like hell. I haven't tried, because I just don't have enough time in the day to do something like this. Plus, the xprt is my only phone, so I can't afford to experiment on it much.
Sent from my XT720 using xda premium

tzuba12 said:
Sounds like hell. I haven't tried, because I just don't have enough time in the day to do something like this. Plus, the xprt is my only phone, so I can't afford to experiment on it much.
Sent from my XT720 using xda premium
Click to expand...
Click to collapse
Same.
Sent from my MB612 using xda app-developers app

are you trying to deodex the stock rom?

rongsang said:
are you trying to deodex the stock rom?
Click to expand...
Click to collapse
yes sir, but in the mean time I managed to patch it with the battery mod, power menu and ICS style notifications
If I can deodex it I think I can improve it a little bit more in terms of performance and looks and functionality , but my powerful pc is a zombie right now, this is no task an old notebook can handle

I have deodexed it a long time back but sadly I can't upload it now. You can run kitchen from cygwin and it will deodexed your rom completely.
Sent from my MB612 using xda app-developers app

Ive used the kitchen and xUltimate with no good results mate!...
I always get smali errors or heap size errors despite I was using even a 4gb heap size, and tried using different versions of smali baksmali....
I am beggining to think I´ve been cursed by the digital gods.
BTW, if you´re able to upload it, I´ll be very thankful dude! I think Im going nowhere right now

Here is the source code for the LG Gpad GPE (510)

this includes the kernel source. I am in the process of trying to build a gpe kernel. so far I can get into the menu config but cannot make successfully. I'm going to download a different distro with a clean build environment and try again. If anybody else has ideas and/or answers on how to do this successfully please post here.
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=lgv510
my attempt to build a kernel will be to allow for gamma correction and for the addition of ext2 to used on the SD card if possible. I have built kernels for my Linux box before but this is quite a bit more involved.

Will this allow a gpe ROM on the stock LG device
Sent from my LG-V500 using Tapatalk

Canadoc said:
Will this allow a gpe ROM on the stock LG device
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
I don't know enough about it yet. one would think that with the source code you could simply build and install GPE on to the framework of the LGE device, meaning the removal of all of the old software in the installation of all new software based on the GPE Kit Kat build.
Apparently, by reading other threads here that is not the case, or they would have already done so. Then again, I did not see anything posted about the source code before now.
Maybe a developer will decide to do something with this, and even better write a tutorial on how to do something that is worthwhile for the GPE. In the meantime I will muddle through.

Just my 2 cents
http://forum.xda-developers.com/showpost.php?p=49468038&postcount=329

Demetris said:
Just my 2 cents
http://forum.xda-developers.com/showpost.php?p=49468038&postcount=329
Click to expand...
Click to collapse
howdy, I like your idea, but I would also like to see more development for the GPE itself. maybe even a separate forum dedicated just to the GPE as right now it seems that everything is spread out, disorganized and very difficult to keep together for one or the other version. Upon this basis it would be easier to see what items and options are available for one device, without being distracted by the same for the other.
That being said, I definitely agree there should be a collaboration to achieve the ends that you desire, as they will also help the GPE users find what they are looking for.

was I able to successfully compile a kernel? Yes! Yes I did!! Arch/arm/boot/zimage is ready!
unfortunately this does not mean an awful lot of this point all I did was change the name of the kernel slightly and if not adjusted anything else nor do I have it back into a boot image but! This is/was the hardest part I think. Reason being the dependencies for getting this done.

I have successfully compiled, and pushed a kernel onto my gpad gpe 510. Now you can too! I wrote a tutorial at : http://forum.xda-developers.com/showthread.php?t=2628951
You will be able to control your device now. No need for a custom ROM if your willing to put in a bit of effort, but I understand if you dont.??