yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] maejrep:
Ladies and gentlemen...

it boots: http://xda.privatepaste.com/209bb8c85e

granted, there's a few errors :p but it initializes the panel, makes it past the 4-second mark, and even registers my attempt at rebooting (SEND+END+MENU). It should be all down hill from here. Anyone interested, I've been keeping my source changes on github:

http://github.com/jhansche/kernel-heroc-2.6.27
[Hero CDMA Android Development] alexthearmo:
You are the man! Make a donations page.
[Hero CDMA Android Development] justinisyoung:
wow... that is just amazing.

great work maejrep, donations coming soon!
[Hero CDMA Android Development] maejrep:
Thanks, I appreciate the thought, but I'm not interested in donations :)

However, if you insist: send donations here.
[Hero CDMA Android Development] maejrep:
Here's a current dmesg, booting with mtd partitions mounted, sdcard mounted, wlan module loaded (and working:

# ifconfig tiwlan0
tiwlan0: ip 192.168.0.108 mask 255.255.255.0 flags [up broadcast running multicast]

),

http://xda.privatepaste.com/823acedf14

Problems left:

* msm_fb timeout errors, makes nothing appear on the screen (after the initial "A N D R O I D" screen)

* qmi (evdo/data) not working:

<4>[ 161.680694] wds: 0020 @ 01
<3>[ 161.681365] qmi: wds: network start failed (001d)
[Hero CDMA Android Development] maejrep:
Hmm, i take that back... Looks like msm_fb does work, after it finishes booting into android. After the screen times out, I can hit menu twice, and I see the desktop.

Which brings me to the next item needs fixing: touchscreen is reversed (down/up, left/right axes are both reversed, but works well otherwise)

jogball left/right/up/down aren't working; but pressing (enter) does work.
[Hero CDMA Android Development] askwhy:
Keep up the awesome work! While most of the code references go way over my head, I have to say that it's been exciting and informative watching this thread (...your project) progress and develop.

I can't wait to see where it goes from here...
[Hero CDMA Android Development] maejrep:
Not sure what the deal is with msm_fb... It draws fine, just doesn't turn the screen on the first time you hit menu (lockscreen) -- have to press menu twice to unlock, then the screen will turn on. The system does wake up though, which is weird. And I can swipe across the screen to unlock, even though the panel is turned off. Once the lockscreen is cleared, the panel powers up and displays fine.

EVDO data is working, and fixed the flipped touchscreen axes. Problems left:

* fix panel issue

* fix jogball axes

Haven't tested:

* GPS (maps only displays the coarse agps circle, doesn't get a lock, but that might be because I'm inside)

* sensors: accel, compass, orientation, light sensor

Then moving on to camera
[Hero CDMA Android Development] wtphoto:
man you are awesome!!! great work. the entire community will be thankfull for this, it sounds like you are realy close.
[Hero CDMA Android Development] chuckhriczko:
*speaks to community* Everyone, meet the CDMA Cyanogen :)

Seriously dude good job and keep up the good work. Once I become employed (hint hint to anyone looking for a web developer :)) I will surely donate.
[Hero CDMA Android Development] quietcblongs:
Awesome progress, glad you're making so much headway!
[Hero CDMA Android Development] abcdfv:
Some so far in such a short time.
[Hero CDMA Android Development] beyondinferno:
Dude, I didn't check this thread for a couple days and now you're telling me you've almost got a full functioning kernel?

YOU ARE THE EFFING MAN!!!!!!!!!!
[Hero CDMA Android Development] maejrep:
Not only a (mostly-)working kernel, but I also back-ported msm_camera from the 2.6.29 kernel into this 2.6.27 code base. I haven't done extensive testing with it yet, and haven't tried actually running the camera app to see if it works, but it does compile, and it does find the camera, and create the correct device nodes in /dev/msm_camera... So far, so good.

Of course, the jogball is still an issue, and toastcfh has been playing around with it and finding bugs here and there. All in due time.

I'll push my msm_camera changes to github when I'm finished.

# ls -l /dev/msm_camera
crw-rw---- system system 249, 2 2010-01-19 02:58 frame0
crw-rw---- system system 249, 1 2010-01-19 02:58 config0
crw-rw---- system system 249, 0 2010-01-19 02:58 control0

EDIT:

