Develop Bugs

Android 2.3 (Gingerbread) Being Pushed To AOSP

http://www.androidpolice.com/2010/1...3-gingerbread-being-pushed-to-aosp-right-now/
go, go, go! )

These are very good news
I already see my Hero running CM 7
:happy face:

Excellent News Lets see who get's their GingerBread ROM out first

Sweet, if the hero really will be supported!

Cooooooooooooooool man very nice go go go go gooooooooooooooogle

Tchuup-tchuup! Hotness train is leaving the stations

ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.

dkelley said:
ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.
Click to expand...
Click to collapse
Feeyo...

Good news
Sent from my HTC Hero

C0mpu13rFr34k said:
Feeyo...
Click to expand...
Click to collapse
should be interesting to watch his progress

I wish the technical know-how would be something well documented.
What I mean is, ive seen lox/benocharm (sp?) progress in the last year in terms of Android knowledge, almost from the start. Ive seen one of these two guys post about initial questions about how things work, then edit his own post to do a mini-FAQ on ROM cooking. Now today it would look like they would kick some major ass at doing it if they were still able to give time for this, because they know the Hero hardware by heart; they know the usual glitch when porting (ie: how to make camera/bluetooth work, etc), all the minor details that makes a ROM usable or not for a day-to-day ROM! However, this kind of knowledge seems not so well documented.
What i'm basically saying is if a developer bails out the documentation about how to rebuild a custom ROM does too. It looks like (from a non-cooker point of view) that there is no centralized Wiki or webpage about the usual generic steps or roadblocks when porting from another device or when starting from AOSP to build FOR an Htc Hero (or any device, too).
Personally i know enough about linux in general, ive build a few updates.zip for my own knowledge's sake (nothing fancy though, removed/added apks ), but I have my questions on how to properly make something not built specifically for an Hero work with all the hardware functioning. I'm sure many others are in the same boat (plenty of tech knowledge but lack of Android ROM resources). For example, the question I had in mind were in the form of:
Does specific hardware components (gps, wifi, bt) relies on linux kernel modules? Does it need some kind of special APKS or Jars to make it work along with the framework, or just kernel modules are enough once loaded?
Following up on the point above: would copying modules from another device specific ROM would be sufficient? (I guess not), what about Android release versions (Eclair, Froyo, Gingerbread, etc)? Can modules work regardless of the Android version being run on?
ETC...
Well its pretty much a long rant, but since i'm stuck with a 3 year contract on Telus with an HTC Hero, I wouldnt mind giving a bit of my free time to make a working ROM out of it. However I am/was under the impression that the Hero ROM development scene went to a stop once Cyanogen started supporting Hero (seems to me there are only two *major* roms out there, CM and VillainRom), and due to that ROM cookers stoped caring about the Hero since it was well enough supported as it is (with CM on board).
Thanks for listening, doctor

I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero

l0st.prophet said:
I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero
Click to expand...
Click to collapse
Any luck with it? I had the same idea, reading now a lot of information about building a rom.

Maybe we can post some useful links or tutorials about building ROMs in this thread so that we can kind of collaborate?

That would be a great idea, i really like the idea of building my own rom. or at least try to build one.
Here you can find how to setup your own machine to build android roms
http://source.android.com/source/download.html
if you have problems with installing sun-java5-jdk follow the instructions on this page:
http://blog.enea.com/Blog/bid/32050/Ubuntu-9-10-Java-5-and-the-Android-Open-Source-Project

Also checkout Cyanogen's wiki, they really did an excellent job there:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Hero

I'm progressing... slowly. Downloading Ubuntu 10.10 iso, 200MB of updates, the SDK, Eclipse, the ADT plugin, all the platform updates and GIT is taking a while on < 2Mb connection...

Especially the repo syncing... that just takes ages ;

krispijn_s said:
Especially the repo syncing... that just takes ages ;
Click to expand...
Click to collapse
Gives me time to read I spose! I totally understand how to build off Cyanogen's code, that sounds simple, but I get a little lost when it comes to syncing with AOSP or branching Cyanogen to make changes... but I got hours of dowloading yet so I can read up about it then!

Make sure you download the x64 version of Ubuntu. Since 2.2.1 you need a 64-bit system to compile the Android OS project.
Also don't expect to get it compiling right away, I reckon somekind of cpu-profile is missing (could be named different). Third I heard that the sound and camera (again) systems got changed, could be buggers to get those working.
Just my two cents

[DEV] Fixing/Updating the HD2 kernel and missing code

Please stay ON TOPIC to kernel DEV and missing code. Don't report every bug the Android build your using is having or it will be deleted as OFF TOPIC
As you all might be knowing that hd2 is pretty much a android native device now. Its just like any another snapdragon device. The current kernel code we are using in HD2 is pretty obsolete and missing a lot of things. It more like something working at its minimal efficiency. While i was porting over all the HD2 board files getting it on par with the other snapdragon devices I found out a lot of code was missing and some was obsolete. Eg. The gsensor code from microp was pretty minimal, a lot of things were missing in microp code. I suspect that it isnt the only code, a lot of bluetooth related stuff was missing and much more. I am not really gonna work on backporting the stuff to .32 kernel so i would like the kernel devs here to backport the stuff to the .32 kernel so a lot of bugs can be fixed and stuff can be made more stable until the .37 kernel is ready. All the commits can be found here
https://github.com/charansingh/cm-kernel/tree/master
There might be some bravo or passion instances in there cuz i am comparing the code with these two devices and taking what is necessary and sometimes i have to leave my work due to some other work and forget which file i was working on so would appreciate the more bugs.
Also Mods can we get this a sticky so we can track the progress here

