yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] nickleby:
I think it was the toolchain. I used gcc 4.7 this time and it booted. (I was using gcc 4.9). Nothing new here (kernel fails to boot some times, camera works but preview is buggy, camcoder doesn't work, issues with USB, bluetooth seems to work, can't suspend the phone)
[Desire Android Development] resoto:
Good "news" but i have 1 small Q.Did you fix problem with cable detecting after unplug ?

Thanks for very good work for us desire. :)
[Desire Android Development] macs18max:
Issue we have in leo(HD2) is PM and bluetooth...

So regarding bluetooth, did you need to make any changes in the ROM side or ramdisk do get it work or did it work out of box..

PM for leo suspend and desn't wake up at all...
[Desire Android Development] nickleby:
It was a real quick test because the Desire is my main daily phone, I can't test it more until the weekend... I just enabled Bluetooth, the icon appeared in the status bar and didn't got any error, I haven't tested pairing a device or sending a file. I've used the ramdisk from nightly build boot.img
[Desire Android Development] macs18max:
Thanks for the info bro... I just wanted to make sure that the bluetooth in Leo was kernel issue and not rom/ramdisk issue... thanks alot
[Desire Android Development] macs18max:
[MENTION=1244844]nickleby[/MENTION]

Can you describe what actually happens when u mentioned that PM is not working?

When you suspend (without connecting to USB) is it dead completely or does it start but screen doesnt turns on?

Assuming you wont have any logs now , if you testing the kernel over weekend kindly upload kmsg.
[Desire Android Development] Saf98:
Anything fixed yet?
[Desire Android Development] :
Sure if something was fixed, we would know.
[Desire Android Development] Saf98:
http://androidforum.tytung.com/hardware-video-encoding-and-decoding-720p-video-playback-t100.html

I wonder if this will help?
[Desire Android Development] LaidbackNikez:
... No. The problem (as stated x amount of times before) is still the the unplugging/plugging of usb cable not being "picked up".
[Desire Android Development] dkstiler:
Indeed but i have seen your code about the power seems good !!

I wonder if it has to do something with the usb drivers of the kernel some not proper initialization of the usb chip :confused:
[Desire Android Development] Saf98:
https://code.google.com/p/qiss-me-bsp/
[Desire Android Development] LaidbackNikez:
pls stahp posting here....
[Desire Android Development] Saf98:
Sorry :p
[Desire Android Development] macs18max:
I don't know it this will help but take a look at this

https://github.com/android/kernel_msm/commit/d44455a0b838b1d691e63913f0b159552ac01803

https://github.com/android/kernel_msm/commit/5ca279bff7880df5284680c5f09984b86f511ad2

By the way. What does the kmsg say?

I have something like this on leo

[ 4.134216] [USB] CI13XXX_CONTROLLER_RESET_EVENT received
[ 4.134216] [USB] cannot enter in device mode
[ 4.134246] [USB] lpm = 0
[Desire Android Development] LaidbackNikez:
I'll have a look into that later this week (vacation \o/) - but I'm not really sure that the Desire has the CI13XXX (ChipIdea controller) which could be one of the reasons why it doesn't work properly.

What's even more weird is that the USB is recognized upon boot and it does charge, but after unplugging it when booted and plugging it back in will not fire of the desired events.
[Desire Android Development] karo222:
thanks for your work on desire,, hope you can do it soon

Just want to appreciate you
[Desire Android Development] Dragonji:
Instead of spamming just click "Thanks" button.
[Desire Android Development] yeahman45:
this project's dead in case someone haven't noticed
[Desire Android Development] LaidbackNikez:
Define dead? I haven't really given up on it but time does not allow me to dev.. Back when I was at uni I had all the time in the world. Nowadays, nope. Oh, I moved the sources to a private repo so the commits you see are from january while the latest are actually from June/July.
[Desire Android Development] chrmhoffmann:
What's the reason for this? Would be nice to publish them so that other people don't waste time. Don't get me wrong. You did a great job.

