yashsingh1/xdaforums huggingface dataset:
[HTC Incredible S] rqmok:
For Developer Options:

- Go to About Phone in Settings

- Keep tapping Build Number seven times and you will activate Developer Options in Settings.

For SMS "read"

- The "read" option does not mean that it will open the SMS so you can read it. The "read" option is pronounced "red" which means that you have read the SMS. So, selecting the "read" option will only mark the SMS as read (pronounced "red"). If you want to open the SMS you have to select the SMS text in the status bar.

Please ask about anything you didn't understand.
[HTC Incredible S] ntmm:
:good: Thank you.

Now the "read" thing makes sence =) "message has been read" :highfive:
[HTC Incredible S] szezso:
Vivokat is the only ROM where the media buttons aren't working? Did it work with CM10 for example? :)
[HTC Incredible S] kuroro:
Is that last thing remained unsolved ? [emoji12]
[HTC Incredible S] batculp:
No, even on CVX Reborn they didn't work with wired headset as I remember
[HTC Incredible S] funCrash93:
I can recall that in one of your ROMs [MENTION=4622338]szezso[/MENTION]...(one of Vivo*CM) , wired HeadPhones Media Buttons WORKED :P

(sadly I can not recall exactly in what ROM)
[HTC Incredible S] szezso:
Okay, even if I was able to update the KGSL and ION drivers, I still have to update the msm_fb drivers also, because without that, I'm getting camera corruption, and the Vido playback/recording makes the phone to do a hot reboot... I found something nice in the last One V kernel source (which is also MDDI), it uses newer msm_fb than the Vivo. Let's see!

Okay, this didn't help, I was wrong, the One V uses almost the same... But wait! I've found a device with 3.4 kernel + MDDI panel!
[HTC Incredible S] Eternalman:
What device buddy!?
[HTC Incredible S] szezso:
Huawei U8800. But sadly, it didn't help, so I'm trying somehow to get the camera working with old msm_fb.

Is there any need for AOSP Kitkat? :) So, I mean AOSP like on a Nexus. :) I compiled one to my Express, and I thought, may you would like to use it also.
[HTC Incredible S] RmatriX1218:
+1.

I believe performance over features and lean ROM will give better performance on our device.

xpossed is there for addon features.
[HTC Incredible S] kalyanroxx:
Is there any way to fix the screen glitches , it is so annoying :confused:
[HTC Incredible S] szezso:
Just read the commit! ;) https://github.com/szezso/android_device_htc_vivo/commit/df9c49c39b5deabbdc59390ba44ed291119847c7
[HTC Incredible S] kalyanroxx:
Sorry szezso I saw that and i don't know what to do, will that be fixed in next version or is there anything I should do? :confused: :D
[HTC Incredible S] funCrash93:
so there is an upcoming AOSP [MENTION=4622338]szezso[/MENTION] Signed.? ^_^

sounds interesting :D

guess it will be more stable (more of a DD than ever) than current CM-based.? :confused:
[HTC Incredible S] szezso:
It's not for AOSP at the moment, I'm trying to fix the camera and the glitches in CM11. :) I'll release that first.
[HTC Incredible S] funCrash93:
so, you wanna say that a 4.4.4 VivoKat "w/o" bugs is coming first.? :D

that's even better ^_^
[HTC Incredible S] szezso:
Exactly. :)
[HTC Incredible S] rqmok:
Oh that device! That was my previous device. The person who ported the 3.4 kernel to that device is [MENTION=4223446]Blefish[/MENTION], and I am really inspired by him. Unfortunately, that device uses NT35399 WVGA Panel.
[HTC Incredible S] szezso:
Yep, I saw. Sadly, Huawei/CAF framebuffer can't be compared to hTC fb, so, that wasn't a good base...
[HTC Incredible S] rqmok:
I know how to add the mddi drivers to 3.4 kernel, but I just can't get the kernel to boot, because HTC kernel is soooooooo different to the Huawei U8800.

By the way [MENTION=4622338]szezso[/MENTION], do you know what the ATAGS in the arch/arm/mach-msm/devices_htc.c are for? If they are for getting the kernel to boot then I need to add them to my kernel immediately.
[HTC Incredible S] szezso:
Yep, probably they're needed! :)

