NexusHD2 Android Forum

I'm using the previous version of this ROM. I didn't read all the latest posts. I would like to know if the black box issue in Google Now fixed? Or otherwise if it is not fixed, can it be fixed according to what you guys know about these black box issues?

Hi all,

Tytung, thanks for your awesome work! With kitkat my HD2 got a revival!

My feedback for the LowSoundFixer problem:

1) Using 771 rights for /data/dalvik-cache, the LowSoundFixer stops working, and in the log cat we can see:
01-26 19:54:01.704 I/dalvikvm( 2918): Unable to open or create cache for /system/vendor/app/LowSoundFixer.apk
(/data/dalvik-cache/system@vendor@app@LowSoundFixer.apk@classes.dex)
01-26 19:54:11.344 W/ActivityManager( 484): Process com.tytung.leo.lowsound has crashed too many times: killing!
http://pastebin.com/cYvK5cJK

2) When I put 777 rights for /data/dalvik-cache, the LowSoundFixer works fine.
01-26 20:36:07.078 D/LowSoundFixer( 2452): Silence.ogg is played
http://pastebin.com/TxR9miD8

The owners of these files are (LowSoundFixer and HwaSettings are at vendor directory at installation):
system@vendor@app@HwaSettings.apk@classes.dex
uid=1000/system gid=1000/system
system@vendor@app@LowSoundFixer.apk@classes.dex
uid=10056/com.tytung.leo.lowsound gid=10056/com.tytung.leo.lowsound

vendor@app@HwaSettings.apk@classes.dex
uid=1000/system gid=41000
vendor@app@LowSoundFixer.apk@classes.dex
uid=1000/system gid=50056

I can't understand why, but the dalvik engine creates the .dex file as com.tytung.leo.lowsound (10056 in my system) user, not system.
OR IS NOT the dalvik engine that creates the file?
Missing any kind of 'su'?

3) Using 777 for /data/dalvik-cache may be a workaround, BUT, I don't know if it is dangerous...
Is it dangerous???


Thanks,
apsspub

Hi all,

Tytung, thanks for your awesome work! With kitkat my HD2 got a revival!

1) I have problems with Android profiles (using kitkat ROM).
I use the Night Profile, and it's supposed to DON'T play notification sound when a SMS message arrives.
But it is played.
In the logcat you can see changing to Night profiles (it is called "Noche" in spanish).
http://pastebin.com/696wnuh5

2) The profiles were working fine for v.2.7-JB
In the logcat you can see changing to Night profiles (it is called "Noche" in spanish).
http://pastebin.com/r3N4Wyde

I don't know how to analize the logcat to check if ths sound is played or not.

Does Anybody uses this feature and have the same problem?

Thanks,
apsspub

gade12 wrote:
For the error with LowSoundFixer i have moved app to /system/app and it work...

+1

apsspub wrote:Hi all,

Tytung, thanks for your awesome work! With kitkat my HD2 got a revival!

My feedback for the LowSoundFixer problem:

1) Using 771 rights for /data/dalvik-cache, the LowSoundFixer stops working, and in the log cat we can see:
01-26 19:54:01.704 I/dalvikvm( 2918): Unable to open or create cache for /system/vendor/app/LowSoundFixer.apk
(/data/dalvik-cache/system@vendor@app@LowSoundFixer.apk@classes.dex)
01-26 19:54:11.344 W/ActivityManager( 484): Process com.tytung.leo.lowsound has crashed too many times: killing!
http://pastebin.com/cYvK5cJK

2) When I put 777 rights for /data/dalvik-cache, the LowSoundFixer works fine.
01-26 20:36:07.078 D/LowSoundFixer( 2452): Silence.ogg is played
http://pastebin.com/TxR9miD8

The owners of these files are (LowSoundFixer and HwaSettings are at vendor directory at installation):
system@vendor@app@HwaSettings.apk@classes.dex
uid=1000/system gid=1000/system
system@vendor@app@LowSoundFixer.apk@classes.dex
uid=10056/com.tytung.leo.lowsound gid=10056/com.tytung.leo.lowsound

vendor@app@HwaSettings.apk@classes.dex
uid=1000/system gid=41000
vendor@app@LowSoundFixer.apk@classes.dex
uid=1000/system gid=50056

