yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Android Development] Gronkdalonka:
Wow, might be just my imagination but .14 seems to be pretty snappy ;)

Less ram consumption and pretty fluid
[G2 and Desire Z Android Development] tsubus:
I think limiting the background processes to 4 helps a lot. It's also possible we could go higher and still have good results. The default on android is 24, therefore I have also added options for 8 and 16 for people to test out. Feedback would be great ;)
[G2 and Desire Z Android Development] tsubus:
I have just removed 3.0.14 because of a FC when using SlimPie for the first time (which makes the phone unusable). I'll upload 3.0.15 soon, which will be the same thing, but no FC with SlimPie. Sorry about that.

[MENTION=320897]People[/MENTION] that have installed 3.0.14: do not enable SlimPie on this version, install 3.0.15 if you want to do that. If it was already enabled from previous versions, you don't have to worry about anything, it will work.

edit: upload finished
[G2 and Desire Z Android Development] bradley_e_smith:
Does that mean themes won't work? I happen to like the themes engine have downloaded an Android L version off the play store and like the look of it a lot.

-brad
[G2 and Desire Z Android Development] tsubus:
the theme will remain active if you have already applied it and don't wipe your phone. I will add the theme engine again in the next release, this release is a test to see if anything improves by not having it. If it does, I will make it optional upon installation, so that people that prefer a little more juice can remove it, and people who like themes can keep it.

If you want to apply new themes, I suggest you stay on .13 until the next release.
[G2 and Desire Z Android Development] bradley_e_smith:
Also on .13 under developer options I can't set the the stay awake if charge, it is grayed out.

-brad
[G2 and Desire Z Android Development] daivee:
OK so I am seeing and feeling a lot better response from this device running the latest .15 update (I left my theme Fi set because its my daily driver not planning on switching between themes ) I see apps open up faster and have noticed that the keyboard seems to pop up quicker. I set my background process to 8 to test things out. So far its been an improvement from the previous releases. Great job [MENTION=3252739]tsubus[/MENTION] I am truly amazed.
[G2 and Desire Z Android Development] bradley_e_smith:
.13 and speaker phone and mic

okay so on .13 if I put the speaker phone on (while in a call) and then take the speaker phone off, the mic is muted and I can't seem to get the mic unmuted. Also I don't believe the mute button works as well.

If someone could check their phone.

btw: it worked correctly on on previous versions of the ROM

-brad
[G2 and Desire Z Android Development] kamild_:
Installed .15 and guess what? It doesn't appear to be rooted for me :I

"There is no SU binary installed, and SuperSU cannot install it."

Any thoughts on that?
[G2 and Desire Z Android Development] Gronkdalonka:
Strange, no SU problems here.

Did you wipe before you installed .15 or did you do a dirty flash from a previous version ?

Also did you try to flash SuperSU manually ?
[G2 and Desire Z Android Development] kamild_:
Well, I sorted it out already. Seems like one of these flashable ROM boosters (either "Turbo Boost Mod" or "Project Mod Boost Nitro X.3 Edition") caused SuperSU to break. Reflashing SuperSU zip from Chainfire's website sorted it out and now everything works flawlessly.

Thanks for suggestion though and sorry for inconvenience. Also I used SuperWipeG2 to perform a clean installation.
[G2 and Desire Z Android Development] WizardStan:
Hi, great work! Everything on .15 seems to be working quite well, even better than Marco's AOSB. When I get a phone call the screen actually turns on and I can see who is calling! It's amazing!

My only concern is that settings keeps asking for super user. I've got logs of it asking for Superuser 10 times this morning between 5:38am and 6:20am. 5:38am is about the time when I started up navigation and 6:20 is shortly before I arrived at my destination,. It isn't just because of maps, I'm sure. I also have a few requests from yesterday, all of which were denied because I wasn't looking at the phone at the right time; I caught it a couple of times but I ignored it because I had no idea what it was doing. Should I be worried about this, or should I just set "settings" to auto-grant?
[G2 and Desire Z Android Development] tsubus:
You should not worry about requests from settings, it could be anything from the ads disabler (only once on each boot) to the performance settings, to ilwt customizer (when you apply settings). If you don't feel safe you can leave it disabled but you'll lose some functionality. I will upload a new version almost the same as .15 but with themes enabled tonight. Hopefully it behaves just as good as .15 so I can just leave them enabled permanently.
[G2 and Desire Z Android Development] tsubus:
3.0.16 is up :)