*sigh* It seems that I have to revert to older KGSL and ION drivers, because with these, I can't fix the camera. In logcat, it doesn't show any problems, so I'll try with older KGSL soon.
[HTC Incredible S] kalyanroxx:
Szezso , I have a request , some time when I call some one phone mic doesn't work, it is making me feel to revert back to ADHD but I'm loving vivokat , so is there any way to fix it ? Thank you..
[HTC Incredible S] szezso:
UPDATE!! :highfive:
​

ROM:

- Android 4.4.4_r1 (merged)

- CM sync

- Enabled SD eject option

- Some cleanup

- Increased boot speed

Kernel:

- Now compiled with AOSP 4.7 GCC, to fix graphical glitches
[HTC Incredible S] Eternalman:
Thanks Mate! So, has anyone tried it yet?
[HTC Incredible S] quentin2260:
Thanks for update !!

Time to Titanium Backup now.
[HTC Incredible S] Inferno7202:
Awesome! Another Update!! Haven't used long enough to give review but i've noticed "Interface" is gone from the settings and cannot activate Immersive mode, or expanded desktop

Edit:

Found the expanded desktop option under "Display"
[HTC Incredible S] ivanich:
Graphical glitches are still here, happens mostly with stock browser.

W/SurfaceFlinger( 1512): HWC_FRAMEBUFFER_TARGET found in hwc list (index=0)
W/SurfaceFlinger( 1512): HWC_FRAMEBUFFER_TARGET found in hwc list (index=1)
[HTC Incredible S] quentin2260:
Yes graphical glitches still here :(
[HTC Incredible S] darker01:
I third that too :)
[HTC Incredible S] quentin2260:
Graphics glitch appears with Chrome browser to. When keyboard is open its Just impossible to see something on screen, screen look likes mosaic of glitch.

Please szezso, can you solve this important bug
[HTC Incredible S] funCrash93:
can you people feel the difference between 4.4.3 and 4.4.4 ? :confused:

---------- Post added at 12:59 AM ---------- Previous post was at 12:58 AM ----------

BTW, can someone post the MD5 for S#10.?

Thank you.
[HTC Incredible S] 072665995:
4.4.4 only adds a bunch of security fixes. There isn't supposed to be anything much different.
[HTC Incredible S] funCrash93:
it's really AWESOME to see our Old hIncredibleS receiving 4.4.4 alongside with flagships :cool:

and kinda funny :D

Thanks [MENTION=4622338]szezso[/MENTION]

waiting for "L" :fingers-crossed:

what do you think [MENTION=4622338]szezso[/MENTION] :confused: is it even possible :rolleyes:
[HTC Incredible S] Inferno7202:
Anything's possible with Szezso here
[HTC Incredible S] funCrash93:
BTW : having minimal to NONE Graphical Glitches with Chrome BETA on S#9. Can someone check with S#10.?
[HTC Incredible S] 072665995:
The incS might not even have enough system space given ART is default now too. Also it probably wont be available for a little while anyways (:
[HTC Incredible S] AndyYan:
As is said in my signature, I had my Nexus 7 with Android L, and I can see that it takes a bit more RAM and (supposedly) much more graphics processing power for these fluid animations. Plus the default ART takes significantly more internal storage. I assume we need a repartition if we want to fit it in, not to mention slight to moderate lags everywhere (KitKat already lags a bit compared to all Jelly Bean builds).

Whatever, let's just keep calm until L's source code is released and CM starts doing its magic :)

Sent from Google Nexus 4 @ CM11
[HTC Incredible S] szezso:
Don't be scared. We have a lib partition also, what I don't use, yet. That means plus 152MB for use. :) I think, I'll have to make very light builds, but hopefully it'll fit on the NAND somehow. The problem is with the cache, it can be 300-400MB because of ART, and it'll use that much space from our data partition. So, we'll only have ~600-700MB to install apps. But, it'll work! :p

