yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] LaidbackNikez:
Right, thanks for letting me know.

Well.. Urgh. I don't know what to say but I kind of lost the fix I did back in (?????) to fix the freezes. Sigh.

EDIT: I did not find the fix but I somehow managed to fix it manually again. 35 minutes of uptime, no crashes yet.
[Desire Android Development] spezi77:
Would you mind sharing your latest code? Maybe walter79 and I could be of help with fixing some stuff.
[Desire Android Development] LaidbackNikez:
Surely you can help without having that small fix? I'm basically just +1 commit on my private branch versus my public branch. The USB thingy does not need this fix.
[Desire Android Development] spezi77:
Uh ok. Then I will try it from your private 3.0-wip branch.

Which GCC do you currently use?

Sent from my Nexus™4 ?
[Desire Android Development] LaidbackNikez:
I use 4.7 - custom toolchain from a friend.
[Desire Android Development] spezi77:
I tried ev-linaro-4.9 but it did not boot. Will use 4.7 now.

Edit: With 4.7 kernel booted fine. After screen-off, phone freezes in with black screen (as expected). Unfortunately USB connection is not working with the mentioned hack by maniacx.

Good night! another day another finding..
[Desire Android Development] LaidbackNikez:
Strange! I had like 21 hours of uptime without it freezing yesterday (and the day before that)...
[Desire Android Development] resoto:
[MENTION=3678722]LaidbackNikez[/MENTION] did you report desire performance increase or better battery life than on 2.6.x kernel ?
[Desire Android Development] LaidbackNikez:
Too early to say and I haven't used my desire for years so I can't really say.
[Desire Android Development] spezi77:
Hi [MENTION=3678722]LaidbackNikez[/MENTION] !

It seems to me that with the kernel I have compiled from your branch, it does not even recognize usb upon boot. I'm not sure if that's only on Windows -- or if it just works fine on Linux.

Please allow me one or two noobish questions. What is the path you have chosen: CI13XXX- or msm72k-driver?

And where to get them from?

From previous posts, I assume that CI13XXX is already in place.

Cheers!
[Desire Android Development] LaidbackNikez:
That's strange. Works just fine with p2 and K3 on Linux.

Well currently we're using the CI13XXX-driver but I want to move to the msm72k-driver cause that's what the Desire originally used. To get em re-use old code or google for new :)

I don't check XDA very often so if you'd like to get a faster response I'd suggest you join/idle in #k3ftw on freenode.
[Desire Android Development] nickleby:
Don't know if this is useful https://github.com/PicoLegacy/andro...mmit/e0b99f435f847e2379c202a4067fd9b86d11104b is a commit for the HTC Pico to use HTC Desire S msm72k usb controller
[Desire Android Development] spezi77:
Hum, just by using msm72k in defconfig, I have observed a first sign of life. When I plugged-in the usb cable then the hw keys got enlightened and also the notification menu was sliding down a little bit. It looked to me as if it wanted to bring up the USB options. .But then the notification menu suddenly disappeared. So, msm72k should be the right path.. :)

Before (with CI13XXX) this did not occur.

Alright, if I find a little more time on the weekend, I'll get in touch with you on freenode.

P.S.: Thanks [MENTION=1244844]nickleby[/MENTION], let's see if it works out...
[Desire Android Development] spezi77:
Unfortunately, It was not the solution.
[Desire Android Development] nickleby:
:( I wished that could work... I remember I saw something about HTC Pico and Kernel 3.x and they were having issues with USB too.... Maybe you can check this out https://github.com/savvas1/htc_pico_kernel_3.x/commit/379115e9c0c75036c0ff638ddad531ab083dc4b0 and this post about something called "vold" http://xdaforums.com/showpost.php?p=36096255&postcount=280 that fixed the USB issue. They thought USB was broken in kernel side but it was broken in the ROM side since the ROM was build for kernel 2.6.x and not intended to kernel 3.x yet.
[Desire Android Development] spezi77:
Good points. I also think that it was just the first piece of the puzzle.

Regarding the 2nd commit, I have seen that we have the exact code already in k3. It only needs to be enabled in bravo_defconfig. *fingers-crossed*

The last point about vold.fstab sounds interesting. Maybe Niklas knows how to tune fstab for bravo? However, it sounds like a great idea to compile a ROM for k3… Thanks very much for your help!

I will soon continue..

Sent from my Nexus™4 ?
[Desire Android Development] resoto:
[MENTION=476929]Spezi[/MENTION] [MENTION=932462]nikez[/MENTION] any news ? :)
[Desire Android Development] spezi77:
Small update. ;)