Chris
[Desire Android Development] Saf98:
Check the first post it will tell you.
[Desire Android Development] chrmhoffmann:
Hi,

i was just asking if there's a reason for not publishing the kernel work (LaidbackNikez said he has them in private repo).

Chris
[Desire Android Development] Saf98:
He is Still trying to get it work so that's why its not published yet.
[Desire Android Development] LaidbackNikez:
Well, the old kernel source without the later fixes is still out there. It only diffs one or two commits. And lets be honest, it's not like I got any help from the community on it so it really doesn't matter if it's public or private. Do you see any pull requests? Do you see any response to all the posts where I ask the community for help?

So to be honest, I set it to private for the time being cause I am sick and tired of everyone piggyback riding on my back.

(Marc and Noonamer does not count as the community, cause we were a team)

Edit; Once I release a public release I will also upload the latest fixes to Github.
[Desire Android Development] chrmhoffmann:
Sure. That's much appreciated.

There are not only people who try to benefit from others, but also potential contributors around. Once there's a certain hurdle taken, it clears the way for less skilled people (like me). We had similar issues with the nook tablet eg. once kuzma/hashcode sorted out the major booting issues, other people could help.

EDIT: It's quite sad that those devices have no contributors anymore. The desire was once a top device considered better than the Samsung Galaxy i9000. But the i9000 is still around and even an officially supported CM device (pawitp is doing an __excellent__ job). Would be nice to get the desire, its deserved attention. I don't have serial console, so this initial work is extremely difficult.

Chris
[Desire Android Development] ze7zez:
.

This may be a stupid question.

Why you just can not decompile the kernel from HTC to see how it works?

Is it impossible?

.
[Desire Android Development] LaidbackNikez:
Well, It has been booting for a very long time now (over a year now) - I did not use any serial console to get it there either. -- Still, no one has contributed. I get your point tho.

Once I get past the last "major" issue (which exists and can be fixed on the public github repo) it will be more or less ready for a public release.

TL;DR: Device has been booting for over a year now - No one has contributed.
[Desire Android Development] dvd777:
How to contribute? By doing some work on public hub or donating?
[Desire Android Development] Saf98:
Lol probably both idk.
[Desire Android Development] LaidbackNikez:
Work on the public hub :)

It's all there just fix the USB recognition

Edit: Old signature --

I do not accept donations anymore. I used to accept donations before I took my degree. (Some extra beer money - We get paid to study here ;) )
[Desire Android Development] Saf98:
This might be a stupid question :p

Is ur micro USB maybe broken like loose, that's what has happened to mine I can't charge my phone only in a certain way.
[Desire Android Development] kostelo:
So probably it is not that easy and obvious. ;)
[Desire Android Development] jukyO:
Well. Compile it, and load it to your Desire, and try yourself.
[Desire Android Development] Saf98:
kernel 3 wont matter for me anymore because my htc desires messed up as a tried resoldering the new microusb which now cant charge cos i dont think pins connected so yh.
[Desire Android Development] jukyO:
If you want, you can compile it, and I'll be more than happy to test it on my Desire.

Just to rule out broken HW on [MENTION=3678722]LaidbackNikez[/MENTION] phone.
[Desire Android Development] paulove:
I have tested it. I get the same result. And my Desire is working perfectly.
[Desire Android Development] resoto:
Did you saw better performance and smoothnes than on 2.6 kernel ?
[Desire Android Development] paulove:
Yes, I did see some improvement in speed and it was smoother.
[Desire Android Development] Saf98:
Wish I could test but bye desire.
[Desire Android Development] jukyO:
So only this usb s**t needs to be fixed. Come on devs. Nikez did all. Only this remains.

[MENTION=1263928]paulove[/MENTION], could you please upload a boot.img?
[Desire Android Development] paulove:
Sorry, I don't have a K3 boot.img.
[Desire Android Development] nickleby:
I've compiled this today. I haven't tested it, but it should boot on Evervolv's ROM.
[Desire Android Development] meo:
I have two desires. One for my children and now one for me. Because my actual smartphone is broken. I am surprised how good the Desire is ! A litle bit of topic. But im wating for the kernal
[Desire Android Development] nickolasemp:
Either I am doing something wrong or after a few minutes the system just hangs... Or at least the screen does.

