yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] Visentinel:
Lastnight I downloaded 3 sense 3.5 roms to try using this kernel. Here's what I have learnt.

First things first, the biggy of it all....

That bloody modules file under init.d

Why can't people standardize the name of it OMG!

The 3 roms all used 02modules but this kernel pack for 2.6.35.1f used 02_modules

Flashing the kernel without first booting the rom for the first time and manually removing the original modules file would leave an unbootable rom.

Next, both dungphp and mikhei roms would work once cleaning out the old modules but the roms would stall and phone had to be reset when the cellular data just appeared.

I would provide dmesg if there was any clear info but unfortunately there was nothing of value, logcat would stop at any point it was up to doing normal things when the radio came up and cellular data caused the lock.

This likely won't happen to anyone else I'm afraid, unbenown to you guys the radio we all flash on our hd2 also contains within code for an Australia model of the hd2 that uses a different chip for use on 850mhz 3.5g (3G) cellular.:)

So I am cursed with inexplicable issues at time with hspa.

If the above info may help... then great but the kernel works great on my Aussie hd2 in nexushd2 rom so it is odd, under sense my data does work on 2.6.32 kernels so it's still kernel related somehow. Hope I didn't confuse you just then.

The 3rd sense rom was sensation XL, that one actually didn't boot on it's own stock kernel LOL so yeah.

Cheers.
[HD2 Android NAND Development] faldo:
Just wanted to tell you, Warrenb213 and the team that the development of this kernel is extremely appreciated. I'm a Sense 3.0+ fan, so hearing that EGL (or is it GLES?) is loading without glitches is something i, and i bet a ton of other thankfull users are longing for more than christmas!

Keep the exelent work up... btw, where do i send appreciation donations?
[HD2 Android NAND Development] bojanbl:
I manage to make 1f kernel to work on TeamBlueDroid Rom v2.1 but had to rename kernel module 01_modules to 01modules.

As I can test,

BT is working (I think, didn't have something to pair with it)

GPS is working

WiFi shows an error...

But I have glitches again with this kernel :(
[HD2 Android NAND Development] theslam08:
I did the same but it 'still' wouldnt work for me (same ROM). Bootlooped after the TBD boot screen. Did you install ROM, let it settle THEN flashed this kernel? I overwrote the files IN the rom resigned then flashed (maybe that was my problem?)
[HD2 Android NAND Development] redjama:
Just installed on typhoon and haven't had a single issue. Hadn't tested bt yet wont be able to till tomorrow when I get to work. No lag, fast, stable and battery drain so far so good.
[HD2 Android NAND Development] bojanbl:
I did unpack rom and replaced files in rom with kernel files and repacked rom again and that's it... Only I had to wait more than 20 minutes for installation...
[HD2 Android NAND Development] Visentinel:
Hehe i have done that to bojanbl but sometimes it don't work, i have no idea why sometimes my repacked zip causes clockwork recovery to go installation aborted.

Have you guys at all had any issues with rom freeze just after the phone signal appears? That's my real Showstopper mixing sense with this kernel:(

actually when it comes to affairs of the tcp/ IP it seems sense 3.5 has issues, like those Wi-Fi problems.

Could all be related.

Just another idea for the devs:) there's a filesystem called UBIFS, might be interesting to support it as it may show promise for speeding up the internal NAND performance.
[HD2 Android NAND Development] theslam08:
@bojanbl, that is exactly what I did. Very odd...

@Visentinel, "i have no idea why sometimes my repacked zip causes clockwork recovery to go installation aborted." That is because the ROM needs to be resigned (anything that is being flashed needs to be resigned). Follow this guide, it will set you up properly (you will have to register) http://androidforums.com/developer-101/8665-how-signing-roms.html or just search this site as I know there are guides on here as well.
[HD2 Android NAND Development] bojanbl:
Did you renamed module 01_modules in system/init.d/modules? I looked into my rom and in that folder stock one was named 01modules, so I renamed kernel's module 01_modules into 01modules and then did replace them...
[HD2 Android NAND Development] pyrorob:
um, clockwork mod has signature checking off by DEFAULT, did you turn yours on? the meta-inf folder which holds the md5 files, is only parsed for the updater script.

you pretty much need to make a new zip, any time you add/delete files from the zip, it potentially messes with it for some reason, and thats enough to break cwm.. and ive made hundreds of cwm zips and scripts..
[HD2 Android NAND Development] bojanbl:
I tried now to install fresh TBD ROM and right after installation applied original 1f kernel without changing module names and now I get WiFi working, battery drain ~5mA, no glitches...
[HD2 Android NAND Development] Kameirus:
can you post it please

Thanks
[HD2 Android NAND Development] bojanbl:
With WiFi and LCD on I get ~200mA battery drain which is suuuper since I had with stock kernel of previous TBD rom ~300-400mA. Also with WiFi on and LCD off I get ~70mA drain which is good for me ;)

