yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] archcantor:
I looked into the Viper mod. It's nice but.....

Tim's Kat App built upon Supercurio's Voodoo Sound App. The idea here was that the TF101 had a super audio subsystem in hardware using the Wolfson Microelectronics WM8994 chip. The app was designed to maximize the use of the built in hardware, preferring the audio take digital paths whenever possible. Voodoo required a modified kernel or getting the paid app. Tim customized all this to work well with the TF101 with the Kat App.

Viper appears to be DSP on steroids. It looks amazing. However, I personally feel when the Kat App optimized the TF101 audio system the sound quality is really fine. I don't see the need to add DSP to the mix. The Kat app boosts the audio and the Wolfson chip does the rest of the job in hardware.

I did install the Viper mod on my Samsung Tab 2 and it works nicely. The audio on the Samsung is really fine without Viper. I found on the Tab 2 that turning on more than one feature of Viper was overkill. Even good DSPs are not perfect and add artifacts (aliases) to the autio. Viper sounds the best I have heard but it's too much for my tastes. I have to admit it is very nice and well-done. I compare this to having a 4 cylinder engine in your car. No matter how many controls from a jet airliner they put on your dashboard, you will always have a 4 cylinder engine. However, some of those new controls can be exhilarating even if you never break the sound barrier.

I would imagine if I had a cheap pair of earbuds I may feel differently. Viper could help with this kind of thing. I used to have a Nook Color tablet which had a horrible audio system. Viper would have been a blessing for that one.

Everyone will have their own tastes and preferences. I think the benchmark of good audio on the TF101 is with the Kat App. I recommend starting from there and then see if you need more.

The Viper mod requires extracting one or more apk files from the distribution zip files. You have to use something like Root explorer to copy them into /system/app and set permissions. Then you run it from the app drawer and set some config options. When you change the Viper settings they take effect immediately and you can hear it change while listening.

As always, you may feel differently. Have fun and enjoy the option to choose.
[Eee Pad Transformer Android Development] old.splatterhand:
I thank you for your in detail answer. But i'm over that point, i have Kat app installed since months and (i'm sorry Tim) it doesn't satisfy me in case of sound and loudness.

Maybe i'm using it wrong, but the problem is, meanwhile my girlfriend is using the TF most and she always complain about the sound/loudness.

Now, if there is an alternative, i wanna try, but maybe i recognise, that Kat is doing the job much better.

I will see.
[Eee Pad Transformer Android Development] reablom:
I guess RaymanFX likes starting things more than finishing them...

He also did it with his "own" TF101 ROM.

All this being voluntary work he's free to do so of course, but switching before the other ROM is stable doesn't seemwise.

In Dutch we have a saying for this: don't throw away your old shoes before you've got new ones.

Good to hear you're still trying to further improve the EOS4 rom.

I'm pretty satisfied. The only issues I have are low volume (even with KAT) and occasionally the tablet freezes and reboots (mostly during surfing)

Maybe coming updates wil fix the latter, I've given up on the first.
[Eee Pad Transformer Android Development] e154037:
He can throw his own shoes away, but do not throw somebody else's shoes.
[Eee Pad Transformer Android Development] philseven:
I am sure you are entitled to your opinion and I hope you are not offended just wished you had used this forum to post your comments and respect the thread. http://xdaforums.com/showthread.php?t=2355490

:good:
[Eee Pad Transformer Android Development] renmo:
everybody is entitled to his own opinion and hope your not offended but i think its great he put his opinion here in this thread because some people gave there opinion about vipermod here and some off use would like to know the difference between that and kat wihout having to read through other people's opinions in another thread .

i for 1 still love eos4 with kat :good:
[Eee Pad Transformer Android Development] philseven:
The the thread is for eos4 I see only two other opinions about sound mod and one was my opinion and I was wrong. Someone asked if there was another sound app other than kat app I provided link and I stated my opinion of the app which I was wrong should have just provided link. For that reason I feel responsible for the discussion of the other sound app.I just wanted to make sure things stayed on topic considering I was the one who provided the link to the other sound app. And gave my opinion which I was wrong. This is eos4 thread. And I thank old.splatterhand for doing something that I should have done by opening a thread specifically for that discussion and if one person does something wrong doesn't mean everyone should follow. Know if you want to continue discussing this it is up to you I have said my peace and apologized for my wrong doing I am done.

Originally Posted by old.splatterhand

I'm interested in this too, maybe you can share what files you installed and what settings you use to make it louder.

As i don't want to spam Team Eos thread i opened here a thread about it.

Would be nice if you could help.

As the reason for this post and thread being made.
[Eee Pad Transformer Android Development] old.splatterhand:
The point of the other thread is, information its easier to find!

Of course we can also talk here, if we talk about "Making Team Eos Rom louder" as long as it depends on the this rom.

But this will go under in hundreds of posts between and after. And for some people hard to find.

Thats why i did the discussion thread, an easy point to find all necessary.

And i don't want a poll or whats better than something else discussion here (cause this is really off topic here).

All respect to devs work!

But i tried now both and if somebody wants to know, what i think, read my opinion in the viper thread of me.
[Eee Pad Transformer Android Development] doppelhelix:
Since the clock can be moved to the center of the statusbar I feel the unresistible urge to tapp the clock. I really want to open the calendar/clock this way. Is this somehow possible?
[Eee Pad Transformer Android Development] ¿GotJazz?:
My Transformer still bogs down after a few hours of use, and I need to use the "Kill All Running Apps" feature to free up RAM and breathe life back into the tablet. I used a stock TF101 Transformer this weekend, and it was surprisingly fast (much faster than I remember :)), and it never bogged down.

Is there a fix for this somewhere? Maybe a different kernel, or custom kernel settings?

Thanks!
[Eee Pad Transformer Android Development] doppelhelix:
You could try nightly 117 or 118. Somewhere around this nightlys the slowdown-over-time started.
[Eee Pad Transformer Android Development] ¿GotJazz?:
I saw this sluggishness problem with 117, and was hoping it would be resolved with 120.

I just checked my tablet, and saw 121 is out now. Any improvement?
[Eee Pad Transformer Android Development] d3l1:
I have zero issues with nightly 120, maybe it's a faulty app.

Gesendet von meinem Transformer TF101 mit Tapatalk 2
[Eee Pad Transformer Android Development] belrik:
Build 121 fails to mount MicroSD

Build 121 failed to mount my microsd, tried manual mount but no joy. The instant I rolled back to 120 the card was mounted first time.
[Eee Pad Transformer Android Development] jopereira:
Same here. Meanwhile I installed KK103, KatApp and use Dolphin to browse (not chrome).

Came from super stable and fast ARHD 3.5.1, so just slightly impressed (at least I have Jelly Bean) :)
[Eee Pad Transformer Android Development] PRBajista:
Here we go again....smh
[Eee Pad Transformer Android Development] bsoplinger:
I'll add that 120 runs better than 117 for me also. But I'll also suggest the Greenify app, thread here at XDA. It hibernates apps you choose keeping them from wasting CPU cycles and memory but unlike the built-in disable function they are ready to go when you want them.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[Eee Pad Transformer Android Development] belrik:
Sorry, do you mean that this is a known issue? I hadn't seen this before and whilst I haven't read every post I hadn't seen this occur before.
[Eee Pad Transformer Android Development] PRBajista:
Yes. It was discussed a few pages back. Unfortunately if you just hit update on the app and don't read this massive thread as I do (which is understandable given how big it is) you could easily miss the multiple complaints about the same issue you are having. No worries. I due suggest they at least put a note in the OP to minimize the thread clutter. I'm waiting for that bug to get squashed in the 122 update which I hope is in the works. In the mean time just sit on 120 until something new is released. :o)
[Eee Pad Transformer Android Development] netvpn7:
TF101 stuck on boot???

installed on TF101 and stuck on the ASUS logo not going any further, waiting alot..???

any idea what to do ?

Thanks
[Eee Pad Transformer Android Development] jazzruby:
Restore NANDroid | Flash/Install 120

Wait for... 122 | Next nightly

-JR-
[Eee Pad Transformer Android Development] just lou:
It's very disappointing that despite all the problems 121 has, it remains on the server for people to download, and there hasn't been a single post from anyone on the EOS Team.
[Eee Pad Transformer Android Development] JimTDI:
well said!
[Eee Pad Transformer Android Development] timduru:
Just to make things clear, there's nothing of voodoo used in the Kat App.

The basic digital/analog principles to maximize audio quality and power have just been applied in the Kat app to get the most out of the WM chip. :)

I still have to add more registers controls later on, there are a bunch.

Kat controls the hardware and allows you to go as high volume as the hardware can.

If your input media and app is of good quality you don't need more than that to get the best audio output volume and quality wise.

Heck with a good set of headphones I don't really go over analog level 30, it's already very loud to me ;)

And doing it like the Kat app (full digital signal without boosting anything , with direct chip analog level control) is what will give you the best quality.

There are however situations when it might not be enough, for example when you have a low level input media, bad quality media that needs band corrections or an app like youtube /flash that outputs at lower volume.

In that case you can resort to a DSP /app like Viper which as far as I understand preprocesses the audio before sending it to the android audio pipe, that will then go to the hardware.

It's perfectly fine to use both.

Just keep in mind that for the best quality, you should not boost things too much with a DSP, before sending to the hardware or it'll saturate.

So it's 2 very different things basically, and both have their uses depending on what you are doing or want to achieve,

and what type of material you use too I guess :)

And you can use both the same time too.

---------- Post added at 01:06 AM ---------- Previous post was at 01:01 AM ----------

Well the latest info I had was that there was no team anymore. ;)

So I'm as surprised as you are to see that there are still new versions coming out.

No idea what's going on myself.

I think my best option at this point is still to just go the way I announced before and make a fork based on the latest preview version.

That will be the most efficient way to work and eat the last few tf101 bugs. :)
[Eee Pad Transformer Android Development] zachf714:
Woooha no more team eos just Timduru
[Eee Pad Transformer Android Development] just lou:
If it helps, the only issue I had with preview 202 was the camera was unstable.It and/or the gallery kept crashing.
[Eee Pad Transformer Android Development] archcantor:
Sorry Tim. Poor choice of words on my part. I should have said Kat App was built on a similar philosophy as Voodoo: Use the great build-in hardware audio system to its best potential. You made my point better than I did in that too much DSP boost can saturate the hardware.
[Eee Pad Transformer Android Development] didier74:
[MENTION=3951330]timduru[/MENTION],

I take this opportunity to thank you very much for all the work you've done, and, if I understood well, you're gonna do in the near future.

I have one small question please, since I bought TF01, voice speaking in swipe ( I am talking about the function that allows you to talk, and the keyboard is writing what you're saying), has never been working correctly, whereas it is working perfectly on my phone for example. Since I installed eOS4 and Kat kernel and Kat app, there has been some improvement, but it is far from having the same efficiency as on a phone.

Do you think it could be possible to improve the product of the some which may be related to the microphone , or maybe not I don't know ?

What is strange is that sometimes it is working really well, and a second after , it will not recognize what your saying. Once again this up is working very well on a phone.

Thank you very much for your answer if you have time to .

Envoyé depuis mon GT-N7000 avec Tapatalk
[Eee Pad Transformer Android Development] timduru:
No probs :)

I think you actually explained it very well that it was 2 different things and so on :)

I'm not sure,

what do you call swipe, is it the android default voice recognition feature like when you click the mic icon in google search ?

I don't use it much but it seems to work ok for me when I did.

I'm not native english speaker so I can't really test very well in english though ;)

But yeah overall I don't think the microphone is as good on the TF101 than it is on my phone either.

Could be because of that.

Since your issue seems random, unless I can reproduce it it would be very difficult to track.

Maybe try to find an exact pattern that you or I can reproduce easily.

Things that might help maybe: Did you try changing the input levels in the Kat app ?

Could it be also that the performances of recognition changes based on the noise that is in your surrounding environment or something ?

The FM34 DSP might also be misbehaving sometime depending on the timing of the recording / playback by the app you're using.
[Eee Pad Transformer Android Development] droyd4life:
Am I the only one experiencing super lag? The launcher runs at like 6 FPS with like 2 apps on it...
[Eee Pad Transformer Android Development] whitekidney:
HW acceleration is not yet properly implemented.
[Eee Pad Transformer Android Development] i9apps:
Hide the navbar
[Eee Pad Transformer Android Development] clouse2013:
Are you using the build listed here or the B96 test build? I think the unofficial one has a bunch if fixes in it. Runs fine and south for me
[Eee Pad Transformer Android Development] DevourDarkness:
But i like having autocorrect...
[Eee Pad Transformer Android Development] st0nedpenguin:
Then wait until it's fixed. :p
[Eee Pad Transformer Android Development] sidneyk:
Try Hacker's Keyboard in Playstore.
[Eee Pad Transformer Android Development] chazzdjr:
85 just popped up on goo.im. Should we move to that from the preview?
[Eee Pad Transformer Android Development] timduru:
Mixed bag of stuff.

A bunch of stuff from CM10 has been merged into EO4 without much testing, not sure why there was a hurry to merge that right during Christmas but well.

- It seems that the CM10 stuff includes the hardware acceleration fix that I had pushed more than 2 weeks ago and was waiting to be merged.

So the good news is that that Hardware acceleration should be mostly back in the official nightly.

One step closer to a useable nightly :)

- Another attempt at fixing the Soft keys custom color crazy cpu loop has been merged too it seems,

it fixes the crazy loop as long as you don't set a custom color.

the bad news is that if you set a custom color you still will get ~15% cpu eaten up by systemui + surface flinger + irq interrupt generated by all the redraw.

- Autorotation seems to be eating a bit more than 2.5% instead of 3-4% cpu,

the bad news is that turning autorotation off is now eating 3-4% cpu, so we don't have a way to prevent it from eating cpu now *joy*

So for the moment it seems we might be better

to turn autorotation back on

to "only get" about 2.5% cpu eaten and some lag.

There might be other things fixed or broken, I'm just coming back from holidays so it'd need a bit more time to check stuff....

But I'd say that you can mostly use the official nightly now:

- if you don't care about custom softkey colors (make sure you clear all custom colors if you have set them previously too and you're not doing a factory reset)

- and you don't mind the few % of cpu eaten by autorotate

It'll still post a new preview in a few hours with the usual launcher & other optimisations, & to address the softkey cpu eating too.

From there it seems I'll have to work on fixing the new stuff that was broken in addition to all the other stuff left to fix.

I think I'll work in priority onto the cpu eaten by autorotation, or at least find a way to bring it back to 0% when it's deactivated.

Because it's not only a cpu eating issue, it's also saturating the message loop with crazy notifications, making it slightly laggy.
[Eee Pad Transformer Android Development] chazzdjr:
I'll wait for your preview. It's taken great care of me so far. I hope you had a great holiday!

Sent from my Mmuzzified Verizon Galaxy Nexus on Tapatalk 2
[Eee Pad Transformer Android Development] zephiK:
thanks for staying active in the TF101 community :)
[Eee Pad Transformer Android Development] timduru:
New 4.2.1 preview version B98

Here's a new B98 preview version. :)

Preview version main Info & Download links

How to install

Main changes for the preview

Changes on teameos gerrit

4.2.1 Preview known issues & Workarounds

How to report an issue

What to include in the report

It contains the latest EOS4 merged stuff as of yesterday

Other changes includes:

- The few previous launcher & misc optimizations

- The usual soft key custom color cpu eating fix.

- Increased the touch sensitivity a bit

(I don't have an issue myself but all fingers might not be equal, so report if it feels better that way for those who felt that it was less sensitive, or if it brings back the "touch being detected as a pinch" issue)

Also as a bunch of other stuff has been merged, we might as well go through the list of known issues again.

See if it fixes some stuff or not.

So those who had some of these issues if you could retest and report to say if it's still there or if it's fixed. :)

Auto-rotation / system cpu usage

As mentioned in the previous message we also now have an additional few % of cpu being eaten even when turning autorotation off,

the cpu is actually now being eaten less with autorotation back on.

I'll have a look at what is causing the extra cpu usage even with autorotation off.

We really need to get a way to bring back system cpu usage to something close to 0% when idling or at least like it was before with autorotation off.

For the moment even if autorotation on seems to bring down the cpu usage to about 2.5% instead of 4% when it's off,

it's not sure what will feel better between the 2.

As with autorotation on, there's the additional message queue being saturated and so it might actually generate a slight higher lag even if it's eating less cpu ;)

Can't verify exactly what is going on currently as I forgot my TF101 cable, so that'll have to wait a bit ;)

So until it's fixed, I'd suggest to just test both autorotation on and off and pick up the one that feels the best for you in the meantime :)
[Eee Pad Transformer Android Development] cimbike:
So would you think B96 eats less battery then?

Thx so much.
[Eee Pad Transformer Android Development] DevourDarkness:
Have the launcher optimisations fixed the lag? And did you fix the keyboard autocorrect issue yet? I've haven't updated in a while.
[Eee Pad Transformer Android Development] timduru:
Yep, if battery is an important criteria for you, #85 and B98 will eat more battery than B96 for the moment.

Because of the added 2-4% cpu being eaten.

Performance wise with autorotation off it feels ok to me so far I don't really feel a difference,

so I'd say on the performance aspect B98 is good to use.

But if battery is your priority, staying on B96 until the system cpu usage is fixed might be better in that case.

I preferred to push B98 for the moment, because with the bunch of other stuff that got merged it might actually help a few other issues.
[Eee Pad Transformer Android Development] asdfzz:
Thanks Tim downloading B98

Btw no way to fix screen flickering?
[Eee Pad Transformer Android Development] atomic339:
Can someone describe problems with dock keyboard?
[Eee Pad Transformer Android Development] timduru:
I don't really see screen flickering anymore since the HW acceleration is back, so I'm not sure.

But maybe it happens only with a certain combination of things, try to give more information in regards to what/when you notice the flickering.

Also, which launcher do you use, and does it happens more, less, or the same for you compared to when there was no HW acceleration in the early versions if you tested these ?

Or do you notice the flickering happening only if you use a particular app or when you do something in particular ?

There has been quite a few things changed in the merged stuff in B98 on the hardware and compositing, so that might also help that.

See if it changes on that aspect once you're on B98.
[Eee Pad Transformer Android Development] wassim79:
Thanks for the great great great work, i was using the 4.1.2 of EOS and now i upgrade to this nice ROM, i only had 1 hour to test it, today evening i will kill it :D:D:D ...

I have only one thing to tell, my docking keyboard can't switch the language by using Ctrl + Shift as earlier ? is this problem still there or any solution had been found?

:good::good::good::good:
[Eee Pad Transformer Android Development] asdfzz:
I will see if B98 change it..

Im using stock launcher

Btw yes i tested old preview and yes without HW acc ive see it more...

I got that problem sometimes (not always) when loading pop up comes up on third apps like tapatalk,or on chrome when it load page.

EDIT: I had one now when typing (near keyboard)
[Eee Pad Transformer Android Development] aspros21:
I run it. It shows 2 temp files I ve created for test. The message about mounting is the point. Right?

u0_a37@android:/ # /data/data/org.meerkats.kat/utils/busybox mount /dev/block/sda1 /Removable/sda1 ; ls -l /Removable/sda1
mount: mounting /dev/block/sda1 on /Removable/sda1 failed: Device or resource busy
-rwxrwxrwx root root 0 2013-01-09 16:37 New Text Document.txt
-rwxrwxrwx root root 0 2013-01-05 19:59 ZDSgfsdf

Before run it, I had mount ntfs read/write my disk from your app. If I run it without mount it from your app it says that it can't find such file.
[Eee Pad Transformer Android Development] darkvoid_66:
I have a bug from time to time. Auto rotate stops working I have to go to rotation set it to "manual" them auto again and it works...

I have already re-flash ROM #89 + Kat kernel 4.2 70b and problem still remains...
[Eee Pad Transformer Android Development] zombiej79:
How should I format a SD card for this rom? Just got a new SD card thanks
[Eee Pad Transformer Android Development] xuser:
I remember the "hide status bar" option set only on power menu back in the Revolver ROM days. If I recall correctly the Dev of that ROM was not able to set it as a "on boot" option, though many did request it. The only option now is to modify the build prop, but doing so then removes the apps settings menu options.
[Eee Pad Transformer Android Development] edd080:
For now the best way is to leave it as FAT32, if the card is large in capacity (over 4gb) you can use a free program which you can google (fat32 format) and format the card as a whole fat32 microsd card, the rom should recognise the card without any problems.