Edit: Restoring the backup as we speak
[Desire Android Development] LaidbackNikez:
This is cause the fix for this is not on the public branch. But it should still allow devs to fix the issue w/ cable.
[Desire Android Development] nickleby:
Hello Niklas! Can you remind me what's the problem with USB? It was related with MSM72_OTG or something like that right? I've a couple of free weeks before I return to the university, so I might take a look over the Internet and see if I can find something and try it.
[Desire Android Development] Saf98:
It's when u turn the phone on with the cable in it charges but when u remove the cable And insert the cable again it doesn't connect...
[Desire Android Development] LaidbackNikez:
Hi!

Well first off; Currently the device uses the ci13xxx-driver like HTC Leo does. So first step is to to change the driver to use the msm72k driver.

I did change it to the msm72k drivers once but that did not help so I guess you have to tinker with it for a while.
[Desire Android Development] LaidbackNikez:
Agh for f sake. I got myself interested again. I'll work on it tomorrow after work. God damn it.
[Desire Android Development] Saf98:
Wish I could test it but desire charge messed up lol.
[Desire Android Development] jukyO:
You can move away from developing, but you cannot kick out developer from within yourself :)

Thanks buddy.

I'm in today in the evening if you need on the fly tests.
[Desire Android Development] vorticerosso:
I can test if you need.

But I need more info because actually I have installed super Nova ROM, and I use my desire for daily use.

Thanks

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Desire Android Development] jukyO:
Hint:

Is there a module in kernel which controls gpio switch? Which I guess control behavior of usb port in certain situations. Maybe to dig in that direction.
[Desire Android Development] LaidbackNikez:
Out of curiosity - Could you upload the defconfig you used?
[Desire Android Development] nickolasemp:
Maybe you should ask nickleby, as I just flashed the boot.img with fastboot.
[Desire Android Development] topgeardave:
I'm starting to learn kernel and rom development. Once I learn the basics and get used to it all I'll try and have a crack at porting this so yeah count me in, in a month's time I should be able to have a crack at this :)
[Desire Android Development] soodmanhar:
This thread is closed as it was boot dev but a copy paste :(
[Desire Android Development] Anon_1989:
I know someone working on dis
[Desire Android Development] noonamer:
who? working on what?
[Desire Android Development] soodmanhar:
Are you referring to sense 4 project.
[Desire Android Development] soodmanhar:
Are you referring to sense 4 project
[Desire Android Development] neXus PRIME:
You mean shaky was working on kernel 3.0, he was 80% done with it, but got distracted with all the trolling by noobs, anyways, @soodmanhar, dude, don't post here more, it's a dev only thread, I'll pm you if i get any news....

Regards
[Desire Android Development] Chaosz-X:
When İ'm back, İ will give Sense 4 and kernel 3.0 a shot ;) On holiday now tho until 5th of august
[Desire Android Development] Thömy:
Weren't you also working on porting the a 3.0 kernel? Didn't you also call for help? Did we ever see anything "working" from you? I can remember pointing out some "basic" issues when you finally showed your sources.

And furthermore you did not really understand the question. He was asking to get a log when the phone is stuck at the HTC splash screen. No adb, no fastboot and not responding to key presses. If you can answer this I will be seriously impressed.

You know... there are some people here who want to learn things. Who want to help. You have to start somewhere. Yes this here is no easy task. But do you know the feeling if you finally solved a problem you had for days? He is stuck for a while and asking for some people who have more knowledge to help him. Whats you problem with this?

Oh shaky... I don't know. Did he ever release sources? What is 80% done? He ported all the drivers but it just doesn't boot? Yeah... whatever.

I can't continue on this since my device had an unfortunate encounter with a car tire :). And I also was stuck getting the mmc and other stuff to work. I don't know the exact details anymore. But it was fun working on it while I made progress.

For those who said that noonamer should contact drewis / texasice. I was in contact with him and he sees no need in a 3.0 kernel since he already ported all the important drivers to the 2.6 kernel. If his viewpoint hasn't changed he won't help here because he is busy enough with the Jellybean work.
[Desire Android Development] noonamer:
thanks thoemy, for ur answer) ur help and also, for source, it's was made big work) I totally agree with your words
[Desire Android Development] Chaosz-X:
Last_kmsg doesn't return anything after a battery pull? Not sure anymore, but I believe it did. If not, my bad. Whether you saw anything working from me: I don't have to prove I know what I'm doing. Been there, done that for the Flyer. And what do you mean with 'did we ever see anything from you?'. I'm not claiming I can get this up and running within one month, nor am I calling noonamer a fraud or anything. All I want to say is that this might be a too big leap forward and he should reconsider if he wants to spend a lot of time in this, as it is very pity.
[Desire Android Development] Thömy:
No, unfortunately it is stored in RAM and the contents are lost when you pull the battery. There may be ways to store the log in persisted memory. But I never got anything to work.