Kernel 1f is attached... I must say that for now this TBD rom with latest kernel is perfect :D No graphic glitches, weather animation perfectly smooth, battery drain lowest as it can be, GPS working :cool:
[HD2 Android NAND Development] Dunc001:
Just no working camera yet, am I right?
[HD2 Android NAND Development] bojanbl:
Uuuups forgot to check that :(

Not working camera :'(
[HD2 Android NAND Development] daysey:
What of Bluetooth, did you test that too?
[HD2 Android NAND Development] zbeky:
Problem is that it works only on T-Mobile version of HD2. On EU it will restart while booting
[HD2 Android NAND Development] ceylin45:
MAG or cLK?

Thanks...
[HD2 Android NAND Development] bojanbl:
I manage to pair it with my laptop and to send file from laptop to mobile phone...

---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------

I am using MAGLDR...
[HD2 Android NAND Development] ceylin45:
I am using MAGLDR...[/QUOTE]

Thanks

I'll try clk...
[HD2 Android NAND Development] bojanbl:
Interesting thing is that Camera Fun Free is working?! I will stick with this latest 1f kernel and latest TBD v2.1 rom with Camera Fun Free since I like this ROM and this kernel without glitches :D
[HD2 Android NAND Development] anikolop:
Does youtube/videos play with 1f?
[HD2 Android NAND Development] bojanbl:
Nope it doesn't :( I get only whit screen... It appears that it is linked problem with camera and video...
[HD2 Android NAND Development] RCOO:
I think that f is not working with EU versions? Not mounting sd-ext... Am I right?
[HD2 Android NAND Development] marc1706:
If you are using an ext4 partition on your sdcard it should mount the sd-ext withouth issues.
[HD2 Android NAND Development] Dunc001:
Are warren's latest commits for the camera getting anywhere close to fixing it yet?
[HD2 Android NAND Development] RCOO:
How can I convert my EXT3 to ext4?
[HD2 Android NAND Development] Dunc001:
I'm pretty sure when you use Clockwork Mod to create/format your ext partition it is ext4. It's only if you formatted on your PC with Minitool or such like that you'd have ext2/3.
[HD2 Android NAND Development] RCOO:
Hmmm... I partitioned using CWM 3, not one of the latest versions, so I'm pretty sure it is ext3. I now have CWM 5... I will try partition again.

I'll convert using a ubuntu live cd...

EDIT: Just converted to EXT4, installed the rom, applied 1f kernel and the boot animation freezes and loops. Very weird.
[HD2 Android NAND Development] faldo:
When CW partitions your SD, it creats an ext3 partition.

Download http://coolexe.hostdevrom.com/Bravo/Extras/Alignment_Cool_2.zip and install it with CW, it converts your ext3 to ext4.

If you have an ext4 when installing a ROM, it more than doubles the installspeed.

Cheers
[HD2 Android NAND Development] isitokay:
Tried the kernel on TyphooN CyanogenMod 7 Nightly v3.7.2 MAGLDR, it boots ok, everything as described in first post, but still no G-Sensor for phones, which have this issue: http://xdaforums.com/showthread.php?t=1094578

Are you going to fix this or leave it as everybody does?
[HD2 Android NAND Development] Cheech1976:
Be polite please :) The dev´s are working very hard on this and have been doing so for quite some time.

To be honest, i see much too much activity from non developers in this thread, i think we users should leave this thread to those who actually participate in the developement of the kernel. Asking for support and receiving support is not intended to take place here.
[HD2 Android NAND Development] isitokay:
Sorry if my message seemed too rude, but i just wanted to ask, if fixing this issue is on the plans or no. If yes, i am open for tests and so on, if no, I'll just leave this thread as it is.

I dont say that devs should fix this problem right now, I know everything takes some time to do, just wanted to mention about the issue and sorry again.
[HD2 Android NAND Development] Visentinel:
You could use 4ext recovery:)

