Database Users

[MOD][MIUI4] Volume+ Mod for MIUI4 v2.7.20 (Hold volume to skip tracks)

The prebuilt android.policy.jar ZIP attached is only for MIUI v2.7.20 for the Arc S (and unofficial ports based on that build, as long as the porter didn't already mess with that jar file). If you want it for other devices, get the 'Source Info' file and port it yourself.
You all know it. Roots in Cyanogenmod, ported to MIUI Gingerbread and many other ROM's over time... but new MIUI4 ROM's have missed out for too long. So here it is. Hold Volume-Up to skip forward a track, Down for back. Only works while music is playing and while screen is off and locked. Apparently it will also change FM channel if playing Radio, don't know and don't care.
It is based on MIUI UK's MIUI v2.7.20 for the Arc S, with the source info it should be easy to port to any other device. Might work on older/newer versions of MIUI too, don't know. This took me half an hour to do, it wouldn't have been possible without 7OH's original mod for Xperia's on Stock ICS. I just ported it to MIUI.
This is not a flashable ZIP, sort it out yourself. Extract, push android.policy.jar to /system/framework/ (overwrite old one) and optionally chmod it to 644.
Integrate it in your ROM if you wish, credit would be appreciated. Don't be an ass and claim it as your own. Just say "Volume+ Mod by CosmicDan and 7OH" in the credits.
Also attached is some info on the smali changes (a unified diff and two new files).
Bye!

i tried this on my galaxy siii but i just get bootloops

daniel9522 said:
i tried this on my galaxy siii but i just get bootloops
Click to expand...
Click to collapse
Galaxy S III is an unofficial MIUI device, contact your ROM developer to make the changes or try a different port. Also tell us which MIUI version it is and where you downloaded it from so others know. Thank you.

daniel9522 said:
i tried this on my galaxy siii but i just get bootloops
Click to expand...
Click to collapse
Just fyi, now that miui is based on stock firmwares, this will only work on devices it comes from (I.e the arc s). Miui gb was compiled from source, which is why stuff like this worked on all roms. Now they just patch some miui stuff into the original jar file, so the chances of a one-jar-fits-all are non-existant. The same patch will work, just that it needs to be done specifically for each rom. Too many framework changes between e.g. sense, touchwiz, Xperia etc.

lenny_kano said:
Just fyi, now that miui is based on stock firmwares, this will only work on devices it comes from (I.e the arc s). Miui gb was compiled from source, which is why stuff like this worked on all roms. Now they just patch some miui stuff into the original jar file, so the chances of a one-jar-fits-all are non-existant. The same patch will work, just that it needs to be done specifically for each rom. Too many framework changes between e.g. sense, touchwiz, Xperia etc.
Click to expand...
Click to collapse
Ahhhh OK fair enough, thanks for the info! I guess I will post in the Arc S section then. I will leave this here though because the other ZIP has a diff of the smali changes. and the MIUI port maintainers can take care of it. Still relevant for this section, also this is a first (at time of writing, no other site/ROM has it in MIUIv4 except for mine).
First post updated.

and this probably works for Neo V also thanks I try that later

Dan can you please provide me any information about how to use the diff file?

_polimorph_ said:
Dan can you please provide me any information about how to use the diff file?
Click to expand...
Click to collapse
Pretty sure you can't. It's for devs and users who want to integrate this feature into other roms. (Unless diff is associated with miui or somthing else then ignore me)

_polimorph_ said:
Dan can you please provide me any information about how to use the diff file?
Click to expand...
Click to collapse
With a program like WinMerge or patch binary compiled for win32. But you will need to edit variables, labels and line numbers where necessary. If you don't know how, don't bother. Basically if it's v0 on mine it might be v1 on yours, you can compare similar code around my changes to get an idea of what it should be.

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:

[DEV] CM10/CM10.1/JB4.2.x Work-in-Process

THIS IS A THREAD FOR TENDERLOIN ROM DEVELOPERS TO DISCUSS ISSUES REGARDING BUILDING, CODING, CREATING, DEBUGGING AND STABILIZING A CM10.1/JELLYBEAN 4.2.x ROM FOR THE HP TOUCHPAD. IF YOU AREN'T WORKING ON THIS, MOVE ALONG... NOTHING TO SEE HERE
Seriously, folks. This is an information exchange thread for developers. You're welcome to watch and listen, but PLEASE, please, don't ask user questions here, don't ask for ETA's, don't give huzzahs, and "I want this" stuff. Post that in the relevant ROM threads, the General or the Q&A. Thanks.

Thanks for starting this thread, shumash. Here's what I have so far:
I have built a 10.1 rom for the hp tenderloin. I am not posting the actual rom because it has a way to go. It is far from a daily driver. Instead, I am posting a link so other developers can build their own roms and maybe we can get a fully working cm10.1 rom.
My device tree is on github:
https://github.com/drmarble/android_device_hp_tenderloin/tree/10.1-ugly
On the 10.1-ugly branch is a semi working device tree for hp tenderloin cm10.1.
Many more details for building are included in the README file.
If you aren't set up to build cyanogenmod roms for the tenderloin, this won't be any use to you. It truely is developer only.
It is a work in progress. Very, very much a WIP.
Camera doesn't work.
Bluetooth doesn't work.
Thanks to the efforts of James Sullins the SDCARD mounts and sound works from the speakers.
This is heavily reliant on the work of Arne Coucheron.
His invaluable patches include:
http://review.cyanogenmod.org/#/c/34375
http://review.cyanogenmod.org/#/c/34377/
http://review.cyanogenmod.org/#/c/34374/
and his highly useful google doc:
https://docs.google.com/document/d/1cGKMXx112gGls9a6ziDTpPgObnU6ZExPy5tByqqIyI4/edit?pli=1
Without his work, we would still have no display.
Of course, everything depends upon the work of the cyanogenmod hp developers Dalingren, FatTire, jcsullins, eyeballer, dorregaray and all the rest.
All my patches are in one big, ugly patch. I included various gerrit patches that my patch is dependent on. I'll work on neatening it up so the commits are separate and readable. I just wanted to get this out there so others could work on it and we can get cm10.1 working.
I think that this is everything.
Please, lets have lots of folks working on this. We can't use gerrit because this isn't cyanogenmod. Steve Kondik feels that since we are dependent upon the legacy qcom repositories it isn't really cm. This is just a kang. We can post patches here, or link to our githubs. Or use pull requests. I also started a thread on Rootzwiki. IRC on #cyanogenmod-touchpad on Freenode is a good place to chat. Jcsullins has already contributed two essential patches that got us SDCARD mounting and sound via irc.
We can get this done together.

drmarble said:
Thanks for starting this thread, shumash. Here's what I have so far:
I have built a 10.1 rom for the hp tenderloin. I am not posting the actual rom because it has a way to go. It is far from a daily driver. Instead, I am posting a link so other developers can build their own roms and maybe we can get a fully working cm10.1 rom.
--SNIP--
We can get this done together.
Click to expand...
Click to collapse
Thanks for that informative post. What are you using for a default manifest and kernel source?

most of the information needed to build is in the README file at my github. I use the regular cm manifest and build tools. The local manifest I use is:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="drmarble/android_device_hp_tenderloin" path="device/hp/tenderloin" remote="github" revision="10.1-ugly" />
<project name="CyanogenMod/hp-kernel-tenderloin" path="kernel/hp/tenderloin" remote="github" revision="ics" />
<project name="CyanogenMod/android_hardware_atheros_wlan" path="hardware/atheros/wlan" remote="github" revision="jellybean" />
<project name="arco/android_hardware_qcom_display-legacy" path="hardware/qcom/display-legacy" remote="github" revision="cm-10.1" />
<project name="arco/android_hardware_qcom_media-legacy" path="hardware/qcom/media-legacy" remote="github" revision="cm-10.1" />
</manifest>
I just use the regular cm kernel. The addional repos work together with a couple of flags in Boardconfig.mk. Those are set in my "big_ugly_patch" which should have been broken up into several different ones. Really, you just have to set up a cm build environment, put in my local_manifest.xml, repo sync, apply the various commits listed in the README file and "brunch tenderloin".
To those who want a downloadable ROM. There isn't one yet. I don't think this is ready for anybody but home brewers. jcsullins' and others cm10 builds are much more stable and useable. This is just more fun for build-it-yourself-ers because it is newer and shinier. It's not a better android experience yet.

It may be worth mentioning, for clarity, to make sure you have included vendor/hp/tenderloin.
<project name="TheMuppets/proprietary_vendor_hp" path="vendor/hp/tenderloin" remote="github" revision="jellybean" />
I've been working on including the latest Adreno drivers but have found they are dependent on the CAF varriant, and we are stuck using legacy. Which is exactly why Steve Kondik said "I do not want to create official builds for any device that needs to use this. If your device can't support the latest driver for whatever reason, it's going to be janky and slow and probably worse than stock on 10.1."
I am trying to take some inspiration from the HTC Sensation, aka Pyramid, because that device is also msm8660 and they are utilizing the legacy display variant in 4.2.2 as well - without any complaints about video playback.

You can also use unzip-files.sh or extract-files.sh from device/hp/tenderloin to get the proprietary files. You just have to use jcsullins' latest cm10 zip file or installed rom (20130304etc.zip). These may be even more current than TheMuppets. They haven't been updated for 6 months. I know that the proprietary-files.txt file has been modified since then. I think that he updated some of the proprietary files so that sound would work. He also added some adreno libs, though we should look into the latest 4.2.2 adreno libs.

I'm trying out the Evervolv manifest, which is mostly AOSP. If it works, we may be able to get a mashup of the CM and AOSP source trees that gives us some options. So far, however, I've had to comment out the audio.primary.tenderloin package and the Settings package overlay in the tenderloin device source to get it to continue the compilation. I'll report back tomorrow.

drmarble said:
You can also use unzip-files.sh or extract-files.sh from device/hp/tenderloin to get the proprietary files. You just have to use jcsullins' latest cm10 zip file or installed rom (20130304etc.zip). These may be even more current than TheMuppets. They haven't been updated for 6 months. I know that the proprietary-files.txt file has been modified since then. I think that he updated some of the proprietary files so that sound would work. He also added some adreno libs, though we should look into the latest 4.2.2 adreno libs.
Click to expand...
Click to collapse
Are you getting any video playback with your builds using extract-flies.sh? All I ever seem to get is an infinite "loading" screen. I once used CM9 Adreno drivers in building CM10, with the same "loading" effect.

shumash said:
I'm trying out the Evervolv manifest, which is mostly AOSP. If it works, we may be able to get a mashup of the CM and AOSP source trees that gives us some options. So far, however, I've had to comment out the audio.primary.tenderloin package and the Settings package overlay in the tenderloin device source to get it to continue the compilation. I'll report back tomorrow.
Click to expand...
Click to collapse
Ok, after much thrashing, I"ve got everything compiled and waiting in the OUT folder, it stops with this:
Code:
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
out/target/product/tenderloin/obj/PACKAGING/systemimage_intermediates/unsparse_system.img: 1376/51296 files (0.0% non-contiguous), 60991/204800 blocks
Install system fs image: out/target/product/tenderloin/system.img
out/target/product/tenderloin/system.img+ maxsize=856424448 blocksize=135168 total=237901004 reserve=8650752
[email protected]:~/android/skz$
I'm guessing it has something to do with the releasetools, but I get no error. Any ideas?

If you look at my release patch I modify the release tools which changed for 10.1. I really need to separate that patch into it's separate parts. That would make it clear what you need to change. I did that months ago and really don't recall the reasons for each step, I just know that it works. The zip file format changed, as I recall. Wish I could help more. I'll get to work on cleaning up that patch and will make a cleaner branch soon.

drmarble said:
If you look at my release patch I modify the release tools which changed for 10.1. I really need to separate that patch into it's separate parts. That would make it clear what you need to change. I did that months ago and really don't recall the reasons for each step, I just know that it works. The zip file format changed, as I recall. Wish I could help more. I'll get to work on cleaning up that patch and will make a cleaner branch soon.
Click to expand...
Click to collapse
I think I've got that covered. I modified the releasetools, too, and tried both the modified Evervolv and CM versions, but what I get is that stop. I'll check and make sure, though, and I'll compile with the "-v" switch to see if there's something I missed.

I'm not sure if you are familiar with it, but you could try an application called Meld; its a diff viewer. It always comes in handy when I'm comparing code.
If you want to see what's different from the release tools in Evervolv and drmarble's repositories, you can just side by side compare them from your source locally :thumbup:
Also:
To go with the sound patch I removed one commit from the build process: # 34375 # MemoryHeapBase: ifdef for gingerbread/froyo compatibility We aren't using froyo libs apparently, thanks to jcsullins' new sound patch. This means we can remove -DBINDER_COMPAT from Boardconfig.mk.
For anyone who is not watching both threads
Sent from my SAMSUNG-SGH-T989 using xda premium

-SGA- said:
I'm not sure if you are familiar with it, but you could try an application called Meld; its a diff viewer. It always comes in handy when I'm comparing code.
If you want to see what's different from the release tools in Evervolv and drmarble's repositories, you can just side by side compare them from your source locally :thumbup:
Also:
To go with the sound patch I removed one commit from the build process: # 34375 # MemoryHeapBase: ifdef for gingerbread/froyo compatibility We aren't using froyo libs apparently, thanks to jcsullins' new sound patch. This means we can remove -DBINDER_COMPAT from Boardconfig.mk.
For anyone who is not watching both threads
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Chortle, I do need to watch everything, don't I? And I do use meld. It's a great tool. What I'd like to do is to run the "tenderloin_ota_from_target_files" python script from the command line. I can just see all those compiled files sitting there waiting to be zipped up!

I've tried utilizing drivers from the HTC sensation and jcsullins CM10 03/04 build with no further success in getting video playback to function.
Shumash, any luck with getting that to compile yet? Are you trying straight Evervolv source?
Sent from my SAMSUNG-SGH-T989 using xda premium

-SGA- said:
I've tried utilizing drivers from the HTC sensation and jcsullins CM10 03/04 build with no further success in getting video playback to function.
Shumash, any luck with getting that to compile yet? Are you trying straight Evervolv source?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I got a CM10.1 to compile, but it boots to the flashy screen. I'm in process of running a clean make to ensure I didn't leave something nasty around. The Evervolv source built to the point that it needs to be zipped into the OTA and release files, but I think there's something missing in the make files that connects with the releasetools. I ran a compile with the verbose switch set, and it acted like it just reached the end of the make files. I have also successfully built a ROM from PAC-man sources, but it also boots to the flashy screen.

Try flashing this after you flash your ROM. It's just a collection of Adreno drivers which I have been experimenting with, it might help get you booting!

-SGA- said:
Try flashing this after you flash your ROM. It's just a collection of Adreno drivers which I have been experimenting with, it might help get you booting!
Click to expand...
Click to collapse
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).