Yap.. i'm not a really pro developer but i suspected those bugs before.. finally a real developer suspected that.. eager to see who's going to help fixing them

charnsingh_online said:
Also Mods can we get this a sticky so we can track the progress here
Click to expand...
Click to collapse
Ok sticky for the moment to see if it helps.

@charnsingh_online
I am really happy that you put so much power in this project big respect for that.
The reason for the missing code is because most of the drivers are reversed engineerd from winmo by cotulla. Wich make it possible to make working android parts but they don't work optimal by that. Also we miss some skilled active coders. After cotulla almost everything is created by markinus he did a incredible part big credit to him but looks like he isn't that active anymore..
Current development are mostly little things a guy who sees a little part from that and a little part from that like : you, tytung, darkstone, gauner,letama, the guy from the bluetooth fix.
We probaly don't have so much real kernel programmers because they buy a native linux / android phone.

The last two major things left with HD2 Android are buggy speakerphone and missing assisted-gps function.
Speakerphone mode is not usable because mic gain does not change when speakerphone is enabled. Info here:
http://forum.xda-developers.com/showpost.php?p=12698204&postcount=22
GPS works but without assistance so most locks take 1 minute instead of like 15 seconds. Info here: (please read all 25 pages)
http://forum.xda-developers.com/showthread.php?t=1008252

memin1857 said:
The last two major things left with HD2 Android are buggy speakerphone and missing assisted-gps function.
Speakerphone mode is not usable because mic gain does not change when speakerphone is enabled. Info here:
http://forum.xda-developers.com/showpost.php?p=12698204&postcount=22
GPS works but without assistance so most locks take 1 minute instead of like 15 seconds. Info here: (please read all 25 pages)
http://forum.xda-developers.com/showthread.php?t=1008252
Click to expand...
Click to collapse
actually i think the gpu drivers are kinda unstable when comparing to the performance of other phones that carry the similar gpu...

@charnsingh_online
Good start.
After reading the github commits, I still don't understand what kernel devs can do so far.

Just see the microp stuff I added to the file. Also I have updated the board files. See wats the difference between the files. A lot of updated code

hi charansingh,
i am willing to help, but i think it would be helpfull to define packets to take over.
By looking in the kernelsources it looks good to me, but i know from own expiriences with porting that i have to look deep...
best regards
trilu

charnsingh_online said:
Just see the microp stuff I added to the file. Also I have updated the board files. See wats the difference between the files. A lot of updated code
Click to expand...
Click to collapse
It's better to start/clone from pure CM 2.6.37 kernel, then add new commits when adding any new functions.
Would you please add a new commit when adding a new function?
Otherwise, it's very easy to lost the way in the source code.
A commit "Update some board files" doesn't tell the whole story. I want to know why to change.
Comparing the source code manually and guessing its function is not convenient for any kernel devs.
For me, I won't add any code in my 2.6.32 kernel until I know the meaning of the changes of the source code.
Thanks.

Ok I'll do it tomorrow n also maintain the list in the op

I may be wrong, but this thread is not supposed to become a bug fix request thread. It is aimed at developpers, so that they collaborate on a merging of HD2 specific stuff onto a cyanogen 2.6.37 kernel...
This would most likely result in the resolution of a lot of our issues, but in the mean time, [DEV] in the thread title means it is for devs only......

Keep this thread clean please.. there are only a select few devs who actually work on kernels around here. Let them use this as a way of communication to generate a complete kernel, then we can test it for bugs.
Very excited about the prospects of this, if you guys get a working kernel with all the new commits shoot it over and I'll test it out on one of my HD2's.

I looked pushed code and it's ok, at least for first few commits. But it needs some deep cleaning an optimization, also there is some bravo naming convention used in leo specific files. You should put this tree on gitorious so we can do more work on it, but anyway i will clone tree and do some cleaning and porting new stuff.

This could be of interest, and not too much off-topic.
This kernel: http://forum.xda-developers.com/showthread.php?t=966786
is being abandoned and it had some patches for performance that I think are valuable. It had linpack scores that can be achieved only with heavy overclocks on other kernels... The problem is, the source is being distributed by a .zip, no commits, nothing... the only way to get those would be to issue a diff with... something and guess where they are. Staying on topic, I've already adapted cm-kernel for another device so I think I'll be able to help when I get enough free time to spare.

D4rk50ul said:
Keep this thread clean please.. there are only a select few devs who actually work on kernels around here. Let them use this as a way of communication to generate a complete kernel, then we can test it for bugs.
Very excited about the prospects of this, if you guys get a working kernel with all the new commits shoot it over and I'll test it out on one of my HD2's.
Click to expand...
Click to collapse
Yes you are right. Unfortunately many threads like this one get's filled with off topic chatter, complaints etc. I will try to keep my eye on this thread so the dev's can communicate. If your not contributing to the DEV work on the HD2 kernel's, please don't post your wishes and thanks post as this will quickly clog up the thread. I'd hate to lose progress due to this. That's why many DEV's end up not using XDA and reverting to IRC only. Thanks
noellenchris