there's a Leo version in dorimanx roms mirrors it will work for all, you can't actually flash it you need to run it via your current cwm. You install it like any other zip but then it launches into 4ext.
[HD2 Android NAND Development] RCOO:
Nevermind guys. I managed to get the ext3 partition to ext4. The 1f version still gives me problem. It gets stuck on the bootanimation (middle) and restarts. 1e works perfectly (aside from the bugs we all know).
[HD2 Android NAND Development] warrenb213:
Wouldn't it be obvious that devs would work to address known issues. Its just finding time man.
[HD2 Android NAND Development] bojanbl:
I am not developer but I like to try new kernel and report problems with it so that dev's know about it and so that they can repair it and make it better ;)
[HD2 Android NAND Development] $t0Rm:
I know this was probably said but I got a issue with version f my Rom boots fine but then sense reboot and few mins later the whole phone reboots
[HD2 Android NAND Development] marc1706:
Please post your dmesg log. I don't have those issues with 1f so it is kind of hard to fix an issue I can't reproduce. ;)
[HD2 Android NAND Development] $t0Rm:
what command do i run to get the dmseg log as noobish as that sounds
[HD2 Android NAND Development] RCOO:
I'm having problems with 1f aswell.
[HD2 Android NAND Development] marc1706:
If you are using Magldr hold down the power button right after reboot. Then select services and "Dump DMESG to SD". It will dump the dmesg log into a DMESG.txt file on your sdcard.
[HD2 Android NAND Development] Visentinel:
Yesterday i released the first hd2 rom with this this kernel as its default kernel:)
[HD2 Android NAND Development] $t0Rm:
the dmesg came out blank on the sd i did a fresh reinstall of my rom and installed the kernel seemed fine booted up with 1f and then froze pulled battery and now seems to work fine.... i think its magic:eek:

Nvm it just froze again gotta pull the battery

edit here is a pastebin of the dmesg

http://pastebin.com/VLEC89kF
[HD2 Android NAND Development] marc1706:
Please test if this does not happen with 1e. That could help narrowing it down.
[HD2 Android NAND Development] RCOO:
I have the exact same problem. 1e works fine.
[HD2 Android NAND Development] Ambious:
The goods news: I managed to make it flash & boot by manually mounting System AND sd-ext before flashing (symlinking did the rest).

Also good news: Gradients that were blocky/choppy before are now smooth. Sweet :-)

The REALLY bad news: No phone signal whatsoever (wifi mysteriously works).

ROM in the sig.
[HD2 Android NAND Development] daedric:
You shouldn't do that. The "rom in the sig". Tomorrow you'll flash anotherone and the sig will update...
[HD2 Android NAND Development] Ambious:
True. Although lately I have been flashing the same rom over and over because I'm addicted to the RcMIX3D quicksettings mod and it's the only rom that supports it (so far)...

But you're right, I'll specify from now on.

Anyway, anyone had this issue of no phone signal? Any workarounds atm?
[HD2 Android NAND Development] DownloadMaster:
Wow! This kernel removes the color banding on Gingerbread. Great work guys!
[HD2 Android NAND Development] sbryan12144:
Hey guys, just wanted to report about 1f:

I had to mount sd-ext manually before installed to get it to work.

I installed on my RCMix3D Runny rom using sd-ext on MAGLDR.

What I found:

-Camera works, but has white screen (as expected)

-Color branding seems to be gone

-Glitches are gone

-Everything is smooth

-WiFi works good

-Any videos will send the phone into reboots though. I tried to play teeter and it rebooted constantly :)

Overall, good job guys. Keep it up. I hope to use this in my future Roms once the bugs with kernel are sorted out. Good luck ;)
[HD2 Android NAND Development] djsolidsnake86:
exactly

and in animated weather pro there is a little glitch in graphic videos
[HD2 Android NAND Development] daedric:
Anyone notice that Bluetooth works?

RCMix3D 4.0, e kernel version.
[HD2 Android NAND Development] ReynaldoH:
First impression with Typhoon 3.7.3 :It's really fast! Can't wait 'till the camera is fixed, excellent work.
[HD2 Android NAND Development] Tigermoto:
Wish I was smart enough to get it working on Coredroid V3 with ext on my EU. But it doesn't mount my EXT partition and then hot restarts when sense loads.

Promising work though guys, definitely subscribed to this thread.

Sent from my HTC HD2 Coredroid.
[HD2 Android NAND Development] vegaman:
I've noticed the memory mapping is a bit different to the 2.6.32 kernel, this gives a total of 404mb usable to android and 2.6.32 gives 411mb.

I'm cloning this now to test changing that and compare some other things to work out why this boots and my kernel doesn't. I'll share any changes I make to this kernel as well.
[HD2 Android NAND Development] MrPadie:
Morning all (at least, morning from my side).

Great work so far guys - really looking forward to this running prime time once the camera/camcorder/video issues have been ironed out. Other than those, this kernel is great!

