yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] spezi77:
Nice, I feel glad that after all - 12 months of development - we (incl. especially ze7zez and other the people in this thread) managed to get the SlimKAT into a stable condition for our beloved device! :D

Hooray! And btw, many thanks to ze7zez for your donation(s), which I badly needed to buy small things (USB cable, replacement battery) for keeping my HTC Desire alive and my Linux build machine..

P.S.: my Google N4 has died a few days ago, well it is not really dead, but the proximity sensor is out of order! But my HTC Desire is still without a single HW related defect, except for the battery.. :D
[Desire Android Development] ze7zez:
It's never so good that it couldn't be better!

A small mistake:

Gallery -> click on the photo -> menu -> edit -> FC

Photo in 2015-12 version, it opens correctly.

-= Tests are ongoing =-
[Desire Android Development] senseii:
Thanx for the update, just wondering if I still have to download and flash the hotspot fix from first post or is it now built in to the rom?
[Desire Android Development] ze7zez:
It is built-in.
[Desire Android Development] FaserF:
Thank you so much for the update and even now keeping the old HTC Desire alive :)

It's not my main phone but still great to see having a phone with working Android 4.4.4!
[Desire Android Development] spezi77:
Thanks for sharing this.

Unfortunately there is nothing i can do from a developement point of view because the error comes from an "external" app: Gallery3d which is part of the gapps that has been flashed over the ROM.

Error log:

I/ActivityManager( 459): Displayed com.android.gallery3d/.filtershow.FilterShowActivity: +345ms (total +467ms)
W/ResourceType( 3574): Failure getting entry for 0x7f0d009f (t=12 e=159) in package 0 (error -75)
D/AndroidRuntime( 3574): Shutting down VM
W/dalvikvm( 3574): threadid=1: thread exiting with uncaught exception (group=0x4185bcc8)
E/AndroidRuntime( 3574): FATAL EXCEPTION: main
E/AndroidRuntime( 3574): Process: com.android.gallery3d, PID: 3574
E/AndroidRuntime( 3574): android.content.res.Resources$NotFoundException: Resource ID #0x7f0d009f

I could remake the slim gapps flashable zip and keep Gallery2 instead.

How about this idea?
[Desire Android Development] ze7zez:
I do not know if we understand each other well.

FC Gallery comes from a pure ROM without installing gapps.

To be sure, I attach logcat pure ROM, right after the installation and edit photos in the gallery.

I think that for each user is essential that everything worked just after a clean install.

The fully-functioning base should be ROM, and no extras.

Later comes the stage of modification and addition of the components.

How it will be done remains the responsibility of the user.
[Desire Android Development] spezi77:
Okay, first I didn't fully understand the scenario, but now I got you. ;)

I tried to reproduce the issue you mentioned, but I couldn't. This was after a clean installation and after I flashed the slim gapps mentioned in the OP. An btw, the gapps installation doesn't replace the Gallery2 -- that has been my wrong assumption.

I was able to open two pics in edit mode. One has been a screenshot and the other a pic I took with the camera. No problems until here.

Maybe the pic you are using has special characteristics or permissions. Are you able to reproduce it with your 2nd bravo?

Edit: also when I switch Jezyk to Polski, there is no FC.
[Desire Android Development] ze7zez:
In a moment I will repeat scenario on another bravo.

FC = Force Close

---- edit 1 ----

Wow! In the second edition of Bravo photo works well. What would that mean?

---- edit 2 ----

I already know.

It works well for 182 DPI. Changing to a 242 DPI causes FC.

The default DPI Bravo is 240 dpi.

Then there is also greater system performance because there are fewer pixels in the image in memory.

Is it possible to change it to make it well at 240 DPI?

---- edit 3 ----

After manually setting the DPI to 240 in build.prop file photo editing work correctly.

Where did the table-resolution settings in the Display -> LCD Density:

142, 162, 182, 202, 222, 242, 262

instead

140, 160, 180, 200, 220, 240, 260?
[Desire Android Development] spezi77:
About edit 3:

Good point, this can be done. I will set the default SlimKAT DPI setting to 180, in order to allow us to use the alternative sequence.

Anything else so far, any further FCs or problems, before I am going to make a new build? ;)

Edit2: Fixed. See https://github.com/spezi77/packages_apps_Settings/commit/b8e1efc7083fe15561855850c91ac826c3583839
[Desire Android Development] ze7zez:
Today, tonight I execute tests. I will inform when I'm done. I did not know that such small things can have such a big impact on the whole.
[Desire Android Development] FaserF:
Issues while installing the gapps