https://plus.google.com/106490939796690729213/posts/cAHVkjvYgWp
[G2 and Desire Z Android Development] bradley_e_smith:
trying .16

under developer options the stay awake while charging is greyed out. Any chance of getting that back?

thanks

-brad
[G2 and Desire Z Android Development] tsubus:
that's never been touched, has it ever worked?
[G2 and Desire Z Android Development] Gronkdalonka:
It's not greyed out for me (.16 atm) and i can confirm it is working (Screen will dimm but never completely go dark during charging)
[G2 and Desire Z Android Development] tsubus:
I will check my phone later tonight, but I will assume it's user error [MENTION=2096888]bradley_e_smith[/MENTION]. Have you made any modifications to the ROM? Have you full wiped and checked if it still doesn't work?
[G2 and Desire Z Android Development] bradley_e_smith:
Will wipe and reload, but for me it worked on .12 and earlier version and the only thing I have done is load a CM theme (just don't like the bland kitkat).

**update**: did a full wipe and the stay awake on charge works again. I do still have issues with the speaker phone/mic. When I turn on the speaker phone, the mic goes dead/mute and the only to get the mic working is to hang up. Also if I just mute the phone, the mic does not mute. So it is almost like the speaker phone button mutes the mic but no way to unmute. This issue for me started with .13 as well, and since I just wiped and reloaded fresh I am curious if others have this issue.

-brad
[G2 and Desire Z Android Development] DerNetzreporter:
This is the best kitkat Rom I used. So much options and with 150 apps still fast.

My only problem is the market won't let me install some apps, eg hangouts. It tells me it is not compatible with my device.
[G2 and Desire Z Android Development] tsubus:
That's most likely due to the modified dpi. I would need to either add a hacked play store apk or switch the default dpi back to 240. I'll think about the best option. I like the 200 dpi but it's a bit of a pain to add the hacked dpi play store.

Anyway, for now you can switch back to 240 dpi from the Display settings (reboot necessary)
[G2 and Desire Z Android Development] tsubus:
I can't help you on this issue because I don't have a SIM that fits the phone. Hopefully somebody else can give more feedback on the issue.
[G2 and Desire Z Android Development] kamild_:
Hey,

I'm experiencing some random reboots and I would like you to provide logs but whenever I enter "logcat" in Terminal Emulator, it says:

I have never used Logcat before. Also I'm using both "Turbo Boost Mod" and "Project Mod Boost Nitro X.3 Edition" to make the phone usable (I'm getting hangs/black-screens/reloads really often otherwise). Any tips?
[G2 and Desire Z Android Development] bradley_e_smith:
Thanks

Can anyone else check their phone mic (speaker and mute button) please?
[G2 and Desire Z Android Development] daivee:
Currently tied up with some work but will test asap.

Edit: I decided a break was required due to the following:

1. During an active phone call. When on call, pressing the speaker button puts the call on speaker but the mic seems to be muted. Once I pressed the speaker phone button my caller could not hear me. When trying to return back to headset mode, my caller could still not hear me. Ending the call was the only option that works.

2. During an active phone call. Pressing on the mute mic button, it seems as no action is taken. Leading me to believe mute button is broken.

Thanks [MENTION=2096888]bradley_e_smith[/MENTION] for bringing this up. I could only imagine myself in a scenario were my client would call me while I am on the road and hitting that speaker button with out knowing it was broken would really make me look bad. Hopefully we can see a fix for this. But until then I highly recommend everyone to not use this for now. Unless your feeling adventurous. [emoji41]
[G2 and Desire Z Android Development] bradley_e_smith:
Thanks!

tytytyty!
[G2 and Desire Z Android Development] feliciaIII:
Report...

Hello,

I did some testing and the mentioned settings definitely improved the overall speed and reaction times, unfortunately, the phone was still acting very clunky in some situations.

This result probably doesn't have to be taken serious, because the SD-Card could have been defective... just while trying to flash the newest build, it couldn't be read anymore, leaving me with an unusable phone. Also on several PCs, the card couldn't be read anymore... (seriously!). I will now test the newest build with a known-as-working card :D

