Just been looking at the new sense 5 screenshots . After using VTS and seeing what everyone else is developing in the M10 thread i must admit im a bit dissapointed . Maybe HTC should start using VTS as I've seen some themers create some amazing things for our devices .which to me put the "new" sense 5 to shame . Diamondback and team you guys rock , awesome product .
If a post has been helpful don't forget to press the thanks button
One little thing: some text is cut off in the file menu (see attached screenshot). I don't think this happened with whatever build was available on 1/19 (I had that one, but I wanted to screenshot the installation process for a guide I'm making, so I uninstalled the 1/19 one and installed today and had some trouble finding the Settings again, haha!). BUT, I might be wrong and it's always been like this.
I'm on a 1920x1080 screen, DPI set to 110% (custom). That DPI might be the issue?
Also, maybe a noob mistake I'm making, but where is ADB pull putting files? I checked \External, nothing. I checked desktop, nothing. I searched for boobs.apk, nothing.
Code:
C:\Program Files (x86)\Virtuous Ten Studio\External\ADB>adb pull /system/framewo
rk/framework-res.apk framework-res.apk
4114 KB/s (30188437 bytes in 7.164s)
C:\Program Files (x86)\Virtuous Ten Studio\External\ADB>adb pull /system/framewo
rk/framework-res.apk /desktop
4556 KB/s (30188437 bytes in 6.470s)
C:\Program Files (x86)\Virtuous Ten Studio\External\ADB>adb pull /system/framewo
rk/framework-res.apk boobs.apk
3320 KB/s (30188437 bytes in 8.878s)
C:\Program Files (x86)\Virtuous Ten Studio\External\ADB>
EDIT: Couldn't find it. Just used "remote" and it worked! I think...see issue below, haha:
---
I had a little trouble today:
1) I pushed a modded SystemUI.apk via VTS and my phone in recovery (this easy mod: http://forum.xda-developers.com/show...8&postcount=18)
2) Said it pushed successfully, but I'm not sure it did (mod didn't work and SystemUI.apk in phone was original, not new)
3) So, then I pushed SystemUI.apk via ADB and my phone on. Restarted to a missing notification bar. No idea what happened, so I fixed permissions in recovery (to 0644) of SystemUI.apk.
4) Phone entered bootloop -> nandroid back before mod attempt.
It's probably something I've done, but I had two quick questions: 1) Does VTS fix permissions of files before pushing them? and 2) Does VTS remount /system when pushing files to it? Err...3) Does anyone know what I did wrong?
1) Created new project. Uploaded framework-res.apk and SystemUI.apk through "Remote". Used "Keep old signature" because it's a system app and changed smali API to 4.1 (I'm on 4.1.1)
2) Found XML file, edited file via copy/paste, saved it.
3) Hit build, no errors.
4) And attempted to push, starting with step 1 above.
--
Tried again; unable to push with VTS nor ADB! Any reason why? I can pull files fine. I'm using a stock 4.1.1, rooted, stock kernel (using adbd insecure). I specifically remount using adb before hitting "push," but even then after 15 minutes of waiting, still "pushing...."
One little thing: some text is cut off in the file menu (see attached screenshot). I don't think this happened with whatever build was available on 1/19 (I had that one, but I wanted to screenshot the installation process for a guide I'm making, so I uninstalled the 1/19 one and installed today and had some trouble finding the Settings again, haha!). BUT, I might be wrong and it's always been like this.
I'm on a 1920x1080 screen, DPI set to 110% (custom). That DPI might be the issue?
Yes you are right, your custom DPI is the problem. In fact it's very hard to make an app fully compatible with different DPI settings.
Even Microsoft's own apps usually don't work too well with higher DPIs.
So unless there aren't any major bugs caused by this (cut off text is not so major for me in this case ) I probably won't try to fix it. Sorry
Quote:
Originally Posted by ikjadoon
Also, maybe a noob mistake I'm making, but where is ADB pull putting files? I checked \External, nothing. I checked desktop, nothing. I searched for boobs.apk, nothing.
Code:
C:\Program Files (x86)\Virtuous Ten Studio\External\ADB>adb pull /system/framewo
rk/framework-res.apk framework-res.apk
4114 KB/s (30188437 bytes in 7.164s)
C:\Program Files (x86)\Virtuous Ten Studio\External\ADB>adb pull /system/framewo
rk/framework-res.apk /desktop
4556 KB/s (30188437 bytes in 6.470s)
C:\Program Files (x86)\Virtuous Ten Studio\External\ADB>adb pull /system/framewo
rk/framework-res.apk boobs.apk
3320 KB/s (30188437 bytes in 8.878s)
C:\Program Files (x86)\Virtuous Ten Studio\External\ADB>
EDIT: Couldn't find it. Just used "remote" and it worked! I think...see issue below, haha:
---
I had a little trouble today:
1) I pushed a modded SystemUI.apk via VTS and my phone in recovery (this easy mod: http://forum.xda-developers.com/show...8&postcount=18)
2) Said it pushed successfully, but I'm not sure it did (mod didn't work and SystemUI.apk in phone was original, not new)
3) So, then I pushed SystemUI.apk via ADB and my phone on. Restarted to a missing notification bar. No idea what happened, so I fixed permissions in recovery (to 0644) of SystemUI.apk.
4) Phone entered bootloop -> nandroid back before mod attempt.
It's probably something I've done, but I had two quick questions: 1) Does VTS fix permissions of files before pushing them? and 2) Does VTS remount /system when pushing files to it? Err...3) Does anyone know what I did wrong?
1) Created new project. Uploaded framework-res.apk and SystemUI.apk through "Remote". Used "Keep old signature" because it's a system app and changed smali API to 4.1 (I'm on 4.1.1)
2) Found XML file, edited file via copy/paste, saved it.
3) Hit build, no errors.
4) And attempted to push, starting with step 1 above.
--
Tried again; unable to push with VTS nor ADB! Any reason why? I can pull files fine. I'm using a stock 4.1.1, rooted, stock kernel (using adbd insecure). I specifically remount using adb before hitting "push," but even then after 15 minutes of waiting, still "pushing...."
When doing adb pull it should probably place the files in the folder where the adb.exe is.
No, VTS won't change any permissions when pushing a file. I am not aware that this is needed btw. Never had any problems so far related to premissions.
Yes, VTS calls adb remount prior to pushing. You can actually see this in the debug log.
Yes, I partly know what's happening. Your problem is a broken signature.
You selected to use the old signature but then edited a file which is protected by this signature.
Therefore Android refuses to load your apk. The half solution would be to sign the apk with a proper signature (ie. use the test signature option in VTS).
However, this will lead to another error. Android will still refuse to load your apk, because its signature is mismatched.
All system apps have to be signed with the same key in order to get loaded by the package manager. Otherwise they will be rejected.
To circumvent this you need to patch services.jar to ignore the mismatched signature.
There are a few tutorials around on how to do that.
Quote:
Originally Posted by torxx
Diamondback, imho you should disable it from the beginning in the next version
Happens on nearly every apk when having it enabled..
Actually people should rather use a newer apktool version with support for that feature.
But I see this is a common problem and I am currently thinking about a few things to solve problems like this.
Do you find yourself obsessively jumping from ROM to ROM? And do you hate having to restore a full … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?