So close, yet so far :(

http://xda.privatepaste.com/174d7ae4ee

but nothing on the screen
[Hero CDMA Android Development] beyondinferno:
as chuckhriczko said, when i've got a job you've got a donation!
[Hero CDMA Android Development] cmccracken:
This may be jumping the gun a bit, but have you built without the debug options enabled yet? One of the main reasons I want the source from HTC is to build an identical kernel as distributed, and see what kinds of performance gains can be realized by disabling debugging. Removing kernel debugging would probably be counterproductive to your efforts at this point, though. :)
[Hero CDMA Android Development] maejrep:
It's not fully working yet, as mentioned above. So it's not "identical" to distributed (for that, I need the identical-to-distributed kernel source :p). And yes, I have a lot more debugging code enabled than what the phone shipped with :D I even hard-code the restart-reason to be "recovery" so every reboot, whether caused by a kernel panic or rebooted gracefully, sends you back to recovery.
[Hero CDMA Android Development] mrinehart93:
Wow. You truly are going to be the next Cyanogen... maybe better than him! I hope you getting this kernel to work(note I didn't say if) comes off as a big "eff you" to HTC. Who needs HTC's generic crap responses (and poor copy and paste skills from that one message) when we have an awesome dev like you who can fricking reverse engineer a kernel?!?! I <3 you... in a not-gay way haha. But seriously, I REALLY appreciate your work for this community :)
[Hero CDMA Android Development] Jwahlg:
I applaud your efforts,

You are truly remarkable and I hope to hear more

good news soon =)

Thank you for your time and efforts
[Hero CDMA Android Development] Tipharet:
I think its interesting how when I read a thread where a guy expresses gratitude, he has to cover himself by saying "not in a gay way".
[Hero CDMA Android Development] maejrep:
On camera..

logcat: http://xda.privatepaste.com/fa76f4f395

dmesg: http://xda.privatepaste.com/afbaddc1e7

Not sure why, but it seems like the problem now is the "app passed NULL surface", which seems to point to it being an error with the camera app...

I'll try a different app that can access the camera and see if it changes anything.
[Hero CDMA Android Development] mrinehart93:
Yeah I said that because I said "I love you"... whatever I don't care.
[Hero CDMA Android Development] abcdfv:
I love you. All of you. Some of you in a gay way.
[Hero CDMA Android Development] wtphoto:
your scary sometimes lol.
[Hero CDMA Android Development] abcdfv:
How am I scary?

I don't even think I've posted enough here for anyone but Flipz to know my personality, and that's just cause I help him out sometimes.
[Hero CDMA Android Development] wtphoto:
just playin man
[Hero CDMA Android Development] abcdfv:
lol. Well after butting heads with HTC for a while, "philip" finally got tired and told me to just contact corporate. Not a good sign for the source getting released, so keep up the good work devs!
[Hero CDMA Android Development] wtphoto:
LOL I just got the same response not more than 2 minuts ago.

keep up the great work maejrep we need ya.
[Hero CDMA Android Development] maejrep:
jogball works
[Hero CDMA Android Development] oxeneers:
do you seriously want more things not to work just so you can kick their ass and make them work? :rolleyes: you, fine sir, are a GOD among cdma hero men.

maejrep, keep up the good work. all i can say.
[Hero CDMA Android Development] gu1dry:
So that leaves what left to get working?
[Hero CDMA Android Development] mrinehart93:
Hopefully not much. But who cares, we have almost have a working kernel!
[Hero CDMA Android Development] maejrep:
It actually is a working kernel.

The only thing major that is not working on 2.x that did work previously (that I know of so far) is the strange issue where the LCD backlight doesn't turn on immediately when waking up the phone. It will turn on immediately after unlocking (you can even use the touchscreen to swipe and unlock, even while the backlight is off), and sometimes it will power on about a second or two after starting the lock screen. Haven't been able to track that issue down yet, except that I think it has something to do with the stock kernel having a "late resume" option, which the GSM source does not have (it does have the early suspend option though). There are other issues too, that are pretty minor for me at this point, but can most likely be easily fixed.

I've been running the kernel since I got it to a working/booting point, and only ran into one issue yesterday where the battery died unexpectedly while at work. But as of right now, about screen shows uptime of 18 hours, last unplugged 9 hours ago, and it's at 83%. Not great, but it's more than enough for my use..

Also, camera is not working in 2.x, but I believe that's a result of HTC's proprietary camera library not supporting the 2.6.29 msm_camera interface, and even then it looks to be only a minor issue that is causing it to fail when drawing the video buffer. Everything else about initialization, settings, powering on the sensor, etc, is all working up until the app tries to display the frame0 stream.