greets,
[G2 and Desire Z Android Development] tsubus:
For the speaker phone/mic issue, it would be helpful if you could provide a logcat and a kmsg (along with the exact time when the issue occured). It's really hard for me to fix something that I can't test myself.

edit: it would also be helpful if this is an issue just on this ROM or all KitKat ROMs.
[G2 and Desire Z Android Development] lm089:
I installed this ROM yesterday, and I must say that until now this appears to be the fastest / snappiest KK ROM I've tested so far on my DesireZ. I'm truly amazed! And it's really nice-looking, too! Reminds me a bit of SlimBean (which I really liked testing last year but wasn't working at all due to too many freezes, FCs and lags).

Could turn out to be my daily driver, replacing alterNdromadus (CM 10.1).

But (you alreday have guessed there's a "but", haven't you?) one thing isn't working at all, and that is auto-rotation: display simply won't rotate, no matter what settings I made. Now I maybe could live with that, if it wasn't for an app I'm using every ow and then (a "Solitair" card game to be exact); this app is forcing the display into landscape upon start, but it's not forcing it back into portrait upon exit. And now guess what: after quitting said game the display remains in landscape, no matter what I do. After reboot I'm back in portrait again, but that's not really an option, I feel.

Questions: anyone else experiencing this (phone not reacting at all to auto-rotation)? Any idea how I could enable this?
[G2 and Desire Z Android Development] tsubus:
Is it enabled in Nova settings?
[G2 and Desire Z Android Development] bradley_e_smith:
I think it didn't happen in .13, I guess you would like a logcat of me making a call then placing the call on speaker phone after a certain amount of time and then taking the call off speaker phone?

**update: added 1 logcat and then decided to wipe the phone clean and load just the ROM and nothing else and get a logcat, which is try#2 file
[G2 and Desire Z Android Development] tsubus:
Yes, the logcat would only be useful in this case. I have not changed anything audio-related from .13, could you please check again with that release to make sure that it did work? if it did, then i can hopefully narrow it down and find the root cause.
[G2 and Desire Z Android Development] WizardStan:
I had no problems installing hangouts. Are there any other apps you're having trouble with? I can try and investigate for you.

I didn't try .13, and I haven't tested this on .15 yet, but on the other KitKat roms AOSB and PureKat putting a call on speaker phone did exactly this as well, muted the mic and couldn't unmute until the call was dropped. I just don't use speaker phone anymore.

I'll try to get some logcat output for you tonight.

I had this as well: anything that forced it to landscape wouldn't set it back. I could fix it by loading up anything else and then hitting home. My actual solution was to disable auto-rotation. Haven't had a problem since. Anything that needs landscape puts it to landscape and then switches back; opening the keyboard switches to landscape and closing it switches back; the only catch is that I can't just turn it sideways and have portrait mode, I need to open the keyboard, but on the plus side it never accidentally switches, which is something that used to happen often so I would have disabled the auto-rotation eventually anyway.
[G2 and Desire Z Android Development] lm089:
Wasn't aware of this in Nova settings... and, yes: in Nova it was set to "Auto rotate". But setting it to one of the other options doesn't really help. Currently it's like that:

- system settings: auto rotate = disabled

- nova settings: never mind, really (currently set to auto rotate)

Thus I always return from landscape to protrait; only way to force display into landscape mode is to pull the physical keyboard. This is mostly ok; only in those rather rare moments where I prefer the full on-screen keyboard (landscape version) over the physical one I'm out of luck. Let's see if I can get used to that.

---------- Post added at 04:26 PM ---------- Previous post was at 04:24 PM ----------

Had it disabled as well; thanks for the "keyboard" hint, hadn't really thought of that one ;)
[G2 and Desire Z Android Development] DerNetzreporter:
is it only me,

open the notification bar an clicking the time on the left doesnt open the clock for me.

Clicking the date opens the calendar, all other ROMs had this feature.

And is it good to use seeder, greenify or smart booster (xposed) with this rom or are this tweaks already integrated?

Updating Hangouts worked after changing dpi and deleting all playstore data. But I still cant install blablacar, kino.de and some other apps.

