yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] spezi77:
First of all, it is not a bug in this ROM!

Thanks for reporting this problem, and sharing the link. Maybe it can be fixed in this way. As soon as I find a little time, I will recompile a kernel with it for you: http://xdaforums.com/showpost.php?p=45217857&postcount=18.

However, on a 2nd thought it appears to me that not everyone would like to have the proximity sensor disabled in their device. Maybe it would be better to compile a kernel mod which has this workaround and offer it as a separate download.

I am not sure how many ppl have this issue. Please let's hear your feedback on this thingie.

Cheers!

Sent from my Nexus™4 :D
[Desire Android Development] wq0913562:
Probably hardware related, yeah (proximity sensor).

I already tried to do what malaspina_speaking wrote:

But unfortunately it did not work :(.

So,

yeah, it would be nice if you could provide a TWRP flashable kernel with the change mentioned in that post from przemas_r. And if you would do it it would also be nice if you could offer a normal kernel as well in case someone wants to undo that change afterwards.

PS:

Using KitKANG v1.1, the Google Play Store says that the device would be incompatible with Mozilla Firefox for Android.

Do you know what could cause that?

It also did say that using the old KitKANG v1.0.

Installing Firefox via F-Droid seems to work though.

But the Google Play store says the device (HTC Desire) would be incompatible with Mozilla Firefox for Android and does not allow to install it.

Regards
[Desire Android Development] spezi77:
U should take Firefox.apk from somewhere and flash it manually by using ADB.

adb push firefox.apk

It is caused by play store policies defined by the app provider, which is Mozilla. They believe that our HTC Desire is stuck at Android 2.3 and thus cannot use this browser and its underlying frameworks, e.g. WebKit and webrtc.

Another workaround is to edit the device and manufacturer name in build.prop file under /system.

Sent from my Nexus™4 ?
[Desire Android Development] spezi77:
I have also baked a kitkang with Data2EXT.

Hope this is the desired solution to get rid of your memory problems.

Big thanks [MENTION=382340]walter79[/MENTION] for this hint!

Sent from my Nexus™4 ?
[Desire Android Development] Saf98:
Is there data1ext in lollipop?
[Desire Android Development] spezi77:
Kind of :D In Lollipop we use System2EXT-1 and Data2EXT-2.

Sent from my Nexus™4 ?
[Desire Android Development] ze7zez:
spezi77, I ask you to give the checksum of the file, as for previous versions.

Of course, this applies to checksum ROM files before they are sent to the server.
[Desire Android Development] kokumetto:
Installation aborted

I have tried several times to install KitKANG v1.2. Of course I have changed the hboot and recovery as suggested, full wipe and system format done. Now, the problem is, during the installation of the ROM I have this message:

Installing KitKANG

set_metadata_recursive: some changes failed

E: Error in /sdcard/cm-11-20150419-UNOFFICIAL-bravo.zip

(Status 7)

Installation aborted.

Now, what to do? Why appears this error?
[Desire Android Development] maxens63:
For me, everything worked perfectly.
[Desire Android Development] Saf98:
Try making a partition again.
[Desire Android Development] kokumetto:
I've found it!

There was a recovery problem, like it was a wrong one. I have flashed back a clockwork-touch recovery and again the suggested 4ext one and voila! It works now!
[Desire Android Development] spezi77:
Ah, alright! Hope you enjoy it now. :)

How's the performance for you? Any difference?
[Desire Android Development] kokumetto:
Flashing gapps right after the ROM, the system is very laggy, for me it's unusable. Without gapps, I think is OK even after installing several apps.

After flashing the gapps, again starts to be laggy. I've got not only FC-s, but several reboot during installation from PlayStore or even trying to turn the phone on. In the latter case the phone becomes unresponsive, turning on the button lights, but not the screen. After several tries the phone just reboots. Sometimes the phone looses the wifi, so I cannot even turn it on, just after a restart. Titanium backup 8 from 10 times give FC.

So I like this ROM without gapps installed :good:
[Desire Android Development] spezi77:
Which gapps did you flash?

Which SD do you use? Maybe it helps to repartition / format it.

Sent from my Nexus™4 :eek:
[Desire Android Development] kokumetto:
I downloaded the Pico modular gapps (~99MB). Should I try with spz_gapps-slim-20141202.zip ?