I can't understand why, but the dalvik engine creates the .dex file as com.tytung.leo.lowsound (10056 in my system) user, not system.
OR IS NOT the dalvik engine that creates the file?
Missing any kind of 'su'?

3) Using 777 for /data/dalvik-cache may be a workaround, BUT, I don't know if it is dangerous...
Is it dangerous???


Thanks,
apsspub

Thanks. Very good analysis.
As other users said, try to move LowSoundFixer.apk to /system/app

HwaSettings is built as a system app which is signed by a platform key.
But LowSoundFixer is just an user app. It didn't need any system permission to play Silence.ogg in order to fix the low sound issue.
I think Kitkat may change permissions for the /system/vendor/app folder. That's why /system/vendor/app/LowSoundFixer.apk works well on JellyBean.
I will move LowSoundFixer.apk to /system/app folder in next release.

Hi tytung, i am just checking whether we are using the apr 2013 JB adreno drivers https://developer.qualcomm.com/mobile-d ... tion-tools in this and in the cm10 roms? Or are we still using the ics drivers? I couldn't see a mention of them in your changelogs.
Thanks

tytung wrote:I think Kitkat may change permissions for the /system/vendor/app folder. That's why /system/vendor/app/LowSoundFixer.apk works well on JellyBean.

I believe you are correct. There is definitely something different about how KK deals with apps which are moved to /system. An app called Secure Settings had a Helper app to accomplish a number of system level tasks which completely stopped working with KK. The Helper app was being moved to /system but restricted by KK and did not function. He recently deprecated the Helper app and recoded his app heavily to resolve the issue.

NYLimited wrote:
I believe you are correct. There is definitely something different about how KK deals with apps which are moved to /system. An app called Secure Settings had a Helper app to accomplish a number of system level tasks which completely stopped working with KK. The Helper app was being moved to /system but restricted by KK and did not function. He recently deprecated the Helper app and recoded his app heavily to resolve the issue.

I've noticed the same thing on KK builds for the Amaze. I thought the issue affected only that device and was caused by some bug in how the devs there were implementing KK. Now that I see your post here things makes more sense.

Unlike the HD2, the Amaze has a large amount of internal space to work with. The '/system' partition is 1.58GB and the '/data' partition is 2.64GB. On the stock Sense ROM much of the space in '/system' gets used by a combination of HTC and T-Mobile bloat and odex files. Every aftermarket ROM is deodexed so there's a lot of extra space in '/system' after installing one. Depending on whether the ROM is Sense or AOSP based, there's as much as 1GB free in that partition.

What I usually do is push all of the Google apps I use and many important utilities that I know have no spyware or trackers into '/system' which frees up more space on '/data' for other apps. I also work system app updates into back into the ROM with Titanium Backup to further free up space. However with KK many apps I push into '/system' no longer function as expected. Some important features requiring escalated privileges fail to work. Examples being my favorite file managers which need root to function correctly. It's not an issue with JB. It's really annoying too because having to run these apps from '/data' means less space for other apps there.

Thanks for posting this info. At least I know it's not an isolated problem.

Hi,
I have installed Simpsons Tapped Out on Kitekat v4.1 and it was working fine, but after upgrading to 4.3 it always stops working.
Here are the steps I tried:
1. v4.1 NAND+Data on Ext - working
2. v4.3 NAND+Data on Ext - NOT working
3. v4.3 NativeSD - not working
4. v4.1 NAND+Data on Ext again - working
Now, I can live without Simpsons game, I always prefered to have latest tytung's build
Has something significant chaned in HWA? I don't see this game listed in HWA settings in both 4.1 and 4.3.
Or maybe it's some EA's problem
I don't want to solve it, but I thought it's interesting. Everything else is working without problems, except low sound fixer crash.

Regards,
my HTC HD2, 4 years old, and always on Tytung's android (or was it Tyween before?)

gade12 wrote:

For the error with LowSoundFixer i have moved app to /system/app and it work...

I put the downloaded *.apk in this folder with root file-explorer and then clicked on it, it asked me if i wanted to update the app, i said yes.
Now it seems to work! (LowSoundFixer didn't crash on call)

Are those the right steps? (In case any other noobs were wondering)