Bluetooth is intentionally disabled and I just haven't gotten around to trying to enable it again to see what kind of issues there are on that front. If we're lucky, it'll Just Work™ when I reenable it.

Multitouch is registering two key inputs as it should, and the linux input subsystem is delivering both events. It's possible that it's just a difference in 1.5 vs 2.x that is causing multitouch to not work in 2.x. I believe toastcfh said that multitouch did work in 1.5 with this kernel (haven't confirmed myself, and I may be remembering incorrectly).

If you do run into any issues that I haven't already mentioned here, feel free to open a ticket in the issue tracker on github.

So, if you're one who likes to compile kernels, feel free to checkout and compile. It's definitely a usable starting point for any kernel hackers around here. :)
[Hero CDMA Android Development] alexthearmo:
So have you basically reverse engineered the kernel that HTC is refusing to give us? Does this mean we can get 2.1 on our Heros now? How much longer do you think till you've got us a fully working kernel? I'll gladly donate once it's all done.

Thanks for ur answers!
[Hero CDMA Android Development] cteneyck:
can you put a tarball up on git hub?

thx
[Hero CDMA Android Development] wtphoto:
dude you are amazing. I just hope you can get the cam going, and we can get a fully working 2.x rom going.

I will gladly donate to you or to whatever charity you wish.
[Hero CDMA Android Development] maejrep:
Yes, everything that is different between the GSM and CDMA heros that is now working in this kernel was found by reverse engineering the stock kernel.

Have you ever used github? :D http://github.com/jhansche/kernel-heroc-2.6.27 -- "Download source" link in top right. Or, you can check out the source via git directly (which will let you track changes, via git pull as I update)

As for 2.1, I haven't tried it. But if I did, it would be AOSP and not with Rosie
[Hero CDMA Android Development] toastcfh:
just to confirm maejrep. multi touch is working in 1.5. the kernel is actually at the point that loxdevs gsm hero is. without the mods for ext4, .sqfs ect... it actually needs to be known that there gsm kernel has the same issues as maejrep's kernel in 2.+. they use for their 2.+ builds a leaked .29 kernel for the gsm hero. which from what i understand has camera issues with aosp builds. anyhow so yeah everyone owes this man some major props and thanx. he busted his ass to get this far.
[Hero CDMA Android Development] alexthearmo:
Woo! For a fully working 2.1 without rosie I'd gladly drop you $20...and I'm sure hundreds of other hero users would as well. Can u build it?
[Hero CDMA Android Development] abcdfv:
On the one hand I'm shocked there isn't a program somewhere that can just decompile the kernel. Hell, even Windows has software that lets you decompile an .exe.

But on the other hand, it being a Linux kernel kind of means you shouldn't have to decompile it.

*sigh*
[Hero CDMA Android Development] maejrep:
It's disassembled, which in a way is the same thing. Just that "decompiling" takes that assembly and turns it into pseudocode, which is often easier to read:

LDR R1, =0x3E8
MOV R0, #0
BL sub_0384

vs:

myFunc(0, 1000);

The asm can be turned into pseudocode, and hex-rays is supposed to be able to do that (even with ARM asm). But I guess it just doesn't work on a "ROM" type, cause the option isn't available in IDA. If anyone knows otherwise, I'd be happy to hear it :)
[Hero CDMA Android Development] abcdfv:
Man, I wish I spoke Greek so I could understand what you just said lol.

I'm more of a hardware guy myself. Never got very far into learning C++, or any other language for that matter.
[Hero CDMA Android Development] chuckhriczko:
I'm not the most knowledgable when it comes to compiling things as I am more a web developer but tried compiling the kernel and got this error:

Definitely confused on this one. Any ideas?
[Hero CDMA Android Development] maejrep:
NEONC shouldn't be enabled in the config. The repository has a working .config, so you should just be able to make, without doing a make *defconfig.

If you did replace the .config (git status will tell you), just revert it back to what was in the repository, cause that's a known good config.
[Hero CDMA Android Development] chuckhriczko:
Well that would make sense. I copied the config from my phone. Thanks for dealing with my silly question :)
[Hero CDMA Android Development] gu1dry:
@maejrep, So I'm assuming your testing this all with an AOSP build of Android, due to you mentioning that that the kernel would work for 2.1 but without Rosie. So my question is, which version of Android are you testing this with?
[Hero CDMA Android Development] chuckhriczko:
I don't know about maejrep but I just compiled the kernel and have it running with the AOSP 2.0.1 with live wallpapers rom I cooked up. Aside from the double touch menu issue he spoke of I can't tell a difference yet.
[Hero CDMA Android Development] cteneyck:
My bad kept looking for a daily, didnt even see the d/l link.
[Hero CDMA Android Development] maejrep:
I'm using the "HEROC21-Community-1.8" ROM currently, for my tests.
[Hero CDMA Android Development] justinisyoung:
http://developer.htc.com/

they finally made it available...
[Hero CDMA Android Development] jmhalder:
shoot, I broke the news a whole 4 minutes before you, I'd like to think my email prompted it, lol I just shot customer support an email earlier today... hopefully they learn from this and realize that theres a whole community of people that want to compile and modify their own kernel for personal use, and that they HAVE to.
[Hero CDMA Android Development] maejrep:
And this project is over :p
[Hero CDMA Android Development] gu1dry:
Now your mission, if you so choose it, is to either: A) optimize the code; B) port it to 2.6.29; or C) both. :p
[Hero CDMA Android Development] maejrep:
I've been working on both, back and forth, for a week ;)

I wonder if we should complain to them that they did not release the code

for the kernel that ships on the device

. This is most definitely modified. (you can even tell just by the build name: "heroc_ef05d31a"). *shrug* this is enough for me ;)
[Hero CDMA Android Development] aaron130:
QUOTE=maejrep;5425059]And this project is over :p[/QUOTE]

Great work anyways maejrep,do u build roms too? I'd really LOVE to see a 2.1 maejrep Rom!!! U really seem to know ur stuff extremely well!!! Thx anyways for all the time u put into this project, I'm sure I'm not the only one that says I truelly appreciate all urs and all the. other devs hard work here at xda!!
[Hero CDMA Android Development] gu1dry:
Awesome.

If you can compile it as it is & it work, I'm not complaining. Too bad I don't have the tools or the complete know how to compile kernel sources, or I would test it.
[Hero CDMA Android Development] tkirton:
Or, if you really want to get bold with it...port it to 2.6.31.
[Hero CDMA Android Development] Kcarpenter:
This source has definetly been modified since our phone shipped...Good to know its at least not a dead project. Doesn't seem to be the best documented stuff I have ever seen. Also, I can't compile it. Given I only tried for 10 minutes since I am at work... :D
[Hero CDMA Android Development] wtphoto:
yes they released the code but great work either way I have a feeling that even had they not you would have had it all set and ready to go very soon.

keep up the great work and thank you for all the time and energy you put into this.
[Hero CDMA Android Development] tkirton:
It's probably the source for the upcoming 2.1 update (I would suspect they would change the kernel in that update). That would make sense if they didn't want you to see the hack job they did in the original source.
[Hero CDMA Android Development] surrealbliss:
My theory is that when they read the above, they realized that they had to hurry up and release the kernel source or else be one upped... again.
[Hero CDMA Android Development] tkirton:
I was thinking the same thing earlier this morning. Don't want to be shown up by, in their opinion, a bunch of amateurs.
[Hero CDMA Android Development] maejrep:
Definitely not a 2.1 kernel, sorry to say. All the changes I made to get it working are in this code, so this is just a .27 kernel that has all the changes that it took me a couple weeks of reverse engineering to find.

And the major difference I see in the released code, and what was in the stock kernel, is that the stock kernel put in a hack to get the nav to work, using a function they wrote (fake_gpio_event_input_func()), which mimics the real gpio_event_input_func, but doesn't do any gpio work at all. And in this released code, they have instead backported the input changes from 2.6.29 into this kernel, so that that hack isn't needed. I thought about doing that, but didn't want to spend too much time on it.
[Hero CDMA General] fallinlove:
I am a chinese and using Sprint CDMA Hero 200.

Actually , ANDROID system is very international,after installed custom-locale.apk it supports not only WWE but also Chinese well.

Even in V1.5 stock rom ,after installed custom-locale.apk, user can chose language such as Chinese or Russian or many many else.

I can input Chinese,read chinese,use chinese software ….

The only unhappy problem is that when i was sending non-WWE SMS, it failed.

It is obvious that the fuction of SMS do not supports UNICODE.

But there is NOT a problem with other GSM android cell phone,such as DREAM or HERO or….

So i believe that it’s not very difficult to fix it on CDMA Hero. Just need a little transplant or rebuilt…

Who can do something with it.

Thousands of people are eager to this update.

Thanks in advance.
[General Questions and Answers] kamelus:
hi

i have installed the spb Mobile shell 3.5.3 and the default contact manager use the T9 system which is not easy for me, i want to replace this default contact manager by the iconsoft phoneex contact manager.

i dont know how to do to change the default link in the home screen to launch the iconsoft contact manager

see the attachement

thank you so much for your help
[General Questions and Answers] Ren13B:
I dont think its possible. There's a thread somewhere on this board specifically for spb mobile hacks so you may want to search around a bit.
[General Questions and Answers] kamelus:
replacing default spb shell contact manager

Hi thanks for your answer

i've searched on this forum about my question but the only thing i found is how to change the default sms manager not for contact manager

i dont think that it's not possible

any other person with any idea ?

thanks
[General Questions and Answers] Freeboss:
Well quite old post dunno if i should start a new one at SPB hacks-etc, but...

If anyone have done this would be great to help, SPB is quite amazing except the contacts crap app..Pretty worthless
[Touch CDMA General] vilord:
Okay, I finally cleaned up what I've been working on the past few weeks :)

New sqsh with tattoo senseui!

so this is senseui from the tattoo, so it runs at native resolution 240x320. I have not tested it at *any* other resolution.

I haven't done a lot of testing so I can't guarantee everything works... ie I think that bluetooth might be broken? who knows... other folks please post your experiences!

Please note: I *have* seen the whole thing crash due to WifiService dying on my vogue once... and I've also seen a hard lockup on the polaris once... not sure why or workaround, but it doesn't seem to be commonplace.

I use the tattoo.user.conf and I *don't* use rosie, and it runs nice and speedy... YMMV.

New rootfs that cleans up a *lot* of little things... you can now use the volume-down installer to *update* your nand partitions and back up your nand data! (you first have to have a the nand flash complete before this will work, and you need to use the rootfstonand with the updated rootfs)

Maybe I'll post some screenshots? who knows...

Everything is HERE

EDIT: Forgot the most important part... Credits!

This build is almost entirely from the Belgian HTC Click image posted somewhere out there. Lots of time was spent getting the RIL to talk to the phone application without crashes, but it seems somewhat stable now.

At my disposal I had donut and tattoo builds from enatefox, zenulator, plemen, and maybe a couple others.

Some bits needed to be swapped out to work, and that took the bulk of my time... oh well :)

I'll also give some creds to the folks over in kaiserland, but I'm not sure who (sorry).
[Touch CDMA General] nabicat:
Thanks muchly! Been beating my brains out trying to dyi a port of Tattoo and you've done all the hard work. Made my day, now I can go to sleep....
[Touch CDMA General] TheKartus:
Trying this out tomorrow. I'll write about anything I see. Nice job.
[Touch CDMA General] arleybarros:
Thanks Vilord

I'm a big fan of tattoo native resolution senseui.

testing.
[Touch CDMA General] vilord:
that is likely due to my new partition/nand management code...

What is your partition setup?

I'll poke at it in a few minutes
[Touch CDMA General] vilord:
I don't know what could be causing the bootup issue :(

I dropped in some debugs and catchalls that might help
[Touch CDMA General] arleybarros:
The faster!

This is the fastest version ever.

i'm using haret and no paritions, works perfect!

i wish i could put it on nand, but i'm using a NIKE and the NBH is for vogue...

NICE JOB VILORD!
[Touch CDMA General] larstnt:
Hi,.

Thanks vilord, this is the best build with sense that i have tried.

I have the mount system error the first time i try to boot it, the second time it boot without problem.

Im wrting this from this build :-)
[Touch CDMA General] vilord:
arleybarros: what is the state of android on NIKE at this point? Do you still have no vibrate?

all: I'm still not 100% sure why the installer's choking, but I'll poke it when I get home (I still need to partition the SD on my POLA200, so I should be able to see exactly what you see when I do it)
[Touch CDMA General] gjbnh:
Sigh, more user freindly

I really don't mean to sound a negative note, your hard work , along with the other devs is sooo appreciated and admired. But for the many newbies that are out here, drooling other the new toys you guys are providing, I would really like to see complete bundles, which are updated as needed, with maybe a version number assigned to each updated build. Because of the modular nature of the OS, it is far to easy to to mismatch components resulting is a royal mess, and a real bad taste for potential users.

Or am I just full of it?:D