I have a question though to those who have worked with it - does anybody know how this kernel has managed to clear up the color banding issue? Reason I ask is because I'm curious whether or not it can be ported back into the current 2.6.32 kernel in order to make our HD2 experience a little more enjoyable, at least until this kernel is put into action.

Thanks guys, keep up the awesome work!

MrP.
[HD2 Android NAND Development] thelonewolf_pav:
MrPadie,

I don't know if I'm talking complete rubbish here, but have you tried setting the rgb565 flag to 1 in build.prop?
[HD2 Android NAND Development] Rebel25:
To the Dev's

Hi Guys,

Just wanted to say thanks for the great work on this kernel. Can I ask for some feedback as to what you are currently fixing and if you are planning another release of the kernel soon? :)
[HD2 Android NAND Development] goldlocke:
this one?

debug.fb.rgb565 = 0
[HD2 Android NAND Development] MrPadie:
Thanks for the input.

Unfortunately it's not this, and I can safely make that assumption without even trying it. Here's why:

If I install this kernel on TyphooN_v3.7.3 CyanogenMod, the color banding issue disappears. However, the kernel install does not adjust the build.prop file to my knowledge, meaning its a fix due to the new kernel installation. Correct me if I'm wrong please.

Any other inputs?
[HD2 Android NAND Development] thelonewolf_pav:
yeah :)

it removes all gradients for me (obviously, our screens are 16bit) :)
[HD2 Android NAND Development] daedric:
That does not remove ALL bandings. Example, most widgets get a REALLY bad gradients, like Analog clock and music widget.

Anyone has a good list of what build.prop settings do ?

Example, debug.fb.* is (PROBABLY) something about FrameBuffer, but cannot be sure.

What about debug.sf.* ??

And all others?
[HD2 Android NAND Development] thelonewolf_pav:
Oh... So perhaps the kernel just ignores this flag and treats it as always 1 :)

OTOH, I have no idea whether we're talking about the same thing ))

I'm talking about the ugly greenish stripes that we have when there is, for example a gradient from black to white. With this flag set to 0, I have very visible stripes (call them banding or gradients or whatever), when the flag is set to 1, they disappear almost entirely...

---------- Post added at 08:40 PM ---------- Previous post was at 08:39 PM ----------

OIC. I'll try to install the kernel and compare :)
[HD2 Android NAND Development] daedric:
A good gradient is normally called when you cannot distinguish BANDINGS on subtle and progressive color changes.
[HD2 Android NAND Development] MrPadie:
@thelonewolf_pav - I'm not too sure what that build.prop setting changes, but it's clearly not the issue I'm referring to.

For example, load up any stock-themed Gingerbread ROM (Typhoon CyanogenMod, for example), and pull down the notification bar. That grey section at the top, by the power widgets, looks awful without this kernel, and represents what I've known to be the color banding issue. Install the kernel, and it'll clear it up.

So basically, I'm trying to track down what in this kernel has solved that issue, if anybody knows that is.

MrP.
[HD2 Android NAND Development] daedric:
This has been puzzling me...

Kernels.... at least for our HTC devices... come in two flavors.

AOSP/CM... and SENSE.

Now, this one, is compatible with both Sense roms... and CM roms. How has this been made possible?
[HD2 Android NAND Development] dimqs153:
Cant wait for the stable one...

Once this kernel stable i beleive hd2 become more powerfull android device

Keep up the good work mate
[HD2 Android NAND Development] warrenb213:
Thank HTC. :)
[HD2 Android NAND Development] 3dak:
some feebacks regarding the kernel 2.6.35 bravo GPU driver:

tested and confirmed it only fully works on HTC gingerbread Sense build without any camera issue. if it is used on CM/AOSP build, the camera will be no preview.

boxmax and I tested 2.6.35 gpu driver (with my kernel 3dak_R2.5/3.5) KERNEL on sense build and miui(CM) build, sense build is OK but miui or CM build is not OK for camera, no preview.

so an idea is to develop two branches, one branch is keeping the 2.6.35 bravo GPU driver and it only can be used on sense build, another is replace the 2.6.35 GPU driver with current hastarin8.6 GPU driver, this one will be compatiable and used for CM/AOSP builds.
[HD2 Android NAND Development] daedric:
So... there are incompatibilities. :D
[HD2 Android NAND Development] MrPadie:
Seems odd, as I still see people, using Mikhei777's Gingerbread, sense 3/3.5 ROM's for example, having camera issues using this kernel (or at least it's source as the base).

If what you're saying is that using only the GPU driver in our current kernel solves the graphics, speed and other issues while maintaining camera stability, then please share that kernel! :P

MrP.
[HD2 Android NAND Development] cyphol:
Wow! I don't know whether it's OOT or not, but yes, setting the "debug.fb.rgb565 = 1" do make all the gradients gone. Thanks man. :) It's clearing all the gradients on the Wifi Tether app GUI.
[HD2 Android NAND Development] stirkac:
hey 3dak nice to see this great progress! :D