My SD card is a Class 10 card. Before flashing every ROM, usually I format everything, except fat32 on SD.
[Desire Android Development] spezi77:
On my device (class 6 SD) the ROM just works fine with Pico modular gapps.

After 1 or 2 years I have discovered that the overall performance has decreased. And after deleting all partitions on the SD incl. fat32 and making it from scratch, the performance was smoother.

Has anyone else this problem?

Sent from my Nexus™4 ?
[Desire Android Development] kokumetto:
OK, I will try ;)

Edit:

I have repartitioned my SD and now is much more smoother the system. Now I can use also the programs from gapps. So :good:

Thanks spezi77 !
[Desire Android Development] spezi77:
ze7zez, good point. done! thx for reminding me. :D
[Desire Android Development] Ro3son:
Is it worth switch to this rom from Carbon?

After few days of using it i'm facing with few strange things ( ie. slowly opening apps or automaticaly switch on gsm data after few minutes of deep sleep, and 5 sec. delay before call window apears) and I'm wondering, will be here the same situation...
[Desire Android Development] Gregor07:
Step-by-Step

Hi Spezi,

I am trying to setup my Desire from sratch on. Your steps:

- Rooted - done

- Hboot with at least 400mb on system. Get it HERE (420/5/12) - where can I find "step-by-step instructions" to install boot?

Regards,

Gregor
[Desire Android Development] spezi77:
Place the hboot entitled as PB99IMG.ZIP into the root folder of your SD card.

Then reboot to bootloader.

Apply the update and reboot to recovery.

Then format all partitions except for SD.

Now you are ready to install the ROM.

Sent from my nexus 4 :D
[Desire Android Development] Gregor07:
Thank you Spezi,

just to confirm that I have installed the boot loader correctly: When I go into the boot loader then the first line shows "AlphaRev LP-loopbk". Correct?

As a next step I did: 1gb - 4gb EXT4 partition on your sdcard. Use this guide.

Here is a problem if you look at the info:

mount point device size free

system mtd3 420MiB 418MiB

data ext4 1007,9MiB 975,8MiB

cache mtd4 5,0MiB 4,1MiB

mount point fs size free

sdcard fat32 14,1GiB 14,1Gib

Warning: sd-ext is not formatted!

To format sd-ext I went into: tools / wipe of format -> ext 4 / Format SD-Ext

Result:

Format sd-ext complete.

E: unknown volume for path (/sd-ext2)

This did not change anything. I still have Warning: sd-ext is not formatted!

How do I format sd-ext?

BTW: When I start the 4EXT Recovery Touch I get the message "the recovery hasn't been configured" ...

Solved: After installing a new hboot you will need to "clear storage". You find "clear storage" in the home menu of boot. With this the formatting of sd-est works.
[Desire Android Development] Gregor07:
Can you explain into more detail? What recovery are you using? I am using the Spezi suggests (4ext-touch-recovery-for-LP-loopbk.zip) in his download and I am running into the same problem.

Please ignore: Problem has been solved (see above post).
[Desire Android Development] mirabilos:
I just tried coming from CM7.2.0.1 and had the same problem. I've tried to do several things, in this order, which helped (note I had already partitioned the SD card with 4EXT at this point):

① Flash CWM Touch (because the non-touch one does not work) from fastboot: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-bravo.img

② Flash the recommended PB99IMG_LP-looback_420_5_12.zip (renamed to PB99IMG.ZIP) from HBOOT itself, reboot into HBOOT

③ Clear storage and reboot into HBOOT again

④ Boot into recovery, then flash the recommended 4ext-touch-recovery-for-LP-loopbk.zip from ZIP (*not* from fastboot!), then reboot into recovery again

⑤ In 4EXT, wipe → format all partitions (except sdcard)

⑥ In 4EXT, tools → wipe or format -> EXT4 → format sd-ext

At this point, 4EXT “info” still says sd-ext is unformatted, but I was able to flash cm-11-20150419-UNOFFICIAL-bravo.zip followed by pa_gapps-modular-pico-4.4.4-20150308-signed.zip (just barely, but I removed BkSync and CalSync via a gapps-config.txt file) successfully. Huh, weird.