shumash said:
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
Click to expand...
Click to collapse
Just downloaded and flashed now, did not run into any errors. Hmm... I've uploaded it again under a different name :good:

-SGA- said:
Try flashing this after you flash your ROM. It's just a collection of Adreno drivers which I have been experimenting with, it might help get you booting!
Click to expand...
Click to collapse
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
EDIT: I found that all but two of the Adreno egl files are missing in the ROM zip. Copied the egl files and your other files manually, and it now boots . I guess is we're going to have to copy them as prebuilt until we have good source.

shumash said:
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
EDIT: I found that all but two of the Adreno egl files are missing in the ROM zip. Copied the egl files and your other files manually, and it now boots . I guess is we're going to have to copy them as prebuilt until we have good source.
Click to expand...
Click to collapse
Don't know if the attached are the same as those posted by SGA, but these are official ones from QualComm that I have been using with some sucess. They are advertised as...
"This release contains the user-mode driver binaries for Qualcomm's Adreno 3xx and 2xx GPU on Google Android 4.2 Jelly Bean MR1. It has been tested with the CAF release A8064AAAAANLGD133402.1 and M8960AAAAANLGD230306.1. Supports any Adreno 2xx and 3xx GPU on Android 4.2 Jelly Bean MR1."

[SOURCES] Elife E7 - Discovery Elite Kernel Sources