mind if i ask you to publish these changes in zImage or commit to git? i've been testing 35 kernel since 1e image came out and i really miss camera..

and when i'm asking already, can you explain what is the difference in those 2 fullcompile scripts in source? and which toolchain should i use to compile?
[HD2 Android NAND Development] tobiascrystal:
WOW, I tried changing the flag and you are 100% correct. You can totally see the gradients are gone! The easiest way to notice it is on the xda app. The brown screen in the startup screen used to be blocky and now it is smooth as butter! That is the most used app on my phone and now it is so much better. Great find! I am curious if there is any drawbacks?

PS. This is like crack for sense roms! Everything is effected in some way you just have to look for it and trust me it isn't all in my head
[HD2 Android NAND Development] thelonewolf_pav:
none that I know of :)
[HD2 Android NAND Development] daedric:
Unless i'm mistaken, that setting enables dithering. The only drawback, is a tiny performance cost. To give you a picture, on a htc kaiser running @ 500mhz, we could not feel it :D
[HD2 Android NAND Development] ph03n!x:
If you are using CM7 based ROMs, Settings > CyanogemMod Settings > Performance > Use 16bit transparency (checked) (And reboot) will take away the "blockiness" of the XDA Apps startup screen - but the grey artifacts in the notification drop-down still remains. I will try the "debug.fb.rgb565" setting in build.prop later, but if I get it right, @daedric says that both do the same thing?

This is with the .32 kernel, BTW...
[HD2 Android NAND Development] ReynaldoH:
Hi, question, does that line have to be in a specific place? Or should I just paste it at the end of the build.prop? Thanks!
[HD2 Android NAND Development] daedric:
No no no... there's Surface Dithering and 16bit transparency.

They (should) affect different things, the dithering to images without alpha chan (no transparency) and the 16bit transperency to transparent or translucid images.

Meaning, Dithering should affect the XDA logo, 16bit transparency the top notification bar (if transparent on your given rom).

Still, with both enabled, though i notice a good diference, all my widgets still seem blocky and banding.
[HD2 Android NAND Development] ph03n!x:
That's strange. When I enabled 16 bit transparency and rebooted the phone, the gradient in the XDA App's startup logo disappeared. I used getprop to check debug.fb.rgb565, and I got a null value... Or maybe the XDA Apps's startup also has a transparency property?

I am now going to see if the gradient in the top (grey) part of the notification area, as well as those in the dialer screen's top part goes away with debug.fb.rgb565=1 (not immediately, later today).
[HD2 Android NAND Development] sbryan12144:
Good news guys. based on the work here, I fixed the camera :) it'll be in the next release of my RCMix3D rom :)
[HD2 Android NAND Development] tobiascrystal:
That is great news!
[HD2 Android NAND Development] MrPadie:
Sounds great!

However, I'd like to ask if you can please share this fix with the community/dev's of this kernel so that everyone can benefit from it. I understand you might prefer to have some exclusivity for your ROM for a while - it's only natural, but you'll be doing the community a big favor by sharing it.

Never the less, looking forward to testing it.

MrP.
[HD2 Android NAND Development] sbryan12144:
Absolutely man. I'll tell after I release. It's only going to be common sense hehe ;)
[HD2 Android NAND Development] MrPadie:
No worries, I wasn't implying immediately anyway. It's good to see you have that development attitude though, something many devs here lack.

Never the less, my F5 button will take some major suffering over on your thread now :P

MrP.
[HD2 Android NAND Development] daedric:
Still, individual/team cookers should give credit where it's due.

If someone uses RCTeam/Anyonelse fix for something, it not only common sense but correct ethic to credit the dev. IMHO opinion of course...
[HD2 Android NAND Development] warrenb213:
Why not contribute to the overall .35 movement here instead of boxing it up only on the RCMix3D build?

I mean, after all, this wouldn't have happened had it not been for the DFT and the extended network of HD2 Android Dev's..... :) I'd be curious to know what you did to fix the camera in the 35 rom? Did you just push in the DSP stuff as I was planning to do, orrrr? Or did you fix the camera in your 32 based kernel using stuff from the 35? lol.
[HD2 Android NAND Development] RCOO:
When you fixed the camera, did it fix Flashlight aswell?