Then I told 4EXT to power off. It told me it had a “USB brick” detected and whether I wanted to fix it. (Huh? First time for this, too.) I said yes, took the SD card to the computer, removed the files from the FAT partition after reviewing the pa-gapps logs, then reinserted the SD card and the SIM card, booted the phone. It's doing that now. We'll see how it goes.
[Desire Android Development] mirabilos:
Works, but I got video problems (flickering) occasionally (though they got better after a few days), it’s not responsive (e.g. pressing Home or Back often does not work in the first try, or Munzee takes a tap on an icon on the map as move instead) and sometimes slow, and the camera is extremely laggy (especially in Munzee).

Switched to ART just now, trying if that makes it better. Video problems are back after the initial reboot.
[Desire Android Development] iadegesso:
Is there someone that had the Wi-Fi Hotspot fully working with 4.4.4? With my smartphone the latest version that make me able to enable Wi-Fi hotspot and to obtain a connection to the hotspot is the v.0.9 of the ROM (i.e., the last 4.4.2 ROM).

Iade
[Desire Android Development] Gregor07:
It is unbelievable how spezi77 keeps the Desire running. The ROM works very well - hmm, sometimes it is a bit laggy due to internal storage on SD card. But hey - the phone is 5 years old and you can run the latest OS on it. Thank you Spezi! You are doing a great job!
[Desire Android Development] mirabilos:
Didn’t try the WLAN hotspot yet…

Lots of forced close with this, and the camera is extremely laggy in Munzee. Switching to ART only helps very marginally.

With CM7, basic functionality such as WLAN was less stable, but I saw less FCs…
[Desire Android Development] spezi77:
Camera preview has lags, everyone knows. ;)

It would be great if you could share concrete logcats which would allow to identify the cause for any FCs in your device.

I don't know if it works out for you, but wiping cache + dalvik cache seems to be remedy.

Sent from my nexus™4 ?
[Desire Android Development] mirabilos:
Ah, too bad ☹ this really affects Munzee.

Hm, tried that yesterday (took ages to boot afterwards), and the amount of FCs got less, but even the first few tries to start the Munzee application broke.

I’ll have a look into doing that then. Unfortunately, they happen “in the field” usually, as it’s a geolocation-based game, so I’m not normally equipped to do that, but I’ll try to reproduce things in the office.