Here is the kernel source for:
General Mobile Discovery Elite
Gionee Elife E7
These two devices using the same kernel source. You should use the defconfig from your own device to compile and use it with shared source.
Source link: http://www.burakgon.com/kernel-sources-for-general-mobile-discovery-elite-and-gionee-elife-e7-is-here/
Have fun while modifying!
XDA:DevDB Information
Gionee Elife E7 - General Mobile Discovery Elite Kernel Sources, a Kernel for the GiONEE Elife E7
Contributors
burakgon
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2014-04-01
Created 2014-04-01
Last Updated 2014-04-05

Thanks a lot burakgon. I knew you were the real deal! Can you please post your ROM as well which is used in discovery mobile? And your flash tools which you promised to release as well?

[OFF TOPIC]
@burakgon Sir i Need General Mobile Discovery Kernel Source... You Made ATOM ROM Having ATOM Kernel For General Mobile Discovery Which Means You Have its Kernel Sources... i Tried Kernel Sources Released By FLY For its Fly-IQ4410 But Those Sources Are Not Complete Lots Of Drivers Are Missing And There is No Hope From Other Rebranded Devices... its An Humble Request Sir
Sorry To Disturb You Here...

Thank You very very much
let my exams complete
i will port cm

if you can provide device tree it will be awesome