Moving to the msm72k-driver did not bring anything good.

So, I decided to stick to CI13XXX-driver which at least brings up ADB and UMS options if the phone is booted with connected USB cable.

I tried lots of things.. and then finally got USB Mass storage to work. Thanks to [MENTION=1244844]nickleby[/MENTION], I looked into the HTC Pico k3 thread and found the solution. It only required to recompile the ROM with the corrected LUN file path: https://github.com/spezi77/android_device_htc_bravo/commit/73c60d3a01878f7bda0c8a6d99b36b95ae3c512e

But unfortunately ADB still does not work for me, neither under Windows nor under Linux. As I cannot take any ROM or Kernel logs I am not able to dig deeper atm.

[MENTION=3678722]LaidbackNikez[/MENTION], do you think that you could tweak vold.fstab or fstab.bravo in some way to cope with k3?
[Desire Android Development] nickleby:
Great! Maybe we need to deal with ramdisk to get adb working? I mean, playing around with files init.bravo.usb.rc and init.usb.rc... Check this http://xdaforums.com/showpost.php?p=36305210&postcount=396 and compare with Bravo...
[Desire Android Development] jukyO:
Do we have some update?
[Desire Android Development] spezi77:
Work is still in progress... Fixing USB is cursed. :silly:

Well, at least the HD2-devs helped me a lot, and I got ADB working. The trick is to modify the ram disk. Add this into init.rc below "on early-init":

# enable adb early
write /sys/class/android_usb/android0/iSerial 0123456789ABCDEF

I will upload a kernel as soon as it is reasonable for being tested..
[Desire Android Development] Saf98:
I may be able to test because I repaired the micro USB on the desire but Idk if the sim and micro sd is detected? So if that works then I can test otherwise I won't be able to root if I don't micro sd working...

---------- Post added at 07:20 PM ---------- Previous post was at 07:08 PM ----------

This might help but its for Samsung galaxy s + but I think they did something with ramdisk look near end post.

http://xdaforums.com/showthread.php?p=48718326

from my HTC Desire S using XDA Free mobile app
[Desire Android Development] resoto:
Maybe HTC Desire Z kernel van help with usb not detecting
[Desire Android Development] holi93:
Testing

Hi,

if you wanna some test i'm open for it. I have my old desire in drawer. I can test everything exclude sound(My speaker broken but Im going to buy one on ebay). I want to see old and best HTC Desire alive and with K3.
[Desire Android Development] TanmayTzara:
I believe you haven't been following the thread lately.

Development isn't currently active enough to benefit from testers.