Had the Same issue with your Last Build from some months ago

See Attachment

EDIT1: issue persits even after a full new clean flash while following the instructions.

The crazy thing is that I have completely set up the sd card partition again and deleted everything in recovery and after flashing the new rom I had my old apps and old settings from the old version??

In terminal while trying A2SD I get an error.

Any idea?
[Desire Android Development] spezi77:
Hey folks,

While testing the latest builds, I have noticed that there were 3 new items that should be added into the slim gapps package. Otherwise you cannot use the latest G calendar app.

Google Play Services 10.0.84 (030-137749526)

Google Play Store 7.2.13.J-all [0] [PR] 138561921

Calender 5.6.8-140599650-release

So, I just compiled a new zip and shared the download link in the OP.

Have fun! ;)
[Desire Android Development] FaserF:
Thanks for this! :)

Any idea for my issue above?

And btw when trying to change the usb connection from charging to mass storage i get system ui has crashed. But maybe this is an issue with my buggy installation?
[Desire Android Development] ze7zez:
1. Gallery2 can be closed when saving a file or when long image manipulation.

2. Display -> Daydream -> Colors

When Daydream wakes up, it is closed, but not always.

I did not check VPN, ie because I have such a possibility.

The rest is working properly, in addition to what did not work from the beginning, wakeup options: trackball wake and volume rocker wake
[Desire Android Development] spezi77:
It could be your buggy installation. On my end USB mass storage has worked fine. Only that it sometimes takes ages to turn it off again.
[Desire Android Development] spezi77:
Nice, thanks for conducting tests. I will check the logs and see whether stability can be still improved.

Edit: wifi hotspot works now, right?
[Desire Android Development] spezi77:
Which are the commands you entered when trying to install a2sd? Anything different from what is mentioned in the OP?

To be honest, I do the initial setup with a2sd and the Gapps installation a little different.

A2SD install -> y n n.

Then I reboot to recovery and flash the Gapps.

This will save a little time.

;)
[Desire Android Development] ze7zez:
WiFi tethering is working properly.

After correcting and before the release of the new ROM, you should check the operation of editing Gallery2 at least 180 DPI.

It would be extremely nice if also worked at 240 DPI.
[Desire Android Development] spezi77:
It seems that daydream stopped just as a coincidence. The real cause is that DashClock widget is no longer present in the ROM.

Edit: Nevermind. I have found the place where it has to be removed: https://github.com/spezi77/android_frameworks_base/commit/c1a205e686c5a6c10c12230bccd0d46117fb6783

Error log:

E/KeyguardHostView( 511): Error when trying to bind default AppWidget: java.lang.IllegalArgumentException: not a appwidget provider: ComponentInfo{net.nurik.roman.dashclock/com.google.android.apps.dashclock.WidgetProvider}
W/ResourceType( 511): CREATING STRING CACHE OF 120 bytes
W/ResourceType( 511): CREATING STRING CACHE OF 108 bytes
I/Choreographer( 511): Skipped 59 frames! The application may be doing too much work on its main thread.
W/View ( 511): requestLayout() improperly called by android.widget.TextClock{41f27900 V.ED.... ......ID 134,0-300,122 #7f0a004e app:id/clock_view} during layout: running second layout pass
W/View ( 511): requestLayout() improperly called by android.widget.TextClock{41e0b080 V.ED.... ......ID 158,0-275,22 #7f0a0055 app:id/date_view} during layout: running second layout pass
D/PhoneStatusBar( 511): disable: < EXPAND* icons alerts TICKER* system_info back home RECENT* clock SEARCH* >
I/Choreographer( 511): Skipped 46 frames! The application may be doing too much work on its main thread.
W/InputMethodManagerService( 436): Got RemoteException sending setActive(false) notification to pid 1317 uid 10045
W/InputMethodWrapper( 601): Incoming session is null
I/DreamController( 436): Stopping dream: name=ComponentInfo{com.android.dreams.basic
[Desire Android Development] ze7zez:
Yes, I use a clean install.

Daydream-Colors is not significantly important element of the system. The Clock is working properly and is more practical.
[Desire Android Development] spezi77:
See above, I have edited my comment 'cause I have found the culprit. :D
[Desire Android Development] spezi77:
[MENTION=4810659]ze7zez[/MENTION]

And in the other case I couldn't find a problem that comes from the source code. It seems to be an out of memory related problem. I suggest that you could use zRAM or try a swap partition if you are working with bitmaps.

See error log:

V/XmpPresets( 1112): Write XMP meta to file failed:/storage/sdcard0/DCIM/Camera/IMG_20161205_195418.jpg
I/dalvikvm-heap( 1112): Forcing collection of SoftReferences for 19660816-byte allocation
W/ExifInterface( 588): Skip the tag entry since tag number is not defined: 2
E/dalvikvm-heap( 1112): Out of memory on a 19660816-byte allocation.
I/dalvikvm( 1112): "ProcessingTaskController" prio=5 tid=18 RUNNABLE
I/dalvikvm( 1112): | group="main" sCount=0 dsCount=0 obj=0x41df1be0 self=0x4d0fbab8
I/dalvikvm( 1112): | sysTid=1168 nice=-2 sched=0/0 cgrp=apps handle=1292004128
I/dalvikvm( 1112): | state=R schedstat=( 9615875221 4629760754 3872 ) utm=911 stm=50 core=0
I/dalvikvm( 1112): at android.graphics.BitmapFactory.nativeDecodeStream(Native Method)
I/dalvikvm( 1112): at android.graphics.BitmapFactory.decodeStreamInternal(BitmapFactory.java:620)
I/dalvikvm( 1112): at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:596)
I/dalvikvm( 1112): at com.android.gallery3d.filtershow.cache.ImageLoader.loadBitmap(ImageLoader.java:330)
[Desire Android Development] ze7zez:
This is possible only if the SD card has a write protection. Sometimes damaged partition table gives the symptoms.

Insert the memory card in the PC and fix errors.

---------- Post added at 21:24 ---------- Previous post was at 21:19 ----------

Well well!

Out of memory, and I even gapps not installed. Now let's see the same thing after installing gapps.

p.s.

Today, I'm exhausted, "thanks" :D

---- edit 1 ----

Ha!, ha!, ha!

After installation s2sd, disappeared issue of closing the gallery during editing. ;)

p.s.2

OKAY. I have to sleep. I get up at 5:00. Good night.
[Desire Android Development] spezi77:
Ha! Crazy! So in that case low memory didn't refer to RAM, but to NAND storage.

I'm also exhausted for today.. Thank you for that fruitful discussion which helped to make big steps forward in the further development..
[Desire Android Development] spezi77:
Hey folks,

watch out, spezi has gifts and treats for y'all!

Look into your shoes: Release 7 has arrived :p

Change log:

* Disable atlas service at start-up to save memory

* Align values under Display > DPI settings to be more regular: 140..260

* Fixed FC in Gallery2 app (while editing images) and merged many more stability improvements from CAF

* Fixed a crash in KeyguardWidgets (still had a reference to DashClock)

* Slim down the ROM size (e.g. LockClock 8.6MB -> 1.6MB)

Happy St Nicholas' Day!
[Desire Android Development] ze7zez:
Thanks, thanks, thanks Matthias!

"spezi77 Today, 02:23" <- Here is the true face of the Renaissance man.

He does not sleep and is still working on the great work.

Great work is to provide to us, users, joy of use SlimKat in our Bravo.

Thanks, thanks, thanks Matthias!
[Desire Android Development] Paisi:
Where to get hboot with more than 250mb on system?

Thank you very much for this development! I managed to get your SlimKat ROM to work on my HTC Desire with the stock (?) hboot 250/40/150. I am still getting memory warnings when i try to install big apps. So i wondered whether one of the other hboots you recommend might be of help. Where do i get a new hboot? The link you provide in your installation instructions has been removed?

1. Recommendations/Requirements:

- An hboot with at least 250mb on system. These include stock hboot or [MENTION=4577482]jmcclue[/MENTION]'s 250/5/182 hboot.
[Desire Android Development] fifo:
You can get hboots here: http://alpharev.nl/ . Just scroll down a bit for download links
[Desire Android Development] pieterbonte:
This is unbelievable!! :D

Great work! :)

very snapy

thank you!
[Desire Android Development] FaserF:
Merry X-Mas!

Thanks again for this rom, it is just working like a charm and makes this old device something great again.
[Desire Android Development] camuu:
Hey everyone,

Could somebody help me out with the partitions and Mount2SD?

I followed the 4EXT tutotial that is linked in this thread and picked a 1gb partition, but I am always SO confused by doing partitions. It's already confusing enough on Windows, but on Android phones it gets even worse with the internal/sdcard storage etc.

I installed this ROM last night and I really like it, but when I install Gapps on it it doesn't even fit. I run out of space and Google Services just keep crashing it's unusable.

Currently I have 150mb internal storage so the ROM + Gapps don't even fit, I'm not sure if that has anything to do with the way I've partitioned it or not.

Is there any way of increasing the internal storage? Has it got anything to do with the partitions or my hboot?

I've been messing around with Mount2SD but I'm not sure how to get Gapps onto the 1gb partition I have on my SD card, if that's even possible.

Thanks for any help.
[Desire Android Development] pieterbonte:
Hi,

Which recovery do you use?

I use 4ext and it's really easy using the tutorial on this page: http://xdaforums.com/showthread.php?t=2125513

The first time I partitioned it with my pc and minitool partition manager but my recovery didn't fully recognize the ext4 partition (I must have done something wrong).

But using the steps on the page above it's really easy and it works like a charme.

The steps from that page:

1. Boot in recovery. (Power + Volume Down, then select "recovery")

2. Select "Tools".

3. Select "partition sd-card"

4. Select "Remove all partitions and start from scratch" (Hope you backed up your sd-card, it removes everything on it)

5. Select your sd-ext partition size. Recommended : minimum 512mb.

6. Skip sd-ext 2 (If asked for it)

7. Skip swap. (If the rom you want to install requires swap, then select 128 mb)

8. Choose Ext4 as your partition type. (Ext4 is faster than Ext3)

(it automatically formats the resting space as fat32)

Voila, now you have an ext partition.

After you partitioned your sd, you have to put it in your computer to place the rom on it and follow the installation steps from the developer of this rom.

When the rom is settled for a few minutes, you normally have to install a2sd and answer y-n-n but you can save more space when you answer y-y-y (at the cost of a slightly slower device).

However, this works great for me (using a high speed sd card).

Good Luck!
[Desire Android Development] camuu:
Yo, thanks for the reply.

I think I've al ready done the partitioning correctly, I have the 4ext recovery and here is what it shows in MiniTool (it's only a 2gb SD card):

But my main problem is with only having 150mb of internal storage. Is that even normal? When I look up specifications of the HTC Desire the internal memory should be 512mb.

I'm installing the ROM again now and then I'll have a look at the "a2sd" you mentioned
[Desire Android Development] pieterbonte:
Yes, it's normal to have only 150mb available. The memory of the desire in total is 512mb, but it is partitioned.

250 mb for system, 150 mb for data and 40 mb for cache. The remaining is lost due to formatting.

When you assign a2sd as said, it moves all appdata to the ext4 partition, leaving the 150mb almost untouched (look at the picture, I actually have about 500mb of appdata).

However, you could also use another HBoot (next to de a2sd eventually) to reassign the partitons of the internal memory.

Take a look at alpharev's site for it.

But for this rom in particular, i would suggest to use stock HBoot.

I would also suggest to use a class10 or uhs1 sd card (i suppose yours isn't because it's one of 2gb).

It has much faster write and reading speeds, this increases the speed of your desire a lot (really) when using a2sd (or something similar)

Regards ;)
[Desire Android Development] camuu:
Alright thanks for the info.

I'm not sure what I'm doing in apps2sd, but I'll look for a tutorial. It looks to be working.

But my problem is when I flash the Gapps zip it doesn't fit on the 150mb and basically the disk is too full and everything just starts crashing, including mount2sd/a2sd when I try to open them, or even space management for an app in settings. This only happens after I flash Gapps which then takes up all the space.

Is there any way to install Gapps straight to the partition of the SD card?
[Desire Android Development] spezi77:
Just install the Gapps that the developer has linked in the OP, no other Gapps. They have been optimized for this ROM and will fit perfectly into the partition layout of the HTC bravo. But before flashing Gapps the a2sd installation is obligatory.

Every step has been thoroughly explained below the headline "installation instructions". Please read it carefully..

Best of luck.

P.s.: don't install mounts2sd or any other link2sf or apps2sd bullzhit via appstore.
[Desire Android Development] spezi77:
[MENTION=6465885]camuu[/MENTION]

Install A2SD

- run Terminal Emulator App

- type 'su' and press enter

- allow root access in the popup query

- type 'a2sd install' and press enter

- reply to questions in this order

--> y n n (dalvik to card - yes, data to card - no, reboot - no)

- reboot to recovery and install Gapps
[Desire Android Development] camuu:
Ah damn, I didn't know you were supposed to install it through terminal. My bad.

I am using the ROM + Gapps from this thread but I was installing them in the wrong order, so things got messed up.

So happy it's working now! I've spend so many hours trying to root this phone, lot's of driver issues etc but now it's finally working. Might look into getting a faster SD card but I'm happy for now. Thanks a lot for your help and sorry for missing a step from the instructions :P