yasirmujtaba said:
if you can provide device tree it will be awesome
Click to expand...
Click to collapse
I will try

Hi guys.
I am looking forward to support this awesome device. I got the source later i do the recovery and all stuff. Can anyone provide me stock boot.img and recovery.img.

icoolguy1995 said:
Hi guys.
I am looking forward to support this awesome device. I got the source later i do the recovery and all stuff. Can anyone provide me stock boot.img and recovery.img.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2706689

burakgon said:
I will try
Click to expand...
Click to collapse
hey burakgon did you got correct sources from gionee
i heard you were talking to gionee support for problems with kernel sources
pls reply

the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.

Ravikirancg said:
the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.
Click to expand...
Click to collapse
Ive tried upacking boot.img from my device replaced the zImage which i compiled from sources and again repacked it with the same ramdisk and flashed..The black screen appears. heard that sometimes the smaller size of ramdisk can be the culprit..

GTARaja said:
Ive tried upacking boot.img from my device replaced the zImage which i compiled from sources and again repacked it with the same ramdisk and flashed..The black screen appears. heard that sometimes the smaller size of ramdisk can be the culprit..
Click to expand...
Click to collapse
not exactly the size of ramdisk but the offset. we need a custom mkbootimg binary. need to edit mkbootimg.c and then re run make recoverytools. try unmkbootimg.