Cheers.
[Desire Android Development] kostelo:
This project never lacked testers but developers to support it.
[Desire Android Development] Saf98:
Yh I fixed my desire now, so I'm available to test. Or atleast give me the link to the rom with k3 on it.
[Desire Android Development] Dragonji:
[MENTION=3678722]LaidbackNikez[/MENTION], [MENTION=5091819]spezi77[/MENTION]: Any news on this? :(
[Desire Android Development] spezi77:
Not really, maybe if time allows in a few weeks.

Sent from my Nexus™4 ?
[Desire Android Development] meo:
Something new ?
[Desire Android Development] jukyO:
No, unfortunately.
[Desire Android Development] Saf98:
this looks interesting looks, dunno it will helped might have already tried it?
[Desire Android Development] Dragonji:
Hmm, as I can see the K3 is somehow functional on HTC Leo? There are already releases with it: http://xdaforums.com/hd2-android/nand-dev/jan-02-01-2014-kernel-3-0-101-t2991489
[Desire Android Development] LaidbackNikez:
I've already worked with marc (the guy who actually got all of this rolling) on this, but I seem to have lost all interest in working on K3.
[Desire Android Development] Malk4ever:
Understandable, Desire is 5 years old, not many users left.
[Desire Android Development] maxens63:
But many users would be glad to have k3.:):D
[Desire Android Development] Saf98:
Yh because some people cannot afford new phones because of where there from so they want latest software etc.
[Desire Android Development] Dragonji:
That's alright, you've already done a lot on this matter.
[Desire Android Development] spezi77:
Hi everyone!

I believe that some of you have probably missed the great news about the awesome job done by Thomas!

We have a pretty stable K3 now!

Cheers! ;)

P.S.: I got it running on Kitkat, but not yet on Lollipop..
[Desire Android Development] nickleby:
Great news! Thanks to Thomas! Can you upload a zImage or kernel img to test? I don't have my Ubuntu partition so I can't build the kernel from his repo. :good:
[Desire Android Development] spezi77:
Ok. You could also download my new Carbon build which has it included.

Sent from my Nexus 4 :D
[Desire Android Development] nickleby:
I've tested it (though I'm using a custom Evervolv ROM) It's definetely a huge improvement. Do you remember what else needs to be fixed in this kernel? Perhaps now that the USB issue is fixed (the big headache of K3) [MENTION=3678722]LaidbackNikez[/MENTION] could take a look to the K3 again :laugh::laugh: (just kidding, but it would be great)
[Desire Android Development] spezi77:
USB reconnect is fixed. Also the freezing is gone. Despite of the noticeably higher standby power consumption, this kernel is ready for daily usage!
[Desire Android Development] LaidbackNikez:
Maybe... Maybe not? :D
[Desire Android Development] jukyO:
Maybe yes? [emoji79]

---------- Post added at 10:48 PM ---------- Previous post was at 10:37 PM ----------

@ths@justremotephone.com [MENTION=5091819]spezi77[/MENTION]

Is there flashable version of k3 kernel available to test? Or at least zImage?

Thanks!
[Desire Android Development] spezi77:
:eek:

I have a zImage for KitKat.. will upload it soon.

Edit: [MENTION=3598933]jukyO[/MENTION] here you are!

Sent from my Linux Ubuntu
[Desire Android Development] weslyr:
Unbelievable Amazing work guys!!! I'm really happy today as I never expected to see this news (i've been waiting on k3 forever as the wifi module in k2 doesn't work well in south-america region).

I applaud all involved for their persistent work and refusal to give up. The stuff that is going on here is

legendary

(revival of the HTC Desire in a way HTC and Google could never even dream of!).
[Desire Android Development] LaidbackNikez:
I actually gave up, so the credit goes to Thomas and Spezi for finishing it! (Ish, kernels are never really done)
[Desire Android Development] nickleby:
Which toolchain did you used to compile the kernel? Can you give me a link? I've made a new installation of Ubuntu in a USB flash drive and I'm trying to compile with linaro 4.7 but I'm getting some errors...
[Desire Android Development] spezi77:
AOSP gcc 4.7

<project groups="pdk,linux,arm" name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" remote="aosp" revision="refs/tags/android-4.4.4_r2" />
[Desire Android Development] spezi77:
Hey there,

I did a new build which has a few small improvements:

drivers: bring up more CPU governors

mach-msm: bravo: suspend fix (credits: macs18max and walter79)

mach-msm: bravo: power down fix (credits: macs18max)

msm: acpu-8x50: add 1190 MHz to scaling frequencies (credits: marc1706)