I'm sorry and I apologize. I was just a little upset with your answer to his question. A bit rude if you ask me. I don't know the other work you did and only remember you from working on a 3.0 kernel for the Desire.
[Desire Android Development] noonamer:
today with shaky we make a lot of things, for now main problem in MMC, all other okay.

can look at last kmsg on github

Thanks for Shaky156
[Desire Android Development] marc1706:
It's unable to find the gp6 vreg. That define used to be in vreg.c but it seems like they moved it. I can't access my VM right now but you probably can find it with an ack-grep.

edit: They changed vreg.c in order to work with regulator API. For now I'd say just revert this commit and you should be fine:

https://www.codeaurora.org/gitweb/q...ff;h=0f1f2ac6ee5f461276f9d040e338f71f9bba5e30
[Desire Android Development] Ravens97:
@Thömy Shaky asks can you come onto the irc freenode #qsd-bravo?
[Desire Android Development] Anon_1989:
I can see this coming along very well :)
[Desire Android Development] topgeardave:
Is it close to booting?
[Desire Android Development] Anon_1989:
Shaky says farrrr from it, there's a tonne of stuff missing, he's done a lot to it but lots to go imo
[Desire Android Development] Anon_1989:
A lot of things fixed, but still few issues
[Desire Android Development] soodmanhar:
Is kernel3 includes sense 4 ics rom also or that is a different project. Sorry for lack of knowledge:confused:
[Desire Android Development] jukyO:
Hello,

Got this boot.img from [MENTION=6013588]code4bugs[/MENTION].

Maybe he can tell what defconfig he used to compile it.

Cheers!
[Desire Android Development] jukyO:
Niklas, do you have some news?
[Desire Android Development] LaidbackNikez:
You know better :P

No.
[Desire Android Development] macs18max:
[MENTION=3678722]LaidbackNikez[/MENTION]

Hey nikez. In bravo or leo board file (code below), I just would like to ask why is the starting physical address of pmem_adsp, pmem_mdp and pmem_venc at 0x0 and not as metion in board-bravo.h?? (If not using ION offcourse)

static void __init size_pmem_device(struct android_pmem_platform_data *pdata, unsigned long start, unsigned long size)
{
pdata->size = size;
pr_info("%s: pmem %s requests %lu bytes dynamically.\n",
__func__, pdata->name, size);
}
static void __init size_pmem_devices(void)
{
#ifndef CONFIG_ION_MSM
size_pmem_device(&android_pmem_pdata, 0, pmem_mdp_size);
#endif
#ifdef CONFIG_ANDROID_PMEM
size_pmem_device(&android_pmem_adsp_pdata, 0, pmem_adsp_size);
size_pmem_device(&android_pmem_venc_pdata, 0, pmem_venc_size);
qsd8x50_reserve_table[MEMTYPE_EBI1].size += PMEM_KERNEL_EBI1_SIZE;
#endif
}