Ravikirancg said:
not exactly the size of ramdisk but the offset. we need a custom mkbootimg binary. need to edit mkbootimg.c and then re run make recoverytools. try unmkbootimg.
Click to expand...
Click to collapse
ive tried with different offsets from xperia z1 n nexus 5 didnt work.....not tried editing mkbootimg.c...ill try it later...btw can u compile it once for us if u have some spare time

Ravikirancg said:
the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.
Click to expand...
Click to collapse
afaik if gionee uses a custom mkbootimg wouldn't they have provided the custom tool to general mobile. if so burakgon could have provided us with same. I at least request him to provide us with general mobile firmware so as to test the theory that they might have made small hardware changes
in general elite.

GTARaja said:
ive tried with different offsets from xperia z1 n nexus 5 didnt work.....not tried editing mkbootimg.c...ill try it later...btw can u compile it once for us if u have some spare time
Click to expand...
Click to collapse
surely.. here you go https://www.dropbox.com/s/e62wf141ahcqy7j/mkbootimg
when you repack, keep base address as 0x0.
dhirajranger said:
afaik if gionee uses a custom mkbootimg wouldn't they have provided the custom tool to general mobile. if so burakgon could have provided us with same. I at least request him to provide us with general mobile firmware so as to test the theory that they might have made small hardware changes
in general elite.
Click to expand...
Click to collapse
well, I dont know much about Gionee to assume that it would have given the binary. afaik, it didnt even release the kernel sources.. let alone explain these. then again, I hope Gionee is dev friendly and helps us out. but I can assure you of one thing. Gionee does not use the standard methods. It surely has a messed up software on the device. it took me a week to get adb working properly on the terminal. Hell, I still cant get it to boot into fastboot mode..
P.S., It seems they use some signature for signing the recovery. I just unpacked the recovery and repacked it using mkbootimg. Its initial size was about 11mb. the newer one barely had a size of 8.7mb.
P.P.S., If some one is in touch with Gionee or get in touch with them, please pm..

Ravikirancg said:
surely.. here you go https://www.dropbox.com/s/e62wf141ahcqy7j/mkbootimg
when you repack, keep base address as 0x0.
well, I dont know much about Gionee to assume that it would have given the binary. afaik, it didnt even release the kernel sources.. let alone explain these. then again, I hope Gionee is dev friendly and helps us out. but I can assure you of one thing. Gionee does not use the standard methods. It surely has a messed up software on the device. it took me a week to get adb working properly on the terminal. Hell, I still cant get it to boot into fastboot mode..
P.S., It seems they use some signature for signing the recovery. I just unpacked the recovery and repacked it using mkbootimg. Its initial size was about 11mb. the newer one barely had a size of 8.7mb.
P.P.S., If some one is in touch with Gionee or get in touch with them, please pm..
Click to expand...
Click to collapse
Missing dt.img??
Sent from my ST25i using Tapatalk