Enable audit to prevent error flooding in logcat (credits: walter79)

Here is a flashable version: http://www.mediafire.com/download/cd3ny88ucn54gtj/Flashable_k3.0.16-test-kitkat.zip - md5 fa9e903fc482978c23481404dbde4b6f

And here is my unofficial test build of Evervolv's Kitkat rom 4.0.0p2-turba incl. this kernel version: http://www.mediafire.com/download/px55haajtoh2pmc/ev_bravo-4.0.0p2-turba-test-k3.0-UNOFFICIAL.zip - md5 701bd4c9d5e5a7d13db154d2e6363cff

Special credits:
* Evervolv
* LaidbackNikez
* marc1706
* macs18max
* noonamer
* ths@justremotephone.com
* walter79
* everyone else who was involved but does not appear in this list

Please report feedback to this thread only -- at minimum include a logcat/dmesg.

I would be very interested if the battery life has increased for you in this version. *fingers-crossed*

Thank you and have a nice day! ;)
[Desire Android Development] jukyO:
Hi [MENTION=5091819]spezi77[/MENTION],

Flashing of turba ROM and gapps went ok.

Only thing is that once phone goes to sleep, it cannot be awaken by any way, battery pull out needed.

No logcat.

Others?
[Desire Android Development] mordesku:
Is there are some special instruction to flash this Evervolv? What version of recovery and hboot should be used?

EDIT:

Is this kernel will work with your kitkang 1.2?
[Desire Android Development] spezi77:
[MENTION=3598933]jukyO[/MENTION]: Strange, i didnt have this. Adb don't work for you? Is this only with the new version?

[MENTION=1928021]mordesku[/MENTION]: Traditional rom setup. Stock hboot or 250mb system. Enable A2SD before flashing gapps.

Sent from my Nexus 4 :D
[Desire Android Development] jukyO:
Yes, new version, haven't tried previous.

It is my mothers phone now,so cannot play much.

Will try to reformat sdcard completely and try again some time.
[Desire Android Development] paulove:
I have tried flashing the new kernel on top of the Carbon rom, but I am unable to boot it. I have tried with a clean flash of the rom too.

Log added.

paulove
[Desire Android Development] pix106:
same for me, i can't boot new kernel version.

Previous verison boots fine, but on first boot my phone got stuck on htc logo, i had to remove battery, since then it's been booting fine.

I had tried to fastboot boot zImage with previous version, i got stuck at htc logo too.
[Desire Android Development] spezi77:
Hey folks, please only use EV ROM for now. Purpose is for testing.. :D

Sent from my Nexus 4 :D
[Desire Android Development] paulove:
That I can support 100% EV rom is very good for testing. :)

paulove
[Desire Android Development] mordesku:
Tested it with kitkang 1.2, has same bugs like in ev. Tomorow when i will have access to my pc i will try capture some logcat or kmesg.
[Desire Android Development] spezi77:
BTW: In case your device don't wake up, you could try to increase the min. frequency a little.

Sent from my nexus 4 :D
[Desire Android Development] mordesku:
Increase min freq to 576 didn't helped. I can't capture logcat cause both my pc and laptop has xhci usb controller which don't recognize my desire correctly is there any solution for that? When phone freezes, after rebooting (removing battery method) no last_kmsg stays in /proc.
[Desire Android Development] spezi77:
Do you have also freezes using the first version?

Sent from my nexus 4 :D
[Desire Android Development] mordesku:
First version was plain zImage? If so didn't tested it yet.
[Desire Android Development] paulove:
I tried to increase min to 998 and that did nothing either.

I had no screen of freezes with Carbon K3 rom.

paulove
[Desire Android Development] spezi77:
Here is a new version. Tested it for a few hours.. no freeze until now.

I had to revert a change that didn't do what I have expected from it.

http://www.mediafire.com/download/daf60h9ml8nix1f/Flashable_k3.0.16-test-kitkat-150511.zip - md5 bfde0f014ad2b71860a873d2836331b0
[Desire Android Development] desireleß:
I wanted to flash it over Carbon 1.0 with 250/5/x hboot without success

Gesendet von meinem Nexus 4
[Desire Android Development] spezi77:
It is currently meant for evervolv ROM only. I will build one for carbon once the kernel is good for daily usage.

Sent from my nexus 4 :D
[Desire Android Development] mordesku:
Testing it on kitkang 1.2 result is 7 hours no single freeze. Well done sir :)

Edit:

Why device info shows less ram than on 2.6 kernel?

Wysyłane z mojego HTC Desire za pomocą Tapatalk 2
[Desire Android Development] spezi77:
About RAM, i currently dunno. Maybe it can be increased a little in a future version.

Sent from my nexus 4 :D
[Desire Android Development] senseii:
Installed it on the Turba Rom, everything is working great so far (half a day in)! You are a genius! Cheers
[Desire Android Development] paulove:
With this version I have no freezes, but my phone have turned itself of a couple of time without me doing anything.

paulove
[Desire Android Development] ze7zez:
Perhaps not everyone knows that the address for Evervolv ROM has changed. Current address is:

http://archive.evervolv.com/builds/nightly/

The last build is here.
[Desire Android Development] spezi77:
Please also share your observations on:

- how stable is your data connection (3g/WiFi)

- battery life (which CPU governor used)

Sent from my nexus 4 :D
[Desire Android Development] senseii:
Wifi is working great, stable with no cuts all day so far.

No random reboots or sleep issues.

CPU governor is ONDEMAND, battery life seems good so far although haven't been doing anything too intensive with the phone.
[Desire Android Development] mordesku:
Can someone on evervolv build chceck is gps is working? On kitkang 1.2 didn't work.

Wysyłane z mojego HTC Desire za pomocą Tapatalk 2
[Desire Android Development] paulove:
It is working on evervolv. Got 11 sat fix indoors, next to a window.
[Desire Android Development] senseii:
A quick update, the battery was at 75% at 00:30 and at some point it died, at 08:00 the phone was off.

Will try and keep an eye on the battery life today more, apart from that phone is super fast!
[Desire Android Development] quimbexa:
Tried flashing the image on top of turba. Mounts2sd activated: stuck on boot. If i try to flash the kernel before m2sd, it doesnt recognize de ext partition. Apart from that, no bugs found. But desire without m2sd is dealbreaker
[Desire Android Development] senseii:
I'm using a2sd without issues.
[Desire Android Development] quimbexa:
What are your configurations? Yyy?
[Desire Android Development] senseii:
config was yny

I've got loads of apps installed and all running fine and fast.

It's a 4GB sd card partitioned - 1GB EXT4 and 3GB Fat
[Desire Android Development] maxens63:
Had a try with the latest evervolv build, and flashed the k3.

Everything works untill I reboot the phone. I get stuck on the first htc logo.

Also noticed that the Evervolv logo animation is faster with k2.6, and slower with k3

I also use int2ext4 instead of a2sd.
[Desire Android Development] jukyO:
I saw that also. Battery pull.
[Desire Android Development] chrmhoffmann:
no space...

Hi,

I am trying to install, but I can't fit gapps.

Could you please post links to

- gapps

- a2sd

- hboot

that needs to be used?

Chris
[Desire Android Development] senseii:
I used the gapps from here http://archive.evervolv.com/builds/gapps/kk44/gapps-kk44-20131126-core.zip