Hi,
Few days back there are some conversation about libsurfaceflinger.so for color banding issue http://forum.xda-developers.com/showthread.php?t=1012278 . Since Rom is changing continuesly with libs can we port the change for color issue.
HD2 GB-2.33-SENSE-2.1 LOCKSCREEN SENSE-3

tytung said:
It's better to start/clone from pure CM 2.6.37 kernel, then add new commits when adding any new functions.
Would you please add a new commit when adding a new function?
Otherwise, it's very easy to lost the way in the source code.
A commit "Update some board files" doesn't tell the whole story. I want to know why to change.
Comparing the source code manually and guessing its function is not convenient for any kernel devs.
For me, I won't add any code in my 2.6.32 kernel until I know the meaning of the changes of the source code.
Thanks.
Click to expand...
Click to collapse
tytung, has any1 of you done so? please let us know..

g30rg10u said:
tytung, has any1 of you done so? please let us know..
Click to expand...
Click to collapse
No, I didn't work on 2.6.37 kernel so far.
I didn't see that charnsingh_online added a TODO list in the OP.

Fried my laptop charger. New one on way. Hd2 arrived

[CM9] Kang's from Fuzz (Defy Porting)

Figured I'd make a new thread so Fuzz\Skankwitch ports and problems with them aren't mixed up in Quarx's CM9 thread. Helps keep relevant info and fixes for their respected rom easily available and findable. And to put Defy Porting in a centralized place (hopefully) All the relevant Defy Porting, especially CM9, is extremely scattered around here. I know, I wrote most of em. I'll post better porting guide eventually.
The latest build (0616) looks like its gonna be pretty awesome since it merges in even more of Linaro build environment. If you don't know, in a nutshell, Linaro is a new toolchain to compile CM9 with fixes and optimizations to the build environment that allows the compiler to use exotic flags, which in turn makes software run faster.
I'm off today and tomorrow, so I plan on starting that Aroma installed Kang in the next few hours. If you've never build a rock wall, they're a pita and will wear you out, especially when you're alone and the rocks are 200+ft away and you push them in about 260-300 pound loads (slightly) up hill to the wall -- damn I missed having the truck that day. Each rock weighs between 60-180 lbs, and I weigh 180 btw. For you metric guys, multiply by 2.2 to get the kilo version, provided my weed math is correct (~2.2 kilos a pound).
Once the initial framework is done, weekly updates won't be that hard to do since it will only be replacing the core rom and updating a few mods that affect system files (volume step, pdroid if it'll patch).

(reserved for later)

Updated:
here's a port I just made: http://www.sendspace.com/file/hh74un (June 28 FuZZ)

Looking forward to the port with the aroma installer. Hopefully linaro is gonna make our devices more smooth. Thanks skeevy!

corvx said:
Looking forward to the port with the aroma installer. Hopefully linaro is gonna make our devices more smooth. Thanks skeevy!
Click to expand...
Click to collapse
Not sure if its Linaro or the build.prop tweaks I did, but the roms feeling really smooth and hardly any lag -- even when opening the app drawer. Base rom and tweaks are done. Currently going over the scripting and changing it as needed, and it needs quite a few since it started as GB Miui, adapted and extended for V4, and now being used for CM9

Almost done with the scripting. I plan on doing a test install later this evening.
Also working on a deal to get a $40 Defy + shipping -- has a cracked screen, but my Bravo's cracked screen is worse Hopefully the deal is able to go through -- seller is in Australia and my online currency is Pre-Paid Visa.
Any Australian Bravoers able to help me out and pay for it for me and I'll hook ya up with an American Pre-Paid Visa #, with it comes full access to the American Market...It's only $40+ shipping. Seller doesn't know much about pre-paid cards, so I sent more info on them, hopefully I'm over worrying about it and the pre-paid card will work.
I plan on getting a Defy or Defy+ as the "upgrade" to my Bravo. Yes, I know that they're the same phones, but I want a damn torch flashlight, 720p recording, and a Gingerbread kernel with 4 Vsel's.
If this doesn't work out, I'll just get one off ebay in a few weeks.
What sucks is doing a GiS for Defy on shopping leads to a few scam sites selling them (Defy) for $120 -- you're lucky to find them on ebay for that price.

skeevy420 said:
Almost done with the scripting. I plan on doing a test install later this evening.
Also working on a deal to get a $40 Defy + shipping -- has a cracked screen, but my Bravo's cracked screen is worse Hopefully the deal is able to go through -- seller is in Australia and my online currency is Pre-Paid Visa.
Any Australian Bravoers able to help me out and pay for it for me and I'll hook ya up with an American Pre-Paid Visa #, with it comes full access to the American Market...It's only $40+ shipping. Seller doesn't know much about pre-paid cards, so I sent more info on them, hopefully I'm over worrying about it and the pre-paid card will work.
I plan on getting a Defy or Defy+ as the "upgrade" to my Bravo. Yes, I know that they're the same phones, but I want a damn torch flashlight, 720p recording, and a Gingerbread kernel with 4 Vsel's.
If this doesn't work out, I'll just get one off ebay in a few weeks.
What sucks is doing a GiS for Defy on shopping leads to a few scam sites selling them (Defy) for $120 -- you're lucky to find them on ebay for that price.
Click to expand...
Click to collapse
Glad to hear that you are upgrading, please dont stop developing for the Bravo. Looking forward to your realease. I tried syllogyking's release, and battery life is amazing, even wifi tethering is working. With all the scriptings you are adding and modifying I can only expect it to be smoother and better. Thanks.
On a side note: I'm not australian, but I use a local pre-paid visa, to buy online on the US, I use paypal though (ex. transfer from the visa to my paypal account).