AnoopKumar said:
Missing dt.img??
Sent from my ST25i using Tapatalk
Click to expand...
Click to collapse
ah! googled that up.. interesting.. the mkbootimg xperia ZU guys use syncs up with the one I built.. I will test that out..

They use some dtb.img.......
Have a look at dtb.img method
Sent from my Discovery Elite using XDA Premium 4 mobile app

This source is not good may be missing display driver.. Only giving black screen after booting.
Sent from my ST25i using Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------
Ravikirancg said:
ah! googled that up.. interesting.. the mkbootimg xperia ZU guys use syncs up with the one I built.. I will test that out..
Click to expand...
Click to collapse
You need to generate dt.img for for your complied zImage
Sent from my ST25i using Tapatalk

AnoopKumar said:
This source is not good may be missing display driver.. Only giving black screen after booting.
Sent from my ST25i using Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------
You need to generate dt.img for for your complied zImage
Sent from my ST25i using Tapatalk
Click to expand...
Click to collapse
yes I did that.. and as you mentioned, I get a white screen.. actually, my kernel itself didnt compile.. but I had some dts files and built a dt.img out of it.. if you built a stock kernel, mind sharinng your dt.img?

[GUIDE] How to Compile Your Own CM11/CM12/AOSP Kernel

Hi guys, long time no post. I have updated this guide on how to build kernels for Falcon so that anyone can learn! It's pretty simple once you get the hang of it. So yeah, here we go!
Prerequisites:
- You must have a Linux firmware running on your computer (I suggest Builduntu because you can skip the next one [build environment setup])
- Build environment setup (Put the this in terminal and follow instructions)
- Patience and a heart willing to learn
- You need to know the languages C, C++, Java, Ruby, Python... NOT! You don't need to know ANY coding languages.
[MOTIVATIONAL SPEECH]
Truth be told, when I first started out developing, I knew NO coding languages except for HTML and a little bit of Java. Both have nothing to do with kernels! I actually learned how to do this when I suffered from a concussion. So if you really want to learn how to kernel dev and you give up halfway, just know that a 14/15 year old kid could do it..
[/MOTIVATIONAL SPEECH]
Click to expand...
Click to collapse
WARNING: I am not responsible for any damages to your phone or computer or pet unicorn. When you modify the wrong partitions, set too many jobs for your compiler, break your keyboard out of frustration etc., that is not anyone's fault but yours. Or your pet unicorn.
Your Personal Handbook to the Following:
- Anything inside "CODE" boxes, type it into your terminal. If you can't find terminal, then press CTRL, ALT, t.
- If I were you, I would write these by hand instead of copying and pasting it because after a certain amount of times, you will remember the linux commands and it will be easier for you to compile more kernels for different devices
- Use this thread as a "Help Me" button. Ask for help!
Click to expand...
Click to collapse
A New Beginning:
Let's start out with something simple, getting the actual code:
Code:
git clone https://github.com/cyanogenmod/android_kernel_motorola_msm8226
This could range from 3 minutes to 2 hours!
Once that's done, open up your file manager and rename the folder (should be android_kernel_motorola_msm8226) to whatever you want. I will refer it as "mykernel".
Click to expand...
Click to collapse
Pokemon!
For this tutorial, we will be using a Sabermod 4.7 toolchain to compile. I WOULD teach you how to compile with 4.8+, but it creates errors that will take even longer for me to write about sooooooooo :fingers-crossed:. Now to get the toolchain:
Code:
git clone https://github.com/SaberMod/android_prebuilts_gcc_linux-x86_arm_sabermod-arm-eabi-4.7
Rename this to whatever you like, but I will be referring this as "toolchain"
Now go into you folder where the kernel source is stored...
Code:
cd mykernel
Click to expand...
Click to collapse
You're Almost There!:
Time to set-up the compiler!
Code:
export CROSS_COMPILE=/home/(insert linux home name here)/toolchain/bin/arm-eabi-
This tells the toolchain that "OK, we want to make ALL this code here into a kernel".
This next line tells it that your defconfig (the toolchain's manual for compiling the kernel) that it's in the arch/arm/configs folder.
Code:
export ARCH=arm
Now to tell the it what the defconfig is!
Code:
make falcon_defconfig
Hehe, now to the hardest part of all...
MuHAHHAHAHa
Click to expand...
Click to collapse
THE HARD (coding) PART
You ready for this? HERE IT IS! TIME TO BUILD THE KERNEL!
Code:
make -j4
Now sit back, relax, and watch the code! Or you could read a book, watch ****, count your fingers, play with your toes...
If you have an error during the waterfall of code, find the part where it actually says *error* (you'll probably have to scroll upwards) and search it on Google or post it here.
Click to expand...
Click to collapse
THE BEST PART
If you manage to get something that says "the kernel zImage is ready" or something like that, that means you've made it!
You have officially compiled your own kernel from source! Now you need to put it in a flashable zip.
Download this file and open it up, but DON'T EXTRACT IT.
Now go to your kernel source then "CTRL + F" and search for "zimage-dtb".
Find it and put it in the "kernel" folder of "FalconKernel - Signed.zip". Then "CTRL + F" and search ".ko".
Copy radio-iris-transport.ko and put it in the system/lib/modules (not pronto) of the zip.
Then find wlan.ko and rename it to pronto_wlan.ko. Copy and paste it in system/lib/modules/pronto of the zip.
Click to expand...
Click to collapse
Now you can put it on your phone and flash it! ​

I will update this in a bit. What feature would you guys want in your kernel? The most votes in the POLL above will be the one I teach you here!
Here I will walk you through on how to add the intelliplug feature made by @faux123
First, fetch my Green Machine kernel source (go into your kernel folder in terminal):
Code:
git fetch https://github.com/YoshiShaPow/green_machine_falcon
Then you could cherry-pick (basically copy) all my cherry picks for intelliplug from my source.
If you do check my source out, you can see there's a little link to a history of commits near the middle of the screen, right above the files/folders. You can see at this page of my features history, you'll see a bunch of commits for intelliplug. I will use those commits and copy it to your own kernel.
This copies the initial coding/first commit of intelliplug!
Code:
git cherry-pick 01a850f
This cherry-picks the remaining commits so that your newly added intelliplug is updated.
Code:
git cherry-pick 6623f2f^..4e1ece7
One more thing though, you need to add the line to compile intelliplug!
Almost all things compiled along with the zImage are in a file called defconfig. What a defconfig does, is tell your machine to build certain modules, kernel objects, drivers, governors, etc.etc.etc.. Now, all of them are found in the folder
arch/arm/configs
Click to expand...
Click to collapse
As stated in the OP, you have to modify the defconfig you use. (CM11 Kernel is falcon_defconfig, Gummy Kernel is msm8226_mmi_defconfig). Open up the corresponding defconfig and add this to ANY line anywhere.
Code:
CONFIG_INTELLI_PLUG=m
Now, for those who are familiar with "y=yes/n=no/m=maybe", you'll see that I specifically told you to put the "m=maybe" one. That's because when you compile the kernel again, right after you're about to start your build. Since you put that "m", the terminal will prompt you with a "y=yes/n=no" question on whether or not you would like to add the following feature. Since you would like to add the feature, put in "y". Later on when you feel more comfortable with adding features to your kernel, you can go back into the defconfig and put it as
Code:
CONFIG_INTELLI_PLUG=y
So that it will compile it without asking, since you have given it an answer.
Now you have officially compiled a "Custom Kernel" and with the knowledge you know, you could create a feature packed one by just kanging (copying one's work/features).
Always remember to
Code:
make clean && make mrproper
after every build to prevent errors and such!
Click to expand...
Click to collapse

I will use this to teach you how to make your own Bash Building scripts (and save time) to make it easier for your development life to flourish... eventually....

Any guide on adding governors or hotplug driver??
Sent from my Moto G using XDA Free mobile app

Best guide but how to add features likes s2w,dt2w etc

Flashhhh said:
Any guide on adding governors or hotplug driver??
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
Vote in the poll above! I will make a guide for one or more of the top chosen picks!
Brawn_Sg said:
Best guide but how to add features likes s2w,dt2w etc
Click to expand...
Click to collapse
DT2W and S2W are more complex. They require a few other things (ex. Powersuspend). I'll wait a bit and see what feedback I get before moving forward to something a bit more complex like DT2W, or GPU Overclock.

Can i use make menuconfig?

Krizthian said:
Can i use make menuconfig?
Click to expand...
Click to collapse
Yes you can. Normally when using "make menuconfig", you use the command after making the kernel's defconfig (falcon_defconfig).

Build using Docker
If you're on Linux, take a look at this approach which uses Docker for building CyanogenMod 12.0:
http://forum.xda-developers.com/showthread.php?t=2650345
(Disclaimer: It's written by me)

YoshiShaPow said:
Hi guys, long time no post. I have updated this guide on how to build kernels for Falcon so that anyone can learn! It's pretty simple once you get the hang of it. So yeah, here we go!
WARNING: I am not responsible for any damages to your phone or computer or pet unicorn. When you modify the wrong partitions, set too many jobs for your compiler, break your keyboard out of frustration etc., that is not anyone's fault but yours. Or your pet unicorn.
Now you can put it on your phone and flash it! ​
Click to expand...
Click to collapse
when i was trying to flash cm12 rom in cwm recovery it says error in zip and getting status 1 error , installation aborted ,
pls help im using moto g gpe and when trying to flash from twrp it says error executing updater binary in zip ,
no idea what to do pls help me out

karthik432 said:
when i was trying to flash cm12 rom in cwm recovery it says error in zip and getting status 1 error , installation aborted ,
pls help im using moto g gpe and when trying to flash from twrp it says error executing updater binary in zip ,
no idea what to do pls help me out
Click to expand...
Click to collapse
When you downloaded the anykernel zip, you aren't supposed to extract it. The best way to put the kernel in the zip is to just drag and drop it while IN LINUX. It will not work for windows! Or you could try signing the zip in TWRP (I think there's an option for that somewhere).

YoshiShaPow said:
When you downloaded the anykernel zip, you aren't supposed to extract it. The best way to put the kernel in the zip is to just drag and drop it while IN LINUX. It will not work for windows! Or you could try signing the zip in TWRP (I think there's an option for that somewhere).
Click to expand...
Click to collapse
im not extracting anything , i just downloaded the official cm12 nightly and flashed but didn't workout ,any ideas

karthik432 said:
im not extracting anything , i just downloaded the official cm12 nightly and flashed but didn't workout ,any ideas
Click to expand...
Click to collapse
That has nothing to do with this thread :silly:. You probably have to sign the zip again.

@YoshiShaPow.... i need some help
i compile a kernel for my device and it booted fine but no display....
can you help me in this....
sorry for posting here..my device is Redmi 1s

Luffy.d said:
@YoshiShaPow.... i need some help
i compile a kernel for my device and it booted fine but no display....
can you help me in this....
sorry for posting here..my device is Redmi 1s
Click to expand...
Click to collapse
No problem, I welcome anyone with kernel development questions here! When booted, what do you mean? And if there's no display, how do you know it booted? Also, did you use my anykernel zip? I may be wrong but I don't think it is compatible with all phones.

YoshiShaPow said:
No problem, I welcome anyone with kernel development questions here! When booted, what do you mean? And if there's no display, how do you know it booted? Also, did you use my anykernel zip? I may be wrong but I don't think it is compatible with all phones.
Click to expand...
Click to collapse
yeah it booted bro....i can hear lock unlock sound and even i can hear incoming call ring
i was trying to fix this from a week and found out it not kernel it rom problem ...
my device is build using prebuilt kernel so any compile kernel wont work...but now they are build with this kernel source so compile kernel work
thanks bro...
and one thing bro... i m new to kernel development so how can i optimize kernel
i know about and can add governors and use custom toolchain but i don't know about o2 or o3 optimization etc and all
sorry if i m being too much

great I start today

Luffy.d said:
yeah it booted bro....i can hear lock unlock sound and even i can hear incoming call ring
i was trying to fix this from a week and found out it not kernel it rom problem ...
my device is build using prebuilt kernel so any compile kernel wont work...but now they are build with this kernel source so compile kernel work
thanks bro...
and one thing bro... i m new to kernel development so how can i optimize kernel
i know about and can add governors and use custom toolchain but i don't know about o2 or o3 optimization etc and all
sorry if i m being too much
Click to expand...
Click to collapse
Those changes are a bit more advanced because it will bring build errors. The kernel is already preoptimized with o2 changes. The errors are fixable though. I don't think I'll be able to add an explanation for those in this thread, maybe through pm?

YoshiShaPow said:
Those changes are a bit more advanced because it will bring build errors. The kernel is already preoptimized with o2 changes. The errors are fixable though. I don't think I'll be able to add an explanation for those in this thread, maybe through pm?
Click to expand...
Click to collapse
thanks bro...will pm you when i finish setuping my git

etvtaglios said:
great I start today
Click to expand...
Click to collapse
Go for it bro!!