Happy newyear!
[Desire Android Development] milogen:
the home and recent apps not working, wondering you guys experiencing the same issue as well ?
[Desire Android Development] pieterbonte:
Not at all actually, it works perfectly with my desire.

In settings there's a navigation section with the option

to change the key actions for hardware buttons,

but you can also add a navigation bar.

Perhaps flash again?
[Desire Android Development] GiorgosCh:
thank you!!
[Desire Android Development] 2be3_80:
Does someone experiencing random reboots with latest builds?

---------- Post added at 02:00 PM ---------- Previous post was at 01:30 PM ----------

I have system/data/cache partition in yaffs2 format, is it necessary to convert it to 4ext and how it can be done?
[Desire Android Development] pieterbonte:
Not all actually, been using it for about a month now and everything is still fine.

Try using the format option in 4ext recovery perhaps?

I'm not familiar with that format...
[Desire Android Development] spezi77:
Don't do that, unless you know what you are doing.

I simply recommend to you to do a clean installation. ;)
[Desire Android Development] 2be3_80:
I have already done clean install (wiped everything except fat32 sd card). Those random reboots happened also with another 4.4.4 rom. I don't know what could be the culprit. Maybe battery - I have purchased not original battery for bravo. Last reboot occued when battery was at about 34 %. Already wiped battery stats in recovery.
[Desire Android Development] spezi77:
Wiping battery stats after flashing is always recommended.

Did you also consider to give the battery a 100% charge, as mentioned here? There is a chance that this method may increase your battery life or even damage your battery. Please bear this in mind, you do this at your own risk.
[Desire Android Development] 2be3_80:
I did this calibration and will see
[Desire Android Development] ze7zez:
Only the original model ensures the best fit between charger, A8181 and the battery.

Find out more on pages Battery University.

The actual battery capacity can be measured by the internal resistance of a special measuring device. The old original battery can just show underestimated the capacity of the battery other than the original.
[Desire Android Development] Maysi2k:
the hboot downloadlink is down :(
[Desire Android Development] spezi77:
Try this..

https://xdaforums.com/showthread.php?t=2549776&page=3
[Desire Android Development] Maysi2k:
Thanks :)

The Slimcat is really smooth on this old brick... i like it! :)
[Desire Android Development] Sikor87:
I do not have space in the phone memory. EXT4 - 1GB. Applications are installed on the phone. I did everything as in the first post. I have thrown stock hboot. Any ideas anyone anything?
[Desire Android Development] spezi77:
Switch hboot to Alpha-jelly. Dont install bloatware, e.g. FB.
[Desire Android Development] Sikor87:
OK.

In point's:

Hboot

Wipe

Rom

Terminal (YNN)

Gapps

Have Fan :)

This way?
[Desire Android Development] spezi77:
Yes, the steps are mentioned in the right sequence. You can give it a shot. ;)
[Desire Android Development] galaxxian:
hi,

i am actually on build.9.0.unofficial-20160408-1820 and i will update on the latest build. my desire runs normaly, small issue, but not so heavy for me.

can i do a dirty flash or ist it recomanded to do a clean flash also if i want to update only?

hmm, i think about what i write down in my question. and i believe a clean flash is the way. because of the a2sd-function. and i want to update to the actually gapps offert in op. yes, clean flash.

isn't it?

thx for replay
[Desire Android Development] ze7zez:
Nobody knows what applications you have installed and how they will react to the upgrade.

So make a backup in 4EXT and then upgrade.

If you are unhappy, you will easily restore the ROM.
[Desire Android Development] galaxxian:
now i did it. fresh, clean install and all do. also what did not work properly before. thx for that rom.

only, but I knew yes, the space to install apps is despite a2sd function still scarce.. and so i say "y" at 2nd step of install a2sd and move data also on the sdcard. and now there is "unlimited" space available. i use a class 10 card and it works fine for me. a little bit lag after touch before the app/function runs, but usable. it is not my dailydriver so its ok.

thanks again for that usefull rom for our first-class-phone (in 2010...)
[Desire Android Development] galaxxian:
so, now i had a small problem, hope someone can help me.

the sound is extremely quiet. ringtones, notifications and music. volume is at maximum but it sounds like wispering. a connectet bt-musicbox sound really really loud.

anyone a idea?

thx
[Desire Android Development] ze7zez:
1. Clean the internal speaker grille and earphone hole.

2. Pure ROM installation

3. Replacing the speaker.
[Desire Android Development] galaxxian:
thx for your replay.

in the previous installation of this rom, an earlier version of which I come, there is the sound loud enough. so it seems not a hardwareproblem. and i do the clean install, read above.