a2sd is already in the ROM (you just need to install Terminal Emulator

hboot : Alpha Jelly (250/5/182) hboot
[Desire Android Development] stark_br:
Thx Spezi for tour hard work but for some reason when I flash the kernel over last evervolv or flash your turba version I cant access my SD card.

Have tried with different hboots.

Now I'm with the stock one and with all your recommendations.

Any tips or how can I provide any more information?

Thx
[Desire Android Development] ze7zez:
You will not have problems when you perform 9 the following steps:

1. no SIM in slot

2. install bravo stock hboot

3. partitioning your sd-card correctly

4. install 4EXT 1.0.0.5 RC9 and apply

5. wipe data/factory reset

6. wipe davik cache

7. install ev_bravo-nightly-2014.11.22-squished.zip (no reboot)

8. install Flashable_k3.0.16-test-kitkat-150511.zip

9. reboot now

Good luck!

----edit----

Tethering Fix

History solve the problem with wifi tethering briefly described here.

In this next letter [MENTION=3678722]LaidbackNikez[/MENTION] replied.
[Desire Android Development] stark_br:
Thx for the tips, but I've exactly those steps. The Desire is a backup phone and it doesn't have a sim card into it.

I started all fresh and still no lucky... I'll try again later as I spend a few hours trying to make it work.

Again, thx
[Desire Android Development] ze7zez:
You try to replace the SD memory to another.
[Desire Android Development] Saf98:
Works for mee took sim out so it boots if u don then it will stick at HTC logo.
[Desire Android Development] ze7zez:
1.

(ev_bravo-nightly-2014.11.22-squished.zip ) + ( Flashable_k3.0.16-test-kitkat-150511.zip ) = ( Does not work hotspot WPA/WPA2 )

or

(ev_bravo-nightly-2014.11.22-squished.zip ) + ( Flashable_k3.0.16-test-kitkat-150511.zip ) + ( Tethering Fix ) = ( Does not work hotspot WPA/WPA2 )

2.

(ev_bravo-nightly-2014.11.22-squished.zip ) + ( Flashable_k3.0.16-test-kitkat-150511.zip ) = ( Does not work USB mass storage )
[Desire Android Development] uriah18:
Hi, can this maybe help you with the tethering problem?

BTW, I also installed ev on my bravo without any problems. Also, I once had problem installing some ROM (can not remember which one) and it turned out to be faulty SD card. Using another card solved the problem.
[Desire Android Development] ze7zez:
Thanks for your efforts.

Tethering is not a problem.

WiFi tethering, it is a problem.

"tether_dun_required" refers to "Bluetooth DUN tethering".

Just in case, I checked.

There is no entry "tether_dun_required" in the database.
[Desire Android Development] uriah18:
I was reffering to WiFi tether. I had that problem and this solved it. Property was not in the db, so I had to add it. I did manualy using terminal.
[Desire Android Development] ze7zez:
Did you do it on ev_bravo-nightly?

(ev_bravo-nightly-2014.11.22-squished.zip ) + ( Flashable_k3.0.16-test-kitkat-150511.zip ) + ( "How to re-enable Tethering on KitKat" ) = ( Still does not work hotspot WPA/WPA2 )
[Desire Android Development] nickleby:
Provide a logcat. Remember K3 still needs further development, also Evervolv's ROM is build for kernel 2.6.x, things like UMS will not work with K3
[Desire Android Development] ze7zez:
The problem with hostapd is very old.
[MENTION=5091819]spezi77[/MENTION] certainly knows about it.

According to your wishes, I send logcat.
[Desire Android Development] spezi77:
It is not a kernel issue. This has to be fixed in the source code of the rom.
[Desire Android Development] ze7zez:
All ROMs based on evervolv have the same problem of lack of function Hotspot WPA/WPA2.
[MENTION=3678722]LaidbackNikez[/MENTION] pointed to the place where hostapd should be improved, but he did not. Do you spezi77 you know how to tweak the source code?
[Desire Android Development] spezi77:
Here is the fix for USB tethering: https://github.com/spezi77/android_frameworks_base/commit/5dfc11b2123f959bc1234c213c80fb99aa4e627a

Credits nickleby

Sent from my nexus 4 :D
[Desire Android Development] ze7zez:
Oh! We're talking about WiFi tethering, not USB tethering, not Bluetooth tethering. ;)