About the performance: Yes, it got worse with Kitkat, because it uses many-many transparent UI elements. Sadly, our GPU can't really handle these. :rolleyes:
[HTC Incredible S] Eternalman:
I had one small question. Can you make a new JB 4.3 ROM that can fit the best in our device? As you know, the battery issue and small minor bugs still happen in 4.3.:confused:
[HTC Incredible S] szezso:
May I will, but I'll soon get an HD2 too, so I'll have 3 devices to support, so I can't make you sure, but I'll try. :)
[HTC Incredible S] Eternalman:
Well, I'm not saying this only from my side. As you know, most us are having only one device as daily driver and we really need a ROM that works buglessly. ARHD was good but now, it has been more than 9 months that ARHD has been my daily driver. I'm tired of it. And almost all of the other ROMs except Sense ROMs have some issues. A 4.3.1 JLS36I Can be the best choice. It is light enough and updated enough for our device. But it all ends up with you. If you can free it from all the bugs, then we will probably don't even need a new ROM. :good:
[HTC Incredible S] kalyanroxx:
Hi im on st#9 My phone mic is broken when I call someone they can't hear me , plz can anybody help
[HTC Incredible S] nikant:
my thoughts exactly.. but it's up on the developer and his time to spare.. (and most of the crowd that just wants to have the latest of the latest even if it's not dd..:rolleyes:)
[HTC Incredible S] funCrash93:
isn't it possible to move some data to SD-Card (like HD2 with NativeSD or DataOnSD or smth like).?

maybe Cache2SD :D (with a Class 10 MicroSD guess that the speed wont be a problem). :confused:
[HTC Incredible S] yurisyi:
stable #9

it's a super bettry saver!!!

Using 25Hr , decrease 16% bettery ! (almost idle,alarm, no wifi,air mode)

(I buy a new mobile, so my IS is for alarming now)

How about stable #10?
[HTC Incredible S] Eternalman:
That's the same as my opinion. Though, szezso has to spend a lot of time trying to fix main bugs in KK while he can spend less time on fixing minor bugs. Just do the math. Less endeavour and amazing result is better than a lot of trying and just an acceptable result.
[HTC Incredible S] rqmok:
If you want, I can build and maintain a JellyBean ROM for you. But, I just need the source code for it.
[HTC Incredible S] szezso:
That would be really nice. :) I'll update the source for ION, and the kernel also....
[HTC Incredible S] otakux:
since the kernel display driver is updated. I will always see the display error on the web browser and camera. would you revert it to the previous version?
[HTC Incredible S] pallxy:
szezso，can you add the OTA
[HTC Incredible S] dinesh2707:
WOW! SZezso! You are amazingly fast! Thanks for an incredible update :D
[HTC Incredible S] AndyYan:
Too much request, not enough time to handle it all. The ROM isn't updated as often as official CM, and when it is, chances are the changes are big enough to demand a clean flash, so I don't see the importance of OTA.

P.S. Another Chinese dude here - welcome :)

Sent from Google Nexus 4 @ CM11
[HTC Incredible S] rqmok:
There is no need to do a clean flash at any point. But yes I would recommend [MENTION=4622338]szezso[/MENTION] to provide very small flashable zips that update the ROM, instead of uploading the entire ROM each time.
[HTC Incredible S] kuroro:
He has been keeping updated for peoples in MIUI forum what's happening here, for quite a long time~

"Ban yun da shen" !

:D
[HTC Incredible S] ruudjuh1986:
Great work, tried stable#10 runs very nice. But I prefere a sense ROM, saw that HTC has blinkfeed launcher in the app store but I am not able to install this...? What am I missing, thought that android 4.4.x was the only requirement (probably the display to low ppi). Would be great to see an option for blinkfeed launcher in this ROM, or maybe a new project? :fingers-crossed:
[HTC Incredible S] pallxy:
Glad to meet you :D

---------- Post added at 12:02 PM ---------- Previous post was at 11:54 AM ----------

Sorry， I misread the word...Someone in anzhi forum want szezso to add the OTG not OTA..:o

Gald to meet you:D
[HTC Incredible S] funCrash93:
[MENTION=4622338]szezso[/MENTION], an update :

[IMG="VivoKAT 4.4.4"]http://i.imgur.com/k6GIfgO.png[/IMG]

http://i.imgur.com/k6GIfgO.png
[HTC Incredible S] pallxy:
Thank you:victory:I'm glad you know me:laugh:
[HTC Incredible S] sneakerspark:
[MENTION=4622338]szezso[/MENTION] , [MENTION=4799442]Sachin Thomas[/MENTION] fixed graphics glitches in pico's weekly builds. maybe that'll be of some help :(
[HTC Incredible S] AndyYan:
In English: Isn't OTG a hardware-related feature? I assume it can be added but not that easy, and if it's achieved, it'll have to be externally powered. Nexus 4, being a "modern" flagship smartphone, has no OTG support originally, and despite having third-party OTG support, it still needs external power and an Y-cable to function.

中文：OTG不是和硬件相关吗？我觉得应该可以有，但不会那么简单，而且肯定是外部供电的。Nexus4算是台比较“现代”的旗舰机，但是原生不支持OTG，第三方支持也需要外部供电和Y型USB线。

还以为你是搬运过去做做修改就当成自己作品发布的，看了你的原帖才发现是纯搬运+附加包的形式，赞一个 :good:

Others, please ignore the Chinese above. Will move to PM if necessary.

---------- Post added at 10:34 PM ---------- Previous post was at 10:23 PM ----------

We have a ported version of BlinkFeed available here: http://xdaforums.com/nexus-4/themes-apps/port-blinkfeed-launcher-v11-dpi-fixed-t2705092 , but I tested and can confirm that it force closes on IncS, possibly because of low DPI (APK doesn't contain enough HDPI resources). Feel sorry about that.
[HTC Incredible S] kalyanroxx:
Sorry for bugging you again and again, but my mic is broken sometimes people on other side couldn't hear me.., plz try to help, I'm using st#9.1

Thank you. :o
[HTC Incredible S] szezso:
Logcat? :o :o
[HTC Incredible S] :
take a look at them may be it can help u in 3.4.y porting

https://github.com/Blefish/kernel_qcom_msm7x30

and sony xperia 2011 uses mddi screens if i remember correctly

https://github.com/LegacyXperia/android_kernel_semc_msm7x30/
[HTC Incredible S] rqmok:
The first link that you have posted is the 3.4 kernel I am trying to port on the kk_2.7-stable branch.

For me, th problem is not the MDDI Panel Drivers, but th problem for me is that the is not booting at all. I am not sure what the requirements for the bootloader is in order to get the kernel booting, which is why I am stuck in the first place.

By the way, our phone uses MDDI Client drivers. They are pretty old as well.
[HTC Incredible S] otakux:
I compile your newest kernel source, it stock on the GPU clock.

If I reset the OC, it seems to stock on the medisserver.
[HTC Incredible S] szezso:
STABLE #11 is coming soon! :)

Teaser:

- KK-2.7 KGSL drivers

- KK-2.7 ION drivers

- No graphical glitches

- :)
[HTC Incredible S] ivanich:
Just want to ask, which framework_base and framework_av repos you are using?
[HTC Incredible S] szezso:
Stock ones, I've patched them manually. :)
[HTC Incredible S] interaser:
this one should go well with stable 11 :)

https://play.google.com/store/apps/details?id=uk.co.shenye.android.inputmethod.latin

thank you szezso
[HTC Incredible S] babicz99:
[MENTION=4145169]interaser[/MENTION]

+1
[HTC Incredible S] szezso:
I tried to build with the DHD's display source, huge fail. :D I have to make a clean build with my sources, but please be patient, because I have to reinstall my Linux, it's getting very slow now...
[HTC Incredible S] dejemi:
I can't download Stable#10, my Chrome browser detect as malicious.
[HTC Incredible S] poondog:
Chrome is good at seeing roms as malicious

Try another browser
[HTC Incredible S] funCrash93:
dunno, my Chrome is ok. (well, almost ok :D )

it depends on many other things (like from where are you downloading, and where are you downloading from (like what country), what policies are ....etc, and even the internet provider seems to count, as I tried at work and at home and the Surfing on net seems different).

p.s. not saying that another browser won't work, it may work ;)

just saying that not always the browser decides :D
[HTC Incredible S] dejemi:
Stable #6 & Stable #8 downloaded via Chrome. No problem.
[HTC Incredible S] AndyYan:
Hmm, I received my Incredible S rooted and recovery'd, so I don't know the exact steps, but it should start with S-OFF your device, installing a custom HBOOT (Revolutionary or BlackRose are available in this section), then installing a recovery (4EXT and TWRP are available), and finally booting into recovery to install a custom ROM. Appropriate tutorials should be relatively easy to find.

Sent from Google Nexus 4 @ CM11
[HTC Incredible S] davidchuyaya:
try this thread that I used

it was my first try at rooting, at it worked pretty well

{[GUIDE]} HTC Incredible S Unlock Bootloader, flash recovery, Root, S-OFF

blackrose is optional

I didn't install it and nothing ever went wrong
[HTC Incredible S] Inferno7202:
Has anyone added music to their sd card lately?? I'm on stable 10 and it doesn't seem to see the recent songs I put on. The app Itag sees all the songs in my sd card but it doesn't appear in the music player. All of the rescan sd card app crashes when ran. So idkk..
[HTC Incredible S] S4crifice:
Issues?

Hi,

I'm using this ROM for 2 weeks and I found out:

- smooth and stable BUT:

- sometimes digitizer does not react, I must pull out the battery and restart ..

- sometimes the buttons does not work, same solution,

- screen goes crazy sometimes, it's like a disco :)

- the system creates many duplicate folders in my Gmail

What gets me crazy the most is the digitizer ...

Is it just me or you have the same problems as I do?
[HTC Incredible S] Mrbababo:
Seems like it is ok for me. for the first 3 points.

as for the screen going crazy usually it's specific apps causing the problem. can try solving it by going dev mode and tick disable HW overlays. works for some apps however do note every restart of phone resets these settings.

For the Gmail issue cant confirm as i gave up, not enough space to even update the apps i use more frequently so i uninstalled it
[HTC Incredible S] S4crifice:
Well, I'll try the HW overlays, but any idea why digitizer gets stucked? I simply can't do anything that release the battery ... :/ That sucks, people ..
[HTC Incredible S] DeBored:
I use S#10 from release date, an no problems with gmail, no problems with digitizer, abaut music i don'n know, i listen radio (software: Spirit) Screeen psihology is normal, and its not crazy :laugh:

Maybe try clean reinstall, in some times solve many problems with custom configs. Or after clean install try some day use your phone without restored apps from backup.
[HTC Incredible S] rqmok:
I think you might have to replace your digitizer.
[HTC Incredible S] S4crifice:
Yes, I do, I have a cracked screen .. but it never happened during using the phone, it stucks while the phone is not used .. so it seems like SW issue, but I'll replace it and we'll see
[HTC Incredible S] S4crifice:
And another issue - phone restarts after almost every phone call .... I did full and clean install before 2 days ..
[HTC Incredible S] rqmok:
If it is possible, could you provide logcat?
[HTC Incredible S] S4crifice:
Sure, how do I do that? :)
[HTC Incredible S] rqmok:
By the way, which JellyBean ROM should I build? I was thinking 4.3, but it is up to you guys. So please let me know so I can start downloading the source code, because it takes me a whole day to download the android source code.

---------- Post added at 01:28 PM ---------- Previous post was at 01:23 PM ----------

You should have an app called Terminal. Open that app and type:

adb logcat -v long > /storage/sdcard0/logcat.txt

and press Enter.

Now, you should have a file on the root of your sdcard called "logcat.txt". Upload that file here.
[HTC Incredible S] S4crifice:
I'll do the log.

About the question - honestly, I don't care if it is 4.4.3 or 4.4.4 - but hey, KitKat runs pretty smooth so .. just make it as stable as possible :)
[HTC Incredible S] szezso:
I'll be back in development on Monday. I'll be able to build a ROM hopefully. :)
[HTC Incredible S] S4crifice:
It still typs me -waiting for device- ... And it also created an empty logcat in SD card .. What am I doing wrong?

Is there any method how to get the text to terminal without manual input? I tried to copy it, send through chrome to phone but I still can't use insert in terminal ..
[HTC Incredible S] paulwollf:
Type the command without 'adb'
[HTC Incredible S] S4crifice:
There you go if you can find it something I'll be really glad...
[HTC Incredible S] Eternalman:
Build the 4.3.1 please.
[HTC Incredible S] S4crifice:
Why Android 4.3 when there is 4.4 with minor changes? More smooth, less RAM usage ect.. ?
[HTC Incredible S] Eternalman:
KitKat has transparent graphics and our GPU cannot handle it well enough. When you run a useful but heavy app with the 4.4.x ROM, it won't function well. Even the official 4.0.4 has better performance on some parts about apps. You can try ARHD and see the difference. No offense to Szezso, he has done a great job on KitKat, but most of us like a 100% working device with an acceptable android version. 4.3.1 is same as 4.2 and 4.1 in user interface so it is smooth enough with our device's specs.:good:
[HTC Incredible S] S4crifice:
Well, I'm not developer so I can't know :) I used before Incredible S Huawei G300 and even Wi-Fi tethering was not working, it was the smoothest system made for this model made by Dazzozo ... He made before also high quality system running 4.1 - 4.3 but 4.4 was the fastest .. So that(s my experience with 4.4 but if you tell me 4.3 goes much better, I'll try ;)
[HTC Incredible S] Eternalman:
It is only my own experience. You can try the 4.3.1 ROM for smoothness test but not as a daily driver. There is a small issue with the battery(Kernel related I think)
[HTC Incredible S] funCrash93:
[MENTION=4985761]Eternalman[/MENTION], you can try and enable smth like "Low RAM devices" (can not recall exactly), it disables some graphical features like transparent bar, and etc.

so I guess it will run even smoother...(maybe even better than 4.3 :) )

---------- Post added at 09:46 PM ---------- Previous post was at 09:45 PM ----------

like in KitKat for ZTE Blade 3 (check it out, can not recall exactly what you should enable in build.prop (I guess) :D )
[HTC Incredible S] Eternalman:
I know what you say. You are talking about that option in performance section. I've tried it but let's be honest. KitKat is like OS 8.1. It is smoother because it is more lagless compared to 4.3 or 4.2. but it actually uses more resources to function properly.:good:
[HTC Incredible S] funCrash93:
this is it.

what't the point in "compacting" resource usage when you have resources (I mean newer devices).

it's the point in progress, of course you optimize, but why restrict when there are resources :) ( :( sadly not on our phone, but running KitKat on a little bit higher ended phone is more than I pleasure (someone to correct me if I'm wrong ;) ))
[HTC Incredible S] dyrgutt:
Hmm, there seems to be a 'little' disparity when it comes to peoples experiences with 4.4 -- i've got to say, with my own device, it is 'BEAUTIFUL'! I've been using it as my daily since release, and the only infrequent/occasional mishap is the screen garble, which I've learned to live with [I find having the home-screen displayed before going into standby, works a treat; it's not foolproof, but I can't remember the last time I got it and I use it 24/7 ;) Anyhow, cracking job [MENTION=4622338]szezso[/MENTION] - can't wait for #11 :fingers-crossed:; it should be brilliant! Cheers Dyr :good:
[HTC Incredible S] rqmok:
Edit: don't worry about it.
[HTC Incredible S] sneakerspark:
[MENTION=4825202]rqmok[/MENTION] 4.3.1 please
[HTC Incredible S] anonymousthing:
I'm getting an issue with this ROM that I have no idea how to fix; I flash it, click reboot now, and everything is fine. I set up my phone, blah blah. Then I reboot, and it gets stuck at the white HTC screen forever (tried letting it go overnight even). Clearing cache/dalvik does not fix it. I've tried redownloading the ROM and reflashing it, same issue: works first boot, but gets stuck at white HTC screen when I reboot.

This doesn't seem to happen to me for other ROMs, and I tried this when it was at update #9 and it was fine. Any ideas?