are this apps not compatible with 4.4.4 or do I have to change more settings to get them back?
[G2 and Desire Z Android Development] BIade:
Just load the apk via pc and then transfer to android :P
[G2 and Desire Z Android Development] DerNetzreporter:
That's not the solution I am searching ;)
[G2 and Desire Z Android Development] tsubus:
I have uploaded a test build, which contains 2 modifications:

1) Modded Play Store: should play nice with all dpi's. If not, try deleting app data and retry

2) Tried something to fix the issue with the mic, but I'm working blindly (no logs and I can't debug myself), therefore it's a shot in the dark. It might even break the mic completely, so if you install this build, please test it right away, don't wait until you have an important call just to realize that nothing works.

download: https://s.basketbuild.com/devs/tsubus/vision/full/test/

md5: 67928ac9c826095b7a82344e28c9923f
[G2 and Desire Z Android Development] lm089:
Since I started testing this ROM on Sunday I had about 5 complete freezes followed by auto reboots.

Before I go into detail it may be important to know that I went from nova launcher to SmartLauncher as I feel that nova has gotten to heavy over the years, SL is much lighter and snappier, and I like it anyway. And I also prefer single color background images over multi color ones, so I replaced ILWT's background image.

OK, here's what happens (when it does):

Every time it starts with the phone freezing completely; yesterday it happened during some file operations, this morning it was when I switched on GPS and started recording a bike ride using a Gps tracker. This situation takes a few minutes until the phone reboots itself (no interaction by myself).