corvx said:
Glad to hear that you are upgrading, please dont stop developing for the Bravo. Looking forward to your realease. I tried syllogyking's release, and battery life is amazing, even wifi tethering is working. With all the scriptings you are adding and modifying I can only expect it to be smoother and better. Thanks.
On a side note: I'm not australian, but I use a local pre-paid visa, to buy online on the US, I use paypal though (ex. transfer from the visa to my paypal account).
Click to expand...
Click to collapse
I'm not gonna stop, that's the whole reason I want to "upgrade" to a Defy.
I'll try and make it a point to finish the rom by tomorrow evening -- I have things to do tonight.
I did have an idea hit me yesterday -- an aroma installer that contains only the bootloader, our baseband, a few mods, and does basic Defy Rom Porting. It would be a Bravo repair, mod, and porting tool to make it easy for noobs to use Defy roms w\o the hassle of having to port it yourself and be able to tweak whatever rom you're installing. The hardest part would be the build.prop, but I could include generic props for cm7, cm9, miui 2.4.20. Anyone interested in something like that?
After going to the Defy forums, I find it kind of funny that a lot of the posters giving help are Bravo usres....but it makes since since we need to know a bit more about the phones because we have to do a lot more digging around in order to get the roms working.

very good idea to use Aroma with Defy Roms.
I'd like to test it when it will be done.
Also I'm interested will KANG team accept Bravo for rom develompent ?
Unfortunelly CM, MIUI currently stopped

PsyClip-R said:
very good idea to use Aroma with Defy Roms.
I'd like to test it when it will be done.
Also I'm interested will KANG team accept Bravo for rom develompent ?
Unfortunelly CM, MIUI currently stopped
Click to expand...
Click to collapse
I put doing the actual rom on the backburner for the moment -- I only have time to for the one project now since I have things going on everyday IRL now.
I decided to do the recovery tool since, other than volume step mod, everything else in the aroma rom was universal and a port tool means users can update, have mods and tweaks, and not have to either rewrite or remod the rom for updates -- which occur every few days with Defy Skank roms.
The recovery tool is about 1\4 - 1\3 done.
Planned features include
Defy CM9, CM7, MIUI (GB) Porting
Bravo Greenbread Mod (for MS2)
Reinstall the kernel\devtree\bootloader
Mods for ICS and GB roms
Basic Rom Backup and Restore in Aroma
/data/app backup\restore (for keeping apps in between flashes)
andriod secure backup\restore
system\data\andriod secure\cache\dalvik\sdext wiping (all separate)
Bootmenu Fixes for all roms
Apps only available on XDA or other forums (or banned by google; only legal apps, nothing pirate)
Add init.d support to stock roms
Multiple touch recovery options ??? (a new cwm touch is being worked on, need to use and test it first)
build.prop tweaks
Multiple gps, wifi drivers and settings
init scripts for performance
custom overclocks
add multiboot support to roms
Maybe more??? Will take requests
Still have much to do, as I only have the basic aroma layout done. I still need to finalize the aroma layout, add in a few of the mods, write the updater-script, write the language file, test, test, and test again....
A few of the features I have planned have never been done or attempted with Aroma as far as I know, and may not be in the release (full system backup and restore); but they technically should work. I'm going to try and make the backups CWM compatible, but don't quote me on that, as the md5 scripting may be a pita to do for first release and proof of concept.
I quite surprised Quarx hasn't released an updated 9 yet, with all the updates his git-hub page has had over the past few weeks. I was hoping that he'd stay with the every 2 weeks-ish that he was doing up until now -- not a big deal since we're Defy porting again. I suppose he's just more interested in the Novo7 tablet than the Defy\Bravo roms for the moment. I'd like to hear his review of it, since a dev's review holds more stock with me than a random website catered to end users.
Not sure if the Kang team will accept the Bravo, never asked or even heard it brought up until now. If someone here has a Linux Build Environment setup, go ahead and ask them if they'll help get it setup to start building Bravo Kangs. You'd get better results offering to build it yourself versus asking one of them to do it for you. I might ask when this is done, but might not since I'd be able to run the roms w\o even having to edit the zip once this is finished -- just flash Defy Kang, run Aroma Recovery, port and mod the rom, reboot and enjoy...easy enough I think.

Can we have MIUIV4?