Thanks!
[Desire Android Development] mirabilos:
Hrm. I just had a sequence of FCs while at home: several times Zee (Munzee's statistics app), then clock (which I hit by accident) and vx.connectbot (!) which I wanted to run in order to run logcat. The desktop background was the screen of vx.connectbot from before it crashed, instead of the wallpaper I set (one of the default ones, boring, but it was there). I did manage to get a logcat into a file and that transferred to my laptop, and attach it here.

I already tried various schedulers, switching to Art (slightly better), disabling “force GPU” (quickly reverted because even worse), disabling all animations (slightly better), wiping cache+dalvik (better for a few program runs, then back to the same problems), rebooting (sometimes better for one or two program runs, then back to the same problems).
[Desire Android Development] spezi77:
Unfortunately, the Desire has a very small sized internal memory, which is in general more appropriate for handling app/data.

But in order to allow you to install more than a handful of apps, some custom roms will store app/data to your SD card, like in this rom.

And here comes the point. I believe that your problems are related to having a "worn out" SD card. Heavy app usage means that the SD card will have to take a lot, and that after some time it could suffer from too many read & write operations.

In your case, you could try if things will improve by replacing your SD with a new one.

Sent from my nexus™4 ?
[Desire Android Development] bl0ndynek:
I go exactly same problem with this room. My card is class 10 and everything works but very very slow. For example I click dialler wait 3 seconds dialler open, click home button, wait 3 seconds dialler close.
[Desire Android Development] spezi77:
In that case the better choice for you is to stick to version 1.1 with normal hboot (stock or alpharev jelly).

Sent from my nexus™4 ?
[Desire Android Development] bl0ndynek:
I take some actions and now it is working, I don't know which one was the cure:

1. FIll whole sd cards with zeros using dd

2. Create 2GB instead 1GB Ext4 partition

3. Choose Nova dialler.
[Desire Android Development] Rminsh:
Hey [MENTION=5091819]spezi77[/MENTION]

Is there any chance to add these code (for camcoder and 720P) from this topic , to your kernel 3? i think there is a chance to fix video camera!

http://xdaforums.com/htc-desire/development/development-camcorder-720p-t2918585

And do you think we can get android 5.1.1 on desire??

Thanks!
[Desire Android Development] ze7zez:
You need to accept that 720p Camcorder with full A/V sync only works Sense ROM and kernel [MENTION=2841939]snq-[/MENTION]. It will not help the kernel 3 and [MENTION=5091819]spezi77[/MENTION].

Unfortunately.

.
[Desire Android Development] Rminsh:
I mean 720p playback and fix camcorder with any quality (it doesn't matter 720p or 480!)!
[Desire Android Development] Gregor07:
I understand the ROM is very slow because internal memory ist swapped to SD-Card. For better performance (but fewer apps) I wanted to switch to stock CM-7. But after installing the zip this does not start. My Desire stay on the white "HTC" screen. Does this have something to do with the EXT-4 partition? I was assuming that CM-7 was simply not using that because the OS is using ext-4 for swapping. Can somebody explain?
[Desire Android Development] Saf98:
Could be your hboot.
[Desire Android Development] Gregor07:
Thank you lilsafbig, could you be more elaborate? Why does another ROM, which does not use EXT-4, not boot?
[Desire Android Development] ze7zez:
You had installed ROM which required hboot 420/5/12 upload.

Simply CM-7 is not a reflash, because it needs a different arrangement of partitions on your phone.

You must restore partition stock ( bravo_alphaspl.img ) or cm7v2 ( bravo_alphaspl-cm7r2.img ).

More info here.

.
[Desire Android Development] T.E.C.H.N.O:
Wow! I'm running this ROM with an 8GB Class 6 SD Card (2GB EXT) and it's so amazing fast! Great job you have done, spezi! :)
[Desire Android Development] kriszg:
Hi! I just found my Desire at the bottom of the shelf. I am going to test this rom for a couple of days. :D

So far, so good! :good:
[Desire Android Development] mirabilos:
Thanks, they indeed improved (I ordered a new Class 10 8 GiB µSD card), but still nowhere near good. I believe that Munzee, Zee, and the new Munzee 3 beta just use functionality that eats up a lot of resources (CPU and RAM also come to mind), and they only work well after a reboot basically. (But then, as I use the Android not as phone but just as toy for those applications, and fallback geocaching, that’s probably ok.)

Interestingly enough, in the Munzee 3 beta, they use a 3rd-party QR code scanner, which lags much less. (Though everything else is smoother in the Munzee 2 app.)

GPS, or rather location, occasionally either lags or even refuses to use GPS in Fused mode (using µG Unified NLP with Mozilla for location and Nominatim for geocoding) despite enough satellites available (switching to Device Only gives me a good fix, but that one sometimes has other problems – though I ran for a couple of hours with Device Only yesterday without hitting them, so they are probably gone again, though I’ll probably experiment with one of those apps that allow keeping the GPS open even when no foreground app uses it). I suspect this all has to do with CPU usage, but without a Windows Taskmanager-like CPU usage indicator in the top bar, I can’t say for sure. Tried several CPU schedulers, though.

Another thing that appears to help is, between rebooting and starting the “hogging” application, to first start GPS Status (to download AGPS data and get a fix once), and then going to Settings → Apps and kill lots of running background processes and services like F-Droid and Messaging.

All in all, I do think your ROM gets the best out of the device (the stock 2.x just sucked, and the official CM7 build was much more crashy and lots of things didn’t work reliably or at all, including WLAN), and even now, ages later, you continue providing updates and user support here. A heartfelt thumbs-up from me (software developer myself, so I know the kind of effort this takes)!

Munzee have recently opened up an API, and a friend is considering writing a Free Munzee app. Maybe that would help (if it will be less fat than the official one), but he said something about HTML5+JS (which will probably be bad… Zee and Munzee 3 seem to be HTML5-based, which causes lots of problems and slowness AFAICT), I think a native app would be better.
[Desire Android Development] AndroidBeginNinja:
Can this work on desire 610?
[Desire Android Development] spezi77:
Nope.

Sent from my nexus™4 ?
[Desire Android Development] spezi77:
Hey desire folks,

make sure that you don't miss kitkang version 2, which includes the stagefright security fix and Kernel 3.0.16!

Have a nice day!

;)
[Desire Android Development] lindahl85:
The pb99img says bad file. Do you have another?
[Desire Android Development] spezi77:
No, please make sure that MD5 Sum of the downloaded hboot file equals: 87db671a5dd04611346aa900feaf1cf5

http://d-h.st/g4Bw
[Desire Android Development] mirabilos:
Unfortunately, we seem to have an md5sum mismatch:

80fd7c54d83c2e5addb24deedbb80639 cm-11-20150815-UNOFFICIAL-bravo.zip

Also, any good links to an upgrade procedure (relatively new to the Android world as user)?
[Desire Android Development] spezi77:
Uups, the md5 sum I have posted refers to the hboot (PB99img.zip) which is given in the 1st post: http://d-h.st/g4Bw

Which is the recovery on your phone? And also please describe steps that you were trying to do.
[Desire Android Development] spezi77:
I have copied most of the installation procedure from CarbonRom and also updated post #1. Please let me know if it has worked out for you.

Instructions on rom installation

General requirements:

- Rooted

- An hboot with at least 400mb on system. Get it from here: http://d-h.st/g4Bw.

- A 1gb - 4gb EXT4 partition on your sdcard. Use this guide to create the partition. Partitions made using other tools (CWM, Minitool Partition Wizard, etc.) will likely cause issues.

- Use this modified 4EXT Touch Recovery ONLY: http://d-h.st/PGVJ. Any other recovery version may cause issues.

Noob-friendly installation guide:

1) Backup your current apps incl. their data (use Titanium backup from Appstore)

2) Backup your current ROM from recovery

3) Install the new hboot via PB99 method (find hints on PB99 method below)

4) Boot into recovery and format all partitions except for SD

5) Install the new recovery via PB99 method

6) Boot into recovery

7) Do a full wipe

8) Flash ROM

9) Flash a GApps package of your choice -- my recommendation is the PICO MODULAR PACKAGE with proper DPI play services ~99MB: http://xdaforums.com/paranoid-android/general/gapps-pa-google-apps-roms-t3074801

10) Boot ROM and let it settle down (3-5 min)

Flash a recovery or hboot via PB99 method:

1) Ensure the integrity of the downloaded image by checking against the md5

2) Copy the zip file to the root of your SD card and rename it into PB99IMG.zip

3) Reboot into bootloader

4) After a few seconds boot loader will search the file and ask you to apply the update

5) Press vol up for yes and then it will ask you to reboot

6) Again press vol up for yes

7) Now hold vol down to re-enter recovery

8) Format all partitions except SD card

9) Before flashing a rom or sth else reboot the recovery to allow the changes to become effective
[Desire Android Development] mirabilos:
I did mean an upgrade method from the previous KitKANG ROM release ;) that shoud hopefully be way easier, right? I’m a bit unsure about keeping applications and settings and all, though…

---------- Post added at 01:34 PM ---------- Previous post was at 01:31 PM ----------

I mean, last time, flashing it was no problem as I had just gotten the device “brand new” (from someone else who did not need it any more), so there was no data to be lost or anything. But this time I invested a bit of effort to get things working… would hate to have to redo that.
[Desire Android Development] spezi77:
In case that you have had v1.2, of course you do not have to change hboot anymore.

In order to use the version 2.0 you should do a full wipe, as the ROM has been rebuild with kernel 3.

Just backup'n'restore your app data with Titanium before upgrading this rom. ;)
[Desire Android Development] mirabilos:
OK thanks, I'll look into recherching this Titanium thing then.
[Desire Android Development] 2be3_80:
Do I have to flash hboot if I have stock 2.3?
[Desire Android Development] mirabilos:
Yes, the specific version linked in the first post.
[Desire Android Development] yeahman45:
that's great! was searching for usb host also!

edit: misread lol no usb host :( but thx and great work anyway
[Desire Android Development] gajodafeira:
I'm using the first version of your ROM, and i'm loving it! The second release my desire don't boot :( I'm looking forward for new releases.

Thanks for your work.
[Desire Android Development] Temaki:
Had the same problem until I did a factory reset, or full wipe. Took me a while to reinstalll all the apps again, but now it works like a charme.

Hope this works for you too. The new ROM is much more stable. But I too look forward to more updates.
[Desire Android Development] showham:
Looks good and promising. :good:
[Desire Android Development] fifo:
Instalation aborted

Hi, didn't find such issue in forum, but when i try to install from recovery, I get: Warning: No file_cotextsE:error in/sdcard/Download/..nameoftheZIPfile..

Instalation aborted.

What am I doing wrong?
[Desire Android Development] ramnkc:
Delete

---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------

You need to update your recovery.... make sure you had S-Off your device before you do so.