The weird thing is that when the phone is back at the lock screen it has restored the original background canvas (ILWT's owl pic). And until I reload my own background image the phone's reaction to anything is v-e-r-y s-l-o-w. As soon as I restored the launcher settings everything appears to be back to normal.

Could it be that in those situation the ROM is explicitly looking for nova launcher and thus consumes a lot of cpu power?

Yet another thing happened twice so far: I started a tool that required SU access but wasn't registered in SuperSU yet. So SuperSU dialog pops up, I make my adjustments and that should be it. But in those two cases SuperSU (or whatever els) went into some kind of infinite loop by popping up a message approx. every 10 seconds that the specific app has now root access. Only way to stop that is to reboot the phone. Don't know if that has to do with SuperSU itself or something else.

I'd be happy to provide some logs if you tell me how to create one...
[G2 and Desire Z Android Development] tsubus:
Could you check if using nova also gives the same issues? It shouldn't be related but the thing about the background is weird and you never know.
[G2 and Desire Z Android Development] bradley_e_smith:
I see that, but it appears to be the sdcard (media_rw) process scanning my sdcard. What I did was to delete the /sdcard/Android/data directory and reboot.

Like you I use the SL launcher because it seems to be memory wise.

-brad

---------- Post added at 08:26 AM ---------- Previous post was at 08:25 AM ----------

Will give it a try for item #2. I don't have issues with item #1 b/c I like my dpi at 240 (old eyes and all).

-brad
[G2 and Desire Z Android Development] lm089:
The first couple of times this happened was when I still was on nova. Difference could be that I had installed Nova Prime (I tend to pay the few Euros for apps that I like, and I used to be a big fan of Nova before it became too heavy for my well-aged DZ). Actually I doubt that the Prime unlocker could be causing this, but as you said: you never know...

---------- Post added at 02:45 PM ---------- Previous post was at 02:38 PM ----------

One more thing I just found: I just manually edited the ILWT.txt file, set "bg_apps_limit" from 4 to 8 (thought that maybe 4 processes might be a bit too limited; and someone here in this thread had mentioned this value, so I gave it a try). Then rebooted the phone.

Now if I'm in system settings, then opening "Customize Installation" then try to scroll down past "Disable ads" >> settings kind of crashes with an error message (sttings closed or something like that) then re-opens itself at the main screen (but not inside "Customize Installation")

re-editing ILWT.txt and setting back that value to a smaller value like 4 or 6 appears to solve the problem (didn't try any other number)

Update:

OK I couldn't resist, tried 4, 6, 7, 8 and 9. Settings crashes only for bg_apps_limit=8, not for the other numbers; weird, but OK: so it'll be 9 processes then ;)

---------- Post added at 03:17 PM ---------- Previous post was at 02:45 PM ----------

Hmm - is this being rebuilt after reboot? I never dared to play around in there, really...
[G2 and Desire Z Android Development] bradley_e_smith:
another weridness with .16

twice now my phone was working just fine, and then I went to it and no response. So this time I plugged it into the computer (was close to work) and adb devices shows 'recovery'

dmesg shows the attachment.

C:\Users\brad>adb shell

~ # logcat

logcat

/sbin/sh: logcat: not found

~ #

df

Filesystem 1K-blocks Used Available Use% Mounted on

tmpfs 188396 32 188364 0% /dev

~ #

seems only to reboot at this point, and of course screen is blank
[G2 and Desire Z Android Development] bradley_e_smith:
Usually after a ROM load I think. I don't do it often, but when my phone is really slow after a reboot I look here (ie delete and then reboot again).
[G2 and Desire Z Android Development] hamxa266:
I'm not able to install ILWT ROM 3.0.16 (Kitkat) don't know why . It is saying E: footer is wrong . I'm using cwm recovery version 6.0.5.0 !
[G2 and Desire Z Android Development] bradley_e_smith:
Same mic issue - will try and get a logcat for you.
[G2 and Desire Z Android Development] hamxa266:
Opps sorry didn't see installation post !
[G2 and Desire Z Android Development] bradley_e_smith:
Text Messages taking longer to send

Also noticed (and reloaded .13 to check) that .16 takes many minutes (3-5) just to send a text message (not mms). .13 sends within the same minute.

Also plan on checking both .13 and .12 for the mic issue and will report back.

Also curious as to how many are actually using the ROM as a DD

**update**: Just check .12 and it also has the mic/speaker phone/mute issue (at least the backup of .12 I had). I can of course reload just the rom if needed. I really love the ROM, but have been caught twice putting the phone on speaker (forgetting about the bug) and then having the mic go mute.
[G2 and Desire Z Android Development] daivee:
I use this ROM as a daily driver. Ever since .11 , that's around the time my nexus 4 shattered.
[G2 and Desire Z Android Development] WizardStan:
I don't have any problems sending text messages, they're all sent and received within seconds.

First I heard about it was .15 last week. Previously I'd been using PureKat as an experimental ROM and then switching to AOSB when I needed something stable that wasn't going to make me wait 5 minutes for my phone to be responsive.

After switching to ILWT, the only time my phone is painfully unresponsive is when I've actually done something, usually opening the browser. I've been happily using it daily ever since and I intend to keep on doing so.

... And having said that, I tried to plug it into my desktop to load a shell and brag about uptime (because PureKat becomes unstable and needs a reboot every 2 days, and AOSB breaks the wifi periodically and needs a reboot to fix it, so 7 days is amazing) and it completely froze, screen came on and no response, adb shell tells me "error: device offline"... and it just self rebooted. Well then, that'll teach me to brag. It took less than a minute to reboot so I ain't really mad, so long as it doesn't do that while I'm in the middle of using it.
[G2 and Desire Z Android Development] Gronkdalonka:
Same here except i didn't need to destroy a nexus. Btw Text messages are sent instantly, no delay whatsoever
[G2 and Desire Z Android Development] daivee:
Trust me when I say that I did not want to destroy my nexus by choice. :(

As far as my messages go, I usually receive MMS and text with no real delay.

I have issues with my data connection every once in awhile, sometimes a reboot is the only fix.
[G2 and Desire Z Android Development] Gronkdalonka:
Did you try turning on and off airplane mode ? Also maybe wipe efs, couldn't hurt :confused:
[G2 and Desire Z Android Development] lm089:
Sending text messages is no issue for me, same speed as with any other ROM...

Currently I'm using this as a DD; I'll leave it ata that for at least one more week then will decide whether I should return to AlterNdromadus or just keep it.

Currently I'm seeing a much higher battery consumption compared to AlterNdromadus, but this may be due to the fact that currently I'm using the phone much more than usual just to test things out.

I hardly ever use the the mic functionality so that's no drama for me. Meanwhile I got used to the dysfunctional auto rotation, so no issue either. Only the odd spontaneous reboot (including the myterious "Return of the Owl") and maybe a higher battery consumption (if so) could make me abandon this ROM.
[G2 and Desire Z Android Development] daivee:
Yes, switching to airplane mode is the first thing I try, followed by turning my mobile data on/off. Both have no effect. I did just upgrade my radio to a newer version. I think this may have solved the problem because after flashing the new radio I was getting more consistent connection. Thanks :good: