yashsingh1/xdaforums huggingface dataset:
[HTC Incredible S] TheQwertiest:
That's nice to hear, but, in the meantime, here is the new buglist =)

Beta #1 bugz:

[New in the ROM] Browser render engine(?) bug: Some apps have dreadful problems with performance. Examples: stock browser, feedly.

[New in the ROM] Native screenshot bug: Native screenshot is not working.

[New in the ROM] Video playback bug: Video playback is broken.

[New in the ROM] SMS pop-up window bug: SMS pop-up window is not sized correctly for our screen.

[New in the ROM] BT sound volume slider bug: When changing BT volume through volume buttons, volume window appears. And if you try to change it via slider on this window (no matter in which direction), the BT volume goes at max value, disregarding the slider position.

[New in the ROM] Recent apps windows bug: Bring recent apps window (i.e. long press home button). All the preview windows are blank. Here is the logcat with the error:

11-19 10:56:41.155 W/Adreno200-GSL(1492): <gsl_ldd_control:225>: ioctl code 0xc01c0915 (IOCTL_KGSL_MAP_USER_MEM) failed: errno 22 Invalid argument
11-19 10:56:41.155 W/Adreno200-EGLSUB(1492): <CreateImage:1232>: fail gsl_memory_map.
11-19 10:56:41.155 W/Adreno200-EGL(1492): <qeglDrvAPI_eglCreateImageKHR:4505>: EGL_BAD_PARAMETER

[EDIT] Wired headset bug: Wired headset buttons and mic are not working at all.

BT headset buttons bug: Fast-forward\fast-backward are not working. Other buttons work just fine.

Capacitive buttons brightness bug: Button's brightness is no longer changed when changing screen brightness - it always stays at max. Perhaps it's a side-effect of CM introducing new feature - controlling time-out of button's light

Flashlight bug: Turns off, when screen is turned off.

Root access bug: Stock Root is not working. Need to install SuperSu zip manually. Still, it's not always possible to get Root access, even if all proper steps were taken. Workaround: untick "Sync with CM settings" in SuperSu settings.

[Still there] CRT-Off animation bug: Screen turns off BEFORE playing CRT animation, while it should happen at the same time. Results in max brightness and blank CRT-off animation.

[Need confirmation] Wi-fi on screen-off bug: when screen is turned off, wi-fi activity halts. I.e. if you download something through wi-fi and turn off display, then download will stop as well (it seems that wi-fi still works, but dl\ul speed drops drastically). Bug does appear with "wi-fi always on" setting. 3g continues to work with screen off without any issues. This bug was present in 10.1 as well and, perhaps, in 10.0 too.

[Need confirmation] Failure to wake up from deep sleep bug: not really traceable. Happens randomly. Phone fails to wake up from deep sleep sometimes. It may happen when it's charging or just when it's idling on the desk, still, the bug appears regularly every few weeks. Might be caused by some voltage tweaks in kernel.

[Not fixable] ART support bug: If you change from dalvik to ART and reboot, the device goes in bootloop. ART will not be supported by this ROM. Reason: >>Link<<
[HTC Incredible S] funCrash93:
[MENTION=4451231]TheQwertiest[/MENTION] I

can confirm

that buttons are not working on wired headphones, and even more : mic is not working either....

(may be just me)

Flashlight bug

can be fixed

by replacing the Torch App from CV10.1 (4.2.2 version)

no problem

with CRT Animation :P
[HTC Incredible S] AndyYan:
Maybe you don't know what the issue exactly is... This also exists on CV10.2.

Expected behaviour: the CRT animation goes, encasing the current screen content in it.

Current behaviour: the screen first clears its contents (i.e. go completely black, but the backlight is still on), then goes the CRT animation, resulting in bad-looking animation.
[HTC Incredible S] juso:
Sorry, might have not been clear, settings->about phone->baseband version. Mine is 20.76.30.0835U_3831.19.00.19_M and I'm not sure if this works well with KK ROM. Also, somehow feel that battery lives a bit less than with JB, but can't say for sure yet.
[HTC Incredible S] TheQwertiest:
Thx for the report. Updated the post.

And as [MENTION=4467696]AndyYan[/MENTION] said, current CRT animation behavior is not the one that was intended originally.
[HTC Incredible S] funCrash93:
[MENTION=351587]juso[/MENTION], mine was _19M, not changed to _11M, will see how it behaves...(no problems so far).

[MENTION=4451231]TheQwertiest[/MENTION] I guess, but the way it is now doen't bother me at all.:silly:

[MENTION=4467696]AndyYan[/MENTION], may be.:cyclops:

but imho it's not a problem.:D
[HTC Incredible S] TheQwertiest:
Not saying that it is critical, but this is still a bug =)
[HTC Incredible S] funCrash93:
isn't there a way to fully disable CRT Ani.?)
[HTC Incredible S] TheQwertiest:
Not in this ROM (yet), no. And it still would be a bug :D
[HTC Incredible S] AndyYan:
I think yes, but involves editing framework-res.apk.

EDIT: I've made a flashable zip for disabling CRT animation - once you flash THIS ZIP, when you lock the screen, the screen content will fade out instead of showing the wrong CRT animation. Tested and verified on my own device.

BE ADVISED that this is version specific - only works for VivoKat 11.18 version.

@szezso: if you recognize CRT animation as a bug, please consider putting this flashable zip in OP. I will update the zip regularly as you update your ROM version.

Sent from Samsung Captivate Glide @ CM10.2
[HTC Incredible S] szezso:
I know already, what makes the Browser and the UI laggy, and some other screen-related issues. :) Fix ASAP.

Sent from my hTC Incredible S S710e with VivoKat 4.4
[HTC Incredible S] 072665995:
You're animation mod is beautiful. Works like a charm. No more buggy CRT animation (you could barely see it anyways :laugh: )

Highly recommend this :D
[HTC Incredible S] achilles08:
I have flashed the Fix...fade out screen works but it is showing "Safe mode" at bottom left corner. do you know why???

Edit: Reboot did the trick...wonder why it went in safemode??
[HTC Incredible S] Sandeep_Jagtap:
May be you accidentally held volume down button till device boot..
[HTC Incredible S] achilles08:
Nope, i did not...
[HTC Incredible S] funCrash93:
what is that Safe Mode exactly?

I mean what's the difference?

something similar what Windows does?

p.s. sorry 4 a little offtop.))
[HTC Incredible S] odinko:
yes :) yes ... sometimes it can help to remove some 'stupid' software,

or disable wrong advanced settings

http://pocketnow.com/2012/07/11/android-safe-mode-gives-you-power-over-misbehaving-apps
[HTC Incredible S] funCrash93:
Thank You [MENTION=312053]odinko[/MENTION].
[HTC Incredible S] AhmadKushairi:
So is it stable now? I really want to flash it!
[HTC Incredible S] Iqbal Ansari:
Yes pretty much stable but no ringtone or notification.
[HTC Incredible S] szezso:
OMG! Sad thing is going on here. :eek:
[HTC Incredible S] Factasy:
What is happening szezso
[HTC Incredible S] funCrash93:
wait....WHAT.!? :eek:

dude....Do Not Scare Us Like That.!!! :rolleyes:
[HTC Incredible S] szezso:
Okay, what's happening? As I discovered, we need the new Adreno drivers to fix the graphical glitches. But, the new drivers are only supporting ION. And ION means, you know. :(
[HTC Incredible S] funCrash93:
dammit...:/

so you can not port it like other 3.4k drivers you've done.?

or w/o ION can not be done.?(

ok, but beside the fact that it glitches what other then visual it means.? (in terms of performance.? it's just visual, no.?):
[HTC Incredible S] szezso:
No, these aren't kernel drivers. These are libs in the ROM. At the moment, you have two possibilities:

1, No graphical glitches, no Camera

2, Graphical glitches, Camera

Somehow I need to port back that v4l2 driver, or I have to get the 3.4 kernel working, but I hope, here will be other solutions. :) If not, then I'll have some sleepless nights! :highfive:

And these aren't effect the Performance too much, but it makes the Recent apps menu blank, and the Browser and other apps unusable.
[HTC Incredible S] uprockin:
I am a java developer, but... I wish there would something that I can do...
[HTC Incredible S] szezso:
I'm still trying, I updated the kgsl, gpu drivers from CAF jb_mr1, may this will make it. :) https://github.com/szezso/T.E.S.C.O-kernel_vivo/commit/620e5ceb16df0c30181bb65afd0fffe204c85094 Building now...
[HTC Incredible S] funCrash93:
of course Camera.:D

I guess Recent Apps not much as a bug in comparison to Camera. but Browser->Other (laggy) apps...is a bit annoying...:/

we all believe in your superpowers [MENTION=4622338]szezso[/MENTION].

hope to be somehow useful, and I guess everybody thinks so here.;)
[HTC Incredible S] james1196:
Sorry for asking. However, what do these graphical issued include? If they are minor, shouldn't the camera come first?
[HTC Incredible S] szezso:
They aren't really minor. If you've tried the ROM already, you should know that the Browser and other apps, which affected by the new Chromium WebView which was introduced in 4.4 are very laggy. All of the apps, which use Chromium, has this lag bug, which can be fixed by the new GPU drivers + ION kernel...

I think, the 3.4 is too much for me, I'll try to get the camera working with 3.0 somehow...
[HTC Incredible S] aerosmith:
Ok, after reading further about these drivers I understand the issue. I think you can ignore my message below.

Sorry for my ignorance but Qualcomm is providing the libs since ICS. Are we already using those? If not can't we use those? They have released the Adreno 2xx drivers for ICS and JB. I have worked on another ROM that uses Adreno 200 and I have used the ones for JB which worked fine. By the way the same drivers should work for Adreno 205 which our phone uses. There are like 4-5 libraries we need to replace. The details of my work can be found in https://github.com/thepasto/android_vendor_acer_salsa_proprietary .
[HTC Incredible S] szezso:
We're already using the 4.1 Adreno libs, which ones are supporting PMEM too. The problem is that to fix the glitches, we have to use the 4.2.2 libs, and with this version, the PMEM got completely deleted from Android source (that's why we have to use legacy sources), so we need an ION kernel...
[HTC Incredible S] Solmath:
I'm not using the camera anyway and I guess I'm not the only one. So for me the ringtone bug is of a higher priority than a working camera right now.

Would it maybe be possible to release the final build in two different versions, one with and one without camera. As I'm not an android developer I have no idea how much extra work that would be.

And one last thing: Thank you so much [MENTION=1132633]szeszo[/MENTION], I love your ROMs.
[HTC Incredible S] funCrash93:
and if there is someone that uses both as well? what then?

of course Ringtone Bug is a priority just because it's a phone.... but for someone camera isn't less than important as well.
[HTC Incredible S] Inferi0r:
Did the devs for the other older HTC legacy devices have a solution for our kinds of problems? Official code or unofficial private code.

I am not a dev at all, but I cant barely imagine that all our problems are total device specific. But probably that is how it works.....
[HTC Incredible S] poondog:
Its either use a hacked up pmem kernel

Or hack in ion into a kernel, whether it be from porting a newer kernel or porting it into an older one
[HTC Incredible S] @di:
Mark, What ever you just wrote it feels like !@#$%^&*()!@#$%^^&**)_..... all bouncer...:silly:

I so wanted/tempted to try this ROM.... Damn,... my old incredible S is taken by my Boss and that bugger has given my phone to his wife.....

I am wondering how to ask for it and get it back? He said he want only for 4 days and its been more than 2 months now...... :rolleyes:
[HTC Incredible S] achilles08:
ask his wife directly :p
[HTC Incredible S] poondog:
Lets say the ION memory allocator (which is what it is) is a new engine for a car.

To get an ION supported kernel (a car with a new engine) you can do a few things:

.buy a new car (new phone with ION in it)

.mod the existing car to work with the new engine

.mod a new car to look and work like the old one, but have the new engine still

To get the new engine into the old car (port ION into the old kernel 3.0.y) we have to change parts, cut things and mould it around the new engine. Eventually, with enough metal hacking it will fit (build) but you may try to start it (boot it) and it will not boot. You'd then have to troubleshoot all the wires and everything to get it booting and functional

Alternatuvely, by porting a newer kernel to our older devices would be like modding a new car to work and look like the old one. It needs to work with our old hardware so old and new code must be used. Because there are no HTC 7x30 (our processor) devices with official JB or 3.4.y kernel, it needs to be ported from CAF (which is like a universal base which HTC started on) or from a similar device.

tl;dr its impossible and only a god can do it
[HTC Incredible S] @di:
Thanks Professor Mark. Really helpful and knowledge to understand.

Now where is my boss ..... let me get my phone back!!!!!
[HTC Incredible S] TheQwertiest:
One can still hope though =)
[HTC Incredible S] poondog:
lol cheers

Keep in mind that we have a really old processor lol from 2009 or something

Is it strange for bosses to take phones off their employees? Not a very good boss lol

You need to pray. To szezso
[HTC Incredible S] odinko:
warp's kernel src

maybe stupid question, but can't we take whole warp's kernel 3.4 ?

http://support.zte.com.cn/SUPPORT/news/NewsDetail.aspx?newsId=1004042

not just parts ...

http://pdadb.net/index.php?m=cpu&id=a8255&c=qualcomm_snapdragon_s2_msm8255

http://pdadb.net/index.php?m=cpu&id=a8655&c=qualcomm_snapdragon_s2_msm8655
[HTC Incredible S] szezso:
May, but really may, I have an idea, how to fix the slowness bug, without using the new libs... But even if it works, we need a proper ION kernel, cause the Vivo can't be supported in the future without that.
[HTC Incredible S] aerosmith:
any thoughts about integrating freedreno libraries instead? I know this would be a long task....
[HTC Incredible S] Solmath:
I think you got me wrong here. As I understood Szezso there's only a tiny little chance that we can have both a working camera and a ROM without glitches. Nevertheless he is currently spending a lot of time and energy to get the camera working without the glitches.

So maybe (just maybe) some other bugs (e.g. the ringtone bug) should be fixed first, as they are maybe easier to fix. In that case the people who do not need the camera (like me) would have a fully working ROM, they could be happy with. After that Szeszo could put even more effort in getting the camera to work.

Please don't take this as criticism, it is just a suggestion. I really appreciate Szezso's work, and I'm glad someone ist still developing those fantastic ROMs for our "ancient" device.
[HTC Incredible S] Hawkysoft:
Dude its bloody awesome that you still walk for the incs i might grab the phone soon out of the dustbox to upgrade it ;)

@ the poster above.

As a programmer the most important thing to fix is the hardest things. Which mostly are the reason why the small things excist.
[HTC Incredible S] RmatriX1218:
Every damn things on this planet has fix life. They have to pass one day and our IncS also would have died natural death.

Thanks to [MENTION=4622338]szezso[/MENTION], our IncS is still alive and still having serious fun and development.:good:

I am not a developer and doesn't understand integrity of kernel development.:crying:

As far as we are living in [MENTION=4622338]szezso[/MENTION] era, I'll have hope and belief that more and more impossible things are going to be reality...:fingers-crossed:

I have no plan to put my IncS aside till [MENTION=4622338]szezso[/MENTION] puts his weapon down and says good bye to IncS..:rolleyes:
[HTC Incredible S] Osamabinatiq:
Tell your boss that the phone you were using had a fault you have given it for repair it may take a few days when can I have my phone back.
[HTC Incredible S] szezso:
I've just finished with a build, I hope, it'll fix some bugs... :fingers-crossed:
[HTC Incredible S] batculp:
hungry for results
[HTC Incredible S] juso:
Hey SZEZSO, great effort and good news, awaiting to flash it afresh. What will be fixed in there?
[HTC Incredible S] szezso:
I hoped, that I fixed the ringtone and video playback bug, and it should be fixed, but it doesn't boot, because of my fault... :rolleyes:

Rebuilding. :)
[HTC Incredible S] Iqbal Ansari:
Rebuilding will take too much time!!! Lets hope that ringtone is fixed!
[HTC Incredible S] szezso:
Thanks to Inferi0r, I got an SSD! :) HUGE THANKS MATE!!! [MENTION=1800422]Inferi0r[/MENTION] :) I'm having problems with installing Linux, so it'll take a while, till I get the build enviroment working. :eek:
[HTC Incredible S] Inferi0r:
No thanks mate, you really deserve a SSD, is it recognized by your computer?
[HTC Incredible S] szezso:
Yep! :) It seems that it's working, but I'm having problems with this Linux installation... :mad:
[HTC Incredible S] szezso:
YEAH! Finally. :p It seems much faster, than it was! Thanks mate! :)
[HTC Incredible S] Inferi0r:
Great:D

Now we're all interested of this makes a difference for the building process....
[HTC Incredible S] Iqbal Ansari:
Thanks a lot inferior! Your name should be superior.....

People like you have helped the devs to continue the developement..
[HTC Incredible S] stryker09:
Not that it seems faster.... it IS faster :good:
[HTC Incredible S] szezso:
Okay, I have made a VERY slim GApps, because the one, what we're using has many unneeded apps. I'm still downloading the source, but I think, I'll only be able to compile tomorrow.

Anyway, my idea is if the SSD speeds up the building process much more, then I'll provide ION and PMEM builds too, till a better workaround comes for the glitches. :)
[HTC Incredible S] szezso:
LOL ;)

Anyway, this new source is a bit harder to build. It takes 3,5-4 hours on my PC, while the 10.2 finished in 3 hours. My old HDD isn't very capable to do thing like this. :D
[HTC Incredible S] Sithhy™:
szezso! I will get my HTC Incredible S on 15th of December and I want see that ROM fully working :D But as always - great work :cyclops:
[HTC Incredible S] szezso:
I'm sure, every bug will be pointed out till that date. ;)

Guys! If someone could make a sigpic, I would really appraciate it! :)
[HTC Incredible S] 072665995:
Camera's kinda broken on the ROM at the moment. I wouldn't stop development on 4.3 just yet ;)

Nevertheless, this is still amazing. We started with Froyo and now we have KitKat too. Amazing work as always Szeszo. You keep this device alive and i hope you continue your work on the Incredible S :)
[HTC Incredible S] james1196:
VivoKat <3 I Like It! Thanks for keeping it up bud, I know you have another phone now. Saved me buying something I would regret, so cheers.
[HTC Incredible S] szezso:
WiFi works!

WiFi and rotating buttons got fixed. Good night! :)

A sigpic added to the first post, thanks to Gizmo648! :)
[HTC Incredible S] funCrash93:
hei, Magician what do you think, can KitKat became the perfect fastest system for our beloved Vivo?

we all know what a WONDERFUL, FAST and SMOOTH ROM CV10.2 (4.3) is. So do you think that KK could be even better???
[HTC Incredible S] TheQwertiest:
Now only SD card left, so that the testing may finally begin =)
[HTC Incredible S] AndyYan:
VivoKat: A nice surprise when I woke up :eek:

Anyway, my PC is properly set up for building CM10.2 (and has done some successful builds so far), so if I have your source, device tree, etc. and know how to implement them, maybe I can bring up occasional, faster builds (my PC build CM10.2 in 1 hour). Just tell me how :)

Sent from Google Nexus 4 @ Android 4.4 KRT16M
[HTC Incredible S] Inferno7202:
Does this rom have Kit kat icons too? Cause i don't see them on the op.
[HTC Incredible S] szezso:
SD got fixed too! :) This was also good for other stuffs, cause Apollo doesn't make FC anymore, I can choose different wallpaper, and the Browser works now!. :) SDcard PC mount doesn't work, yet.

Now you can see the nice lockscreen music controls and the transparent status bar too! :p
[HTC Incredible S] szezso:
In fact, I'm a bit disappointed because of the KitKat. I thought it'll be as fast as hell, but it doesn't even reach the CM10.2's level. Or, I wasn't exact. Some animations are very, very fast, but for example the status bar is a bit laggy.. So, it's a bit bipolar, but It'll get better, I'm sure. And I have many, many free RAM! :)

[MENTION]AndyYan[/MENTION]: It'll take more than a while, cause you'll get continuous phone process crash, if you build a CM10.2 nowadays. I think, I know how to fix it, if you need help, PM me! ;)
[HTC Incredible S] Iqbal Ansari:
Thanx a lot szezso!!! :D

When are you going to release new build cause I really wanna try it. But in first build wifi i broken and I really need wifi.
[HTC Incredible S] AndyYan:
Thanks for the heads-up! The next school week is beginning and I'll try building next weekend (I suppose things would be somewhat ironed out by then, right?) If I need build-specific assistance I'll definitely PM ya.

Sent from Google Nexus 4 @ Android 4.4 KRT16M
[HTC Incredible S] szezso:
It's compiling now. :) I think, I'll be able to share it today afternoon.
[HTC Incredible S] funCrash93:
can't wait to get my hands on this WONDER..!!!! :D

as I can understand correctly, [MENTION=4622338]szezso[/MENTION], if you could get our phone a 3.4kernel, further versions of Android 4.4+ (5+, ...) will not be a pain in the a**, not a problem in making Custom ROMs.?)

p.s. with [MENTION=4622338]szezso[/MENTION], no need to upgrade to a newer phone.:D
[HTC Incredible S] szezso:
I found out, why is it so slow sometimes. There are some genlock errors in the logcat, so, I need to port back the genlock driver from the ZTE Warp's 3.4 kernel. That'll fix the slowness. :)
[HTC Incredible S] funCrash93:
yup, just like I said...no need in upgrading..xD

Thank you man.!!!!
[HTC Incredible S] Iqbal Ansari:
You are so genius. Did you invent android OS?
[HTC Incredible S] james1196:
Your sentence structure makes my brain bleed. No idea why, takes me a while to comprehend what you are saying :P No offense of course.
[HTC Incredible S] szezso:
ART Fixed! ;) This is F*CKIN FAST! :p
[HTC Incredible S] TheQwertiest:
Wonderful news! =) How did you manage to get the required space for the ART? Was it the slim version of GApps that made it possible?

PS: What do you mean by ION\PMEM build? Build with camera and glitches and build w\o camera and glitches?
[HTC Incredible S] szezso:
I had to delete some apps. It also boots up if you leave all of the apps in, but then you'll get some FCs. But after deleting the huge LatinIME, it works! :)

As you said. You can decide, which is more important for you. Camera, or no glitches. But in fact, I've found a possible fix, I'll try to build tomorrow. :)
[HTC Incredible S] szezso:
- Added some optimizations, also now compiled with Linaro GCC 4.8.2. I think, it worth a TESCO 3.1.2 version. :)
[HTC Incredible S] funCrash93:
[MENTION=4622338]szezso[/MENTION], any news on Ringtone Bug?)

or any other that was a Bug.))
[HTC Incredible S] szezso:
I don't know anything about that, cause the download has just finished. I'll only build tomorrow, cause I need to go now. :) But it should be fixed :rolleyes:
[HTC Incredible S] funCrash93:
Thank you :)

we all know you can fix everything :D
[HTC Incredible S] !crazy:
Are you using Art or Dalvik? I'm not even sure Art had anything to do with animations.

---------- Post added at 02:04 PM ---------- Previous post was at 02:00 PM ----------
[HTC Incredible S] AndyYan:
Dalvik, of course. /system space isn't enough for ART as of yet (@szezso said it might be fixed in the next version). Plus I'm not willing to tackle potential stability problems...

Sent from Google Nexus 4 @ CM11
[HTC Incredible S] TheQwertiest:
Hmm... So, in Desire HD section they managed to make ION compatible kernel. Is it possible to use their findings for our device?
[HTC Incredible S] LamboBull:
[MENTION=4468696]funCrash93[/MENTION]

Dont get too dependant.. We still have hardware limitations

Press "thanks" if I helped you out!