Can someone explain?
[Desire Android Development] LaidbackNikez:
Huh?

If you look at, e.g. "PMEM_VENC_SIZE" you see that this value is gotten from; static unsigned pmem_venc_size = MSM_PMEM_VENC_SIZE; and this value is defined in board-bravo.h as "#define MSM_PMEM_VENC_SIZE 0x00800000"

Not really sure what you're asking?
[Desire Android Development] macs18max:
I'm not asking about the size. I am asking about the physical start address. I have highlighted in red in the code below

static void __init size_pmem_device(struct android_pmem_platform_data *pdata, [COLOR="Red"]unsigned long start[/COLOR], unsigned long size)
{
pdata->size = size;
pr_info("%s: pmem %s requests %lu bytes dynamically.\n",
__func__, pdata->name, size);
}
static void __init size_pmem_devices(void)
{
#ifndef CONFIG_ION_MSM
size_pmem_device(&android_pmem_pdata, [COLOR="Red"]0[/COLOR], pmem_mdp_size);
#endif
#ifdef CONFIG_ANDROID_PMEM
size_pmem_device(&android_pmem_adsp_pdata, [COLOR="Red"]0[/COLOR], pmem_adsp_size);
size_pmem_device(&android_pmem_venc_pdata, [COLOR="Red"]0[/COLOR], pmem_venc_size);
qsd8x50_reserve_table[MEMTYPE_EBI1].size += PMEM_KERNEL_EBI1_SIZE;
#endif
}

Shouldn't it be something like this?

#ifndef CONFIG_ION_MSM
size_pmem_device(&android_pmem_pdata, [COLOR="Red"]MSM_PMEM_MDP_BASE[/COLOR], pmem_mdp_size);
#endif
#ifdef CONFIG_ANDROID_PMEM
size_pmem_device(&android_pmem_adsp_pdata, [COLOR="Red"]MSM_PMEM_ADSP_BASE[/COLOR], pmem_adsp_size);
size_pmem_device(&android_pmem_venc_pdata, [COLOR="Red"]MSM_PMEM_VENC_BASE[/COLOR], pmem_venc_size);
qsd8x50_reserve_table[MEMTYPE_EBI1].size += PMEM_KERNEL_EBI1_SIZE;
#endif

EDIT:

Anyways I tried it in leo so and i get this all over the kmsg and it wont boot, so gues I'm wrong

<2>[ 14.024963] kgsl kgsl-3d0: |kgsl_mh_intrcallback| axi write error interrupt: 000000c0
<2>[ 14.024993] kgsl kgsl-3d0: |kgsl_mh_intrcallback| axi write error interrupt: 000000c0
<2>[ 14.025115] kgsl kgsl-3d0: |kgsl_mh_intrcallback| axi write error interrupt: 000000c0
<2>[ 14.025115] kgsl kgsl-3d0: |kgsl_mh_intrcallback| axi write error interrupt: 000000c0
[Desire Android Development] LaidbackNikez:
No, cause that function only RESERVES memory. The position is decided upon init.
[Desire Android Development] TonyStark R.I.P.:
Please keep the thread about Porting kernel 3.0 for DESIRE

:good:;)
[Desire Android Development] FeraVolt:
Much better (Y)

http://xdaforums.com/android/software-hacking/hack-overclocking-tuning-snapdragon-s1-t2883708
[Desire Android Development] spezi77:
O'clocking is a nice thing. And how can you help the Desire community with porting k3?
[Desire Android Development] Saf98:
This might be useful but for different device:

http://xdaforums.com/showthread.php?t=1049170

my HTC Desire XS using XDA Free mobile app
[Desire Android Development] macs18max:
using ci13xxx driver partially works on leo too. Like when I suspend the device and plug in the usb is doesnt detect. I have to resume the device manually and then it charges and shows connectivity.

Anyways I tried porting from some codes from board-qsd8k.c in msm/kernel 3.4 and enable msm7k_otg drivers. Seems like it initializes but I think I'm missing something. Still no connectivity.