glucky said:
Can we have MIUIV4?
Click to expand...
Click to collapse
Easier said than done....the Defy Miui v4's that we port from are based on Quarx CM9 from March 08. The newer CM9's don't like to be the base rom for v4 porting. Miui v4 is based on pure AOSP roms, not CM9; where GB Miui was based on CM7 and more compatible with CM7 porting.
Since it only takes 30-40 minutes to port and see if it works, I'll attempt porting v4 with the latest skank rom I ported last night. Maybe it'll work, maybe not.
In the meantime, I'm about to upload the yesterday's skank slightly tweaked with 30 step volume mod, Motoinspired CM9 Theme, HWA Selector --- I also have the srs mod installed with it, but frankly, the srs mod has washy treble that I don't like so I'm going to remove it first. I should begin that upload in 40 minutes, with it finishing 40 minutes after that. BTW, the lastest Skank (0628) is really stable and battery efficient (I fell asleep lisnening to music, woke up 8 hours later with 65% battery -- 45% loss with wifi on, radio on, 2 hours web surfing on wifi, 8 hours of music, 6 reboots, full brightness, and installing 20 apps from google sync is very acceptable to me -- means I can listen to music while driving for 12 hour, have about 4-8 talk hours, and have that last for at least 2 days on a single charge.
EDIT: Call of Duty being played in the other room, need to wait for the bandwidth to be freed up before I can upload.
As far as the Port Project is concerned, I have the Aroma layout almost finished (just need to add in an install rom feature), its completely translated for English and ready for multilingual. The rest of the Aroma part will only take 5 minutes or so to complete, then its on to the edify scripting and shell scripting; followed by actual testing of the tool. If I had to guess, 50%+ of what I'm trying to do has never been done in Aroma as far as I know; and if they work as expected, you'll soon start seeing Aroma Roms that install from Nandroid Backups as that's a feature I know Walter79 and espaciosalter20 both want. Expect something in the next 4-5 days as all I really have left is a ton of edify scripting and shell scripts (around 20-30 shell scripts I assume).

Skankport 0628 (NOW UP)
Port to Bravo of Skank CM9 0628
Does anyone here still need install instructions???
--If so, feel free to look in any other damn CM thread, they're all the same
Gapps not included, so flash it as well.
30 step volume mod
Motoinspired 1.4 Theme
HWA Selector 1.5 Beta
Bravia Engine
Vibhinna 1.01 Beta (Multiboot Manager Reloaded)
Defy Apps Removed (Torch, Rom Updater)
DOWNLOAD HERE
I don't think that Bravia Engine is working with ICS roms due to there being no Bravia being mentioned at all in logcat output; you can see it loading on GB Roms; also my first time trying Bravia on ICS. Everything else, however, is working perfectly*. Before enabling it in HWA, Chrome actually loaded and let me enter an address, but only showed a grey screen instead of fark.com which did load....Chrome's almost there.
*Except for camera....

camera isn't connecting for me...when I tried making my own skank port based on your instructions, it didn't connect either. any advice?
also, sio wasn't present (only noop and cfq) according to no frills, so I flashed the droidx zip to get it

syllogyking said:
camera isn't connecting for me...when I tried making my own skank port based on your instructions, it didn't connect either. any advice?
Click to expand...
Click to collapse
Not as of yet....I do know the problem -- its not loading the kernel module correctly. I've already tried the Defy modules, replacing camera.kobe.so with a renamed camera.jordan.so, using the Kobe CM9 camera app, swapping init scripts with Quarx CM9...I'm kind of stumped for the moment, but I've only been at it for about 10 minutes now. I never actually tested the camera, just ported over like usual, which usually works.
I'm just hoping that there isn't a new step in camera porting....
For sio, I didn't fully tweak the overclock.sh like I normally do as a test to see if the scripting would work like its supposed to. Apparently it doesn't....You can remove the 2 governors from the DX zip and also remove the 2 insmod lines for the Governors in the init script to save a bit of ram....and the boosted governor works as well as boostedass anyways. I'm not sure what Epsylon did, but he did do something to it.
Perhaps a better option would be to ask Fuzz for some help in starting up a Bravo build environment. I've built my own CM7's in the past. I'd already be doing the same for CM9, but I've been getting sync errors every time I try to sync with Quarx's Bravo repo since he's been releasing CM9 (usually due to MotoMagic, then I fixed that and couldn't sync with Quarx's personal repo).
The building and compiling isn't hard at all, its just a matter of syncing the repo (which I can't do) and knowing how to use git (which I don't). I'll send Fuzz a pm shortly and we'll see what happens from there.
EDIT: PM Sent; Hopefully he'll help me out in setting up a Kang build environment.

Yeah, I'm fearing there might be some further tinkering that now needs to be done to get the camera to work again. Since Fuzz basically adds cherry picks to epsylon's commits (he pushes mostly tpruvot commits in git), I'm thinking all of this is going to quickly change. The reason being because epsylon has already stated that jelly bean is going to be ported to defy in a few weeks, and that I can believe. But because the camera app is further "improved" in jb, it might still require some more steps to keep us on pace with the "bleeding edge".
anyways, I wish I had the time to read up on Android dev and get started on git, but unfortunately real life is taking priority atm
thanks for the pm initiative. hopefully, fuzz imparts some insight.

Oh the fun fun world of porting never ends when you own a Bravo.
From what I've understood, Jellybean isn't that big of an update so I'm not surprised that they're doin it (and doin it and doin it well). I actually expect them to keep coding until the platform just can't handle the new software any longer without updating the kernel...

I figured out my github sync problems -- the manifest.xml linked to the bravo repo was out dated, so I switched it to Quarx's manifest.xml on his github and have now fully synced it with no problems.
I was thinking that if I was going to ask for help, I might as well try to build it from the repo first (or at least have it all on hand).
If all goes well it should compile in while I'm sleeping.:fingers-crossed:
I'm referring to CM9 & not a Skank Kang, btw.
EDIT: NOW COMPILING, time to smoke a bowl and go to bed.
EDIT2: Didn't compile correctly...
EDIT3: Think I found that problem as well, been compiling for 3+ hours now. Problem was I followed the Bravo ICS instructions to the letter & and they're now wrong. Using Quarx's Defy+ Instructions, modified for the Bravo, are working.
EDIT4: Successfully compiled CM9, going to test it in the next hour or so -- took over 5 hours to build.

My First CM9 Compile
Here ya'll go -- my first compiled CM9 rom. This is basically Quarx 0526 with an updated CM app base. Haven't tested it much, but camera works, it synced with Google and installed all my apps, and it hasn't FC yet. It doesn't have the new hwui.allow feature yet, as I'm still learning git and want to do this all in the proper manner.
Once I learn how to properly sync the Defy repo to the Bravo repo and not screw up the camera is when I'll start to be able to make Bravo Kangs.
DOWNLOAD HERE
Install as usual, gapps not included.
While I don't want to start doing too much too fast, I'd like to add in Pdroid support, use Motoinspired as the default theme (I really like it), add in what ever the Skank roms do, and maybe add in Paranoidandriod to the mix.
I've actually wanted to do this since CM9 was released but I got caught up with v4 porting that went nowhere, v4 Patchrom that's being a pita but getting somewhere albeit slowly, found some work, and finally got COD Elite. I'd post my gamertag, but I'm currently using my Dad's since my PS3 is out of commission for the moment (it fell out of my truck door).
/Dammit, all this has done is set my other project back a few days, but I think we'd rather have Kangs from Bravo source rather than a tool to port them from the Defy.....Anyone disagree with that?

Great works skeevy420 ...congratulation..

[Q] Kernel Source

I've been around these forums for over 6 months now, and we've all been anxiously waiting for the source code of ICS kernels. Everyone always says that it's not the OTA we want, but the kernel source. Even I have been really excited to get it... but recently I've been wondering... why? What exactly does the kernel source allow us to do? I'm not a developer by any means, but from the limited knowledge I have, these are the features the source will allow us to do:
- OC/UV without having to use Tegrak
- Custom kernels
What else? This post isn't mean to criticize or anything... I'm just genuinely curious how the kernel source will help us on ROMs. If you know anything, please post.

Kernel source gives us the opportunity to add a variety of things like:
OV/UV
More/different CPU Governors
A variety of I/O Schedulers
Different kernel modules
Support for more/different filesystems
And the big one we are hoping for with GSII is a fix to that dang ICS recovery bug! :/

MandaNick said:
Kernel source gives us the opportunity to add a variety of things like:
OV/UV
More/different CPU Governors
A variety of I/O Schedulers
Different kernel modules
Support for more/different filesystems
And the big one we are hoping for with GSII is a fix to that dang ICS recovery bug! :/
Click to expand...
Click to collapse
Thanks for the informative response. Yeah I was gonna mention the superbrick bug but I think developers found a workaround using TWRP and Agat's recoveries these days.
Sorry for being a noob, but what are different kernel modules?

Hahaha don't be sorry man, we are all noobs in some way! They did find a workaround for it, but they are also not sure that their workaround will work in 100% of all use cases. If you read their first post there is some worry about "super wipe" packages over-riding their safe binary.
A kernel module is a piece of functionality written after the kernel is compiled. It is compiled into what is called the module, and then loaded into the kernel. This allows developers to add bits of functionality without having to rebuild their whole kernel.

The kernel is like the motor that helps our phone run. When tuned properly, it will purr, give us good gas mileage and make the driving experience more enjoyable.
Sent from my SPH-D710 using XDA

Hahaha well that's one way of putting it! The kernel sits in-between the hardware and the software, and essentially enables them to interact together. I guess you could call it the middle-man, putting things into a language both the application's and then hardware itself will understand

Source code is the map to put the engine together correctly. Given enough time a dev might be able to build the kernel from scratch, but what's the point of driving yourself mad like that. Right now it's like they're tinkering with a demo engine but can't be fully sure that they're putting the parts in the right place.

It's more like all the parts to put the correct engine for your device together(The map would be the make files ). Right now they are using different parts from various different engines to try and assemble one that works for our "car".

Haha thanks for the responses. I forgot about this thread for some reason but I'm back to give you guys thanks And yeah I know what a kernel is heh but just the basics... I know basically next to nothing about development of kernels at least

Since is up I will add the all important to some of us reason. CyanogenMod9. I always knew I would one day ditch Samsung firmware for CM9 but i didnt know our phone would get it so soon. Once we have kernel source our developers will be able to write a proper CM kernel easier than it has been for developers like sbrissen to do one from scratch. Once that is done we can get rolled into official CM releases.
Other than PRL updates I am never going back to Stock firmware.

[Kernel] visi0nary's kernel alternative build | v1.6.1

Howdy!
I hereby offer an alternative build of the latest visi0nary's kernel.
The original thread is located here
Please note that the credits remain with BlueFlame4 (the maker of visi0nary's kernel), as this is the same kernel, just differently built.
Some years ago I spent many months trying to optimize UI smoothness and power consumption for a kernel of a different device, in which I succeeded.
From this time I remember some build flags and kernel config settings that improved (scrolling) smoothness and power consumtion for that device at that time.
So, in an attempt to do the same for the P9000, I re-built the latest visionary's kernel with the following differences:
different/improved build flags
minor changes in kernel defconfig
compiled using a self-compiled sabermod toolchain
With these changes in the build process I try to achieve the following things:
improved smoothness/snappiness of the UI (NOT higher benchmarks - I just want the user experience to be as smooth as possible, benchmarks do not really matter)
improved (lower) power consumption
The built kernel feels improved in smoothness to me, but this might be my own biased opinion.
Anyway, I would appreciate, if some of you good people could use this kernel as a daily driver, in order to see after a few days, if there are really any noticable improvements over the original build of visi0nary's kernel. Please report back in this thread, thank you.​
Installation: just flash in recovery - delete cache & dalvik cache afterwards (also in recovery, after kernel flash)
Attention: this build is not for cyanogenmod - it's for Stock P8000 ROM or other Stock-based ROMs like Eragon (I'm using it on the latest Eragon myself).
To verify that you are running the alternative build, you will see a "-gueste" (that's me) appendend to the kernel version number (see attached screenshot).

Thanks mate.
I will flash it to See if something is different/improved

Wish you all the best for this project!

Thanks Allways glad to see effort.
Testing will return with feedback.

Thanks for the kernel. I've just flashed it and so far I see that when you go directly to the battery menu from the notification bar, that menu is much snappier. On the stock and on visionary's kernel you had to wait a little bit to see the details of specific apps draining the battery. That's the feedback which I can say now, I'll try to give information about the power consumption in the future. Thanks for developing!

Thanks in advance at all.
For me so far power consumption seems to be very good (while it is not bad on the original build either). I'm anxious to see, how it will compare to the original build after 2 more days.

Hello! I have just fleshed the phone with this kernel. Seems great for now. Will update you for the power consumption in the near future.
P.S Im so happy that someone has taken over this project, and I hope it will keep you developing it!

boka18 said:
Hello! I have just fleshed the phone with this kernel. Seems great for now. Will update you for the power consumption in the near future.
P.S Im so happy that someone has taken over this project, and I hope it will keep you developing it!
Click to expand...
Click to collapse
Actually it is still BlueFlame4's project, as the changes I performed so far do not qualify for this project to be standalone. For now I only intend to make improved builds for visi0nary's kernel, but not my own kernel.
Making an own kernel out of this would include things like porting stuff to the kernel to enable new features - like SIO scheduler or "Snappy compression" for ZRAM, or even an enhanced kernel tweaking tool that allows the user to set additional kernel settings and tweaks in Android GUI.
But this is not the purpose of this thread/project

Stefan Gündhör said:
Actually it is still BlueFlame4's project, as the changes I performed so far do not qualify for this project to be standalone. For now I only intend to make improved builds for visi0nary's kernel, but not my own kernel.
Making an own kernel out of this would include things like porting stuff to the kernel to enable new features - like SIO scheduler or "Snappy compression" for ZRAM, or even an enhanced kernel tweaking tool that allows the user to set additional kernel settings and tweaks in Android GUI.
But this is not the purpose of this thread/project
Click to expand...
Click to collapse
Feel free - that's the spirit of open source! My P8000 is already on eBay so I'll visit this forum less and less. It's good to see people picking up my work though!

Stefan Gündhör said:
Actually it is still BlueFlame4's project, as the changes I performed so far do not qualify for this project to be standalone. For now I only intend to make improved builds for visi0nary's kernel, but not my own kernel.
Making an own kernel out of this would include things like porting stuff to the kernel to enable new features - like SIO scheduler or "Snappy compression" for ZRAM, or even an enhanced kernel tweaking tool that allows the user to set additional kernel settings and tweaks in Android GUI.
But this is not the purpose of this thread/project
Click to expand...
Click to collapse
I understand completely, but I DO hope that u will be able to continue optimising this great kernel!

What new in this kernel?
What the bug fix?

Okalash said:
What new in this kernel?
What the bug fix?
Click to expand...
Click to collapse
Pro Tip: Read the OP :laugh:

For me so far battery life seems to be very good.
After 2 days and 10 hours of uptime I still got 42% battery.
Now this value is not very informative, as it depends heavily on the usage of the phone.
Compared to the original build of the kernel at least power consumption seems to be better on my phone.
During phone uptime I occasionally played games (not very long though), was connected to bluetooth and wifi many hours, browsed through the web regularly and had only few and short phone calls. Over night for some hours I was in flight mode, while last night I wasn't.

Thank you for continuing the project! I flashed the rebuilt kernel because I had a "feeling" that the battery performance of the original Visi0nary kernel was somewhat lower than the stock kernel. (But maybe I am mistaken.)
So far I have no problems with the rebuild kernel. It is too early to comment on battery performance.
Does it make sense to run Skeleton's Seeder app (part of Eragon ROM) in conjunction with this custom kernel?
Moreover, is there any chance to port the P7000 kernel scripts that enable Android device encryption into this P8000 kernel/Eragon ROM? See http://forum.xda-developers.com/elephone-p8000/general/dev-cwm-elephone-p8000-t3200296/page11 The lack of device encryption is my main gripe with the P8000. Apart from that, I love this phone.

-Tiz- said:
Does it make sense to run Skeleton's Seeder app (part of Eragon ROM) in conjunction with this custom kernel?
Click to expand...
Click to collapse
This rebuild of visionary's kernel is feature-equivalent to the original build. So, yes, you can use the seeder app (I use it myself).
Regarding device encryption you need to understand that it has been left out of the ROM most likely on purpose, because this is a China-phone, and the chinese government is quite restrictive on encryption. And as Eragon (same as other stock-based ROMs) is based on the stock ROM, this feature is missing there as well.
This means, depending on the effort, Elephone made, to remove this feature from Android, it might be possible to reactivate it, it's just a matter of (testing) time.
I haven't tried with other ROMs like Cyanogenmod, but in theory it should work there.
As far as I have seen, the to enable encryption for P8000 stock and stock-based ROMs we would need to modify one or more scripts of the P8000 ramdisk (for example the russian guy you linked added in init.environ.rc:
Code:
export LD_PRELOAD libsigchain.so
And there are also a couple of other differences in the other rc scripts. It's not exactly clear (to me), which changes in the end are required for encryption to be enabled. Also we don't know if after these changes, the encryption option will magically appear in the device settings, or if we need to enhance the menu ourselves.
Furthermore, the russian guy mentions, that we might have to modify and rebuild the sepolicy binary file located in the ramdisk, in order to get selinux (security enhanced linux) to permit our changes (but I don't know if we would need that just for the encryption feature, as init.d already works for P8000 as opposed to P7000 - correct me if I'm wrong).
So to sum up, this sounds like a lot of testing, which I personally don't have the time for But maybe someone else does.
Don't take the Android encryption feature too seriously - at least not, if you are trying to hide from government. However, if you are trying to protect your data from normal people, it surely would be nice to have.

Stefan Gündhör said:
Tin order to get selinux (security enhanced linux) to permit our changes (but I don't know if we would need that just for the encryption feature, as init.d already works for P8000 as opposed to P7000 - correct me if I'm wrong). ...
However, if you are trying to protect your data from normal people, it surely would be nice to have.
Click to expand...
Click to collapse
Thanks. It is also my understanding that init.d already works for Eragon ROM. Therefore, I was hoping that it might be relatively easy to enable encryption. On the P7000, it seems that the menus simply appeared once the scripts were implemented. Wooster even talked about the possibility to make a "blind" patch for the the P8000.
Moreover, I agree that Android device encryption might not be 100% bullet-proof. However, it would allow me and others to sufficiently protect private email passwords and work-related data (e.g. if the phone gets lost or stolen). By contrast, the screen lock is no protection at all. In particular, if a custom recovery is installed ...
It appears that I am not the only P8000 owner who has a vital interest in device encryption:
http://bbs.elephone.hk/thread-6924-1-1.html#.Vow51hBukwE
http://bbs.elephone.hk/thread-9012-1-1.html#.Vow51xBukwE

Tonight I will download and test it
I don't care much about encryption, but God, I would pay for someone who could actually SOLVE the sub-15% sudden battery charge. Any chance you can look into/fix it, Stefan? You look like one of our potential hopes, haha
---------- Post added at 02:42 PM ---------- Previous post was at 02:41 PM ----------
BlueFlame4 said:
Feel free - that's the spirit of open source! My P8000 is already on eBay so I'll visit this forum less and less. It's good to see people picking up my work though!
Click to expand...
Click to collapse
Hi, sorry to ask but why exactly? Got a new/better phone? Got tired of the P8000 bugs/camera? In time, which phone did you get?
Best regards

Rizera said:
Hi, sorry to ask but why exactly? Got a new/better phone? Got tired of the P8000 bugs/camera? In time, which phone did you get?
Best regards
Click to expand...
Click to collapse
No problem, haha. Well, I bought this phone because I want to learn how to port CM or ROMs in general onto other devices and how Android works internally. Unfortunately MediaTek SoCs are quite beginner-unfriendly so I'll go for Qualcomm for now. Just got my Elephone Trunk btw Also there's basically zero "from source" development going on the the P8000 and it's not really fun to do all the things completely alone.
Cheers!

1.
Battery performance of the newly built kernel seems to be good. Heavy WLAN browsing still quickly kills the battery. But I could imagine that this is a hardware issue (power inefficient Mediatek WLAN modem?).
2.
"Also there's basically zero "from source" development going on the the P8000 and it's not really fun to do all the things completely alone. " Sad but true.

Announcing kernel "guestekrnl" (based on the latest version of visi0nary's kernel): http://forum.xda-developers.com/elephone-p8000/orig-development/kernel-guestekrnl-v1-6-2-t3287518