Have a look at the kmsg > http://pastebin.com/QjKXKMnq

If you feel I'm getting somewhere I will push the codes so that u can refer and correct where I've gone wrong and hopefully get it working on desire.
[Desire Android Development] LaidbackNikez:
Well it certainly looks like you're getting somewhere. When using the 72k does it recognize the cable on boot (i.e charging on first boot)?
[Desire Android Development] macs18max:
Well no. USB drivers do not detect usb connected in msm72k.

However the battery charger detects when usb connected (shows notification on battery icon and notification led lights up) as leo uses dex interupt in the charger for detection. (in both case CI and 72k)

It's wierd if I use CI13 drivers, and If phy reset (assert/deassert ) fails usb drivers work, but the moment I fix phy reset, driver wont work. in CI saying it cannot suspend usb.

EDIT: [MENTION=932462]nikez[/MENTION]. If you are getting ulpi read timeout and ulpi write timeout with your msm72k version try assigning seperate memory space for otg.

Initially I had a lot of those ulpi read/write timeouts then I did the following and the driver somewhat got initialise to a certain extend.

In device-qsd8k.c changed this

static struct resource resources_otg[] = {
{
.start	= MSM_OTG_PHYS,
.end	= MSM_OTG_PHYS + MSM_OTG_SIZE - 1,
.flags	= IORESOURCE_MEM,
},
{
.start	= INT_USB_HS,
.end	= INT_USB_HS,
.flags	= IORESOURCE_IRQ,
},
};

In msm_iomap-8x50.h added this

#define MSM_OTG_PHYS 0xA0900000
#define MSM_OTG_SIZE SZ_4K
[Desire Android Development] blackpac:
Will that help...? http://xdaforums.com/showpost.php?p=55885907&postcount=142

Posted on HD2 forum
[Desire Android Development] walter79:
We have working 3.0.101 ION kernel for HTC HD2.

Maybe it can help desire devs.

maniacx source: https://github.com/maniacx/android_kernel_htcleo-3.0

walter79 source: https://github.com/walter79/android_kernel_htc_leo
[Desire Android Development] jukyO:
Isn't hd2 the same as desire? Chipset, cpu and gpu are equal.

[MENTION=2606832]LaidbackNikez [/MENTION], can you do your magic from this?
[Desire Android Development] Saf98:
Well everything is working I think except for micro USB which might be different to hd2.
[Desire Android Development] jukyO:
[MENTION=382340]walter79[/MENTION] [MENTION=2448361]maniacx[/MENTION]

Could you please check microusb issue on desire?

Any hints?
[Desire Android Development] walter79:
whats the problem with usb?
[Desire Android Development] spezi77:
[MENTION=382340]walter79[/MENTION]

USB recognition doesn't work.

Sent from my Nexus™4 ?
[Desire Android Development] jukyO:
To elaborate:

When usb plugged in in powered off state, and powered on, it is shown as connected. If plugged in when phone powered on, it is not detected as plugged in.

So detection of usb fails when phone powered on, but if plugged in and then powered on, works ok and detected.
[Desire Android Development] spezi77:
[MENTION=3678722]LaidbackNikez[/MENTION]

I have found a "hack" by maniacx in [MENTION=382340]walter79[/MENTION]'s project: https://github.com/walter79/android_kernel_htc_leo/commit/8f763b3c013444629c4492a0475cbb0276fe1c96

I know that you aim at the most appropriate and clean solution. But could you give it a try?
[Desire Android Development] jukyO:
[MENTION=3678722]LaidbackNikez[/MENTION],

This looks promising. Could you check?
[Desire Android Development] LaidbackNikez:
No, sorry. No time. Here's the compiled zImage w/ the eventual fix.

Untar the tar with the zimage, stupid xda does not let me upload zimages ......

fastboot flash boot zImage
[Desire Android Development] resoto:
Yeeeaaaa im waiting for feedback from users :D
[Desire Android Development] paulove:
Boots fine, but no cable detection at all. And if screen is of for more than 5 sec, it freezes with black screen. :-/