Related
After reading many posts about not being able to the XDA App with JIT enabled… I decided to post this…
Here’s something I happened to “stumble” upon while playing around with ROMs with JIT-enabled. Hopefully this will help some others enjoy the XDA/Tapatalk App from their phones with JIT-enabled
I have done this on two (2) Cyanogen based ROMs (CELB2.4 and CE1.1). Both had JIT enabled by default.
In any case, I love being able to use the XDA App from my phone to feed my addiction However, I also enjoy having JIT and the goodness that comes along with it! So… I was playing with CELB2.4 and testing some battery life. After disabling JIT, I instantly started up XDA (as I was unable to use due to FC’s with JIT enabled). I logged in and browsed around. However, disabling JIT had no effect on my battery life, so I decided to re-enable. Later, without thinking, I started up XDA and browsed around some more. It didn’t hit me until a few minutes later that JIT was enabled and I was able to use XDA.
In any case, I loaded up a NAND of CE1.1 and did the same thing, with the same result. XDA app worked perfectly… and I’m still getting over 5.3 mflops
I think there are other apps that have issues with JIT, however, I personally don’t use them. Hope this helps others! Would love to know what ROMs this “trick” works with, and/or which it doesn’t.
------------------------------------------------------------------------------------
I highly recommend doing a NAND backup before doing anything. It's just good practice!
There are a few methods to enable/disable JIT... here's what I did (using a Windows machine):
Disable JIT via adb:
adb remount
abd pull /system/build.prop build.prop
Open build.prop in Notepad/Wordpad or favorite text editor (file will be in the working directory)
find the line:
dalvik.vm.execution-mode=int:jit
replace with:
dalvik.vm.execution-mode=int:fast
SAVE
adb push build.prop /system/
Reboot Phone
------------------------------------------------------------------------------------
After disabling JIT, reboot, open up XDA App, login and browse around (as a side note, I created a favorite to the Eris Forums). Then, close out of XDA App, and then re-enable JIT and reboot.
------------------------------------------------------------------------------------
Enable JIT via adb:
adb remount
abd pull /system/build.prop build.prop
Open build.prop in Notepad/Wordpad or favorite text editor (file will be in working directory)
find the line:
dalvik.vm.execution-mode=int:fast
replace with:
dalvik.vm.execution-mode=int:jit
SAVE
adb push build.prop /system/
Reboot Phone
------------------------------------------------------------------------------------
Alternatively you can also use a program like Root Explorer to find the build.prop file in the /system/ folder and edit/save/reboot.
Again, would love to know the results this has for others!
------------------------------------------------------------------------------------
Thanks to a post from thenestor, it's been discovered that version 0.9 of the XDA/Tapatalk app works just fine with JIT (regardless if an AOSP or other ROM). I'm currently using version 0.9 on xtrROM and it works great. I have attached the zip with the 0.9 apk. It has a "funky" name... and I didn't rename... I simply used Astro to install the apk. works great!
MODS: if for any reason I am NOT allowed to have version 0.9 posted, please let me know, and I will take the attachment down ASAP.
I vote for a toggle app/widget
Root Explorer
It works! Used root explorer...nor really that hard to do. Thanks for sharing your discovery.
didnt work with Aloysius v12. Oh well.
paintguy said:
It works! Used root explorer...nor really that hard to do. Thanks for sharing your discovery.
Click to expand...
Click to collapse
which ROM where you using?
I have not had time to try on my ROM but would love to know if it is a viable work around to try and incorporate...
zach.xtr said:
which ROM where you using?
I have not had time to try on my ROM but would love to know if it is a viable work around to try and incorporate...
Click to expand...
Click to collapse
I was using Eris Lightening Bolt 2.5.
When I loaded the app the first time on my ELB install, it crashed. However, I reloaded it straight away and it worked. I did not disable JIT or do anything else to make it work, just restarted the app. It hasn't crashed since. I have, however, had it sit and spin on "Processing".
Didn't work on latest ErisLightningBolt 1.4.
1. XDA didn't work w/stock config.
2. Changed int:jit to int:fast.
3. Rebooted.
4. XDA worked! Signed in, created some favorites.
5. Changed int:fast back to int:jit.
6. Rebooted.
7. XDA FCs.
I can confirm that it works.
Eris Lightning Bold 2.5
Thanks!
Disable JIT via adb:
adb remount
abd pull /system/build.prop build.prop
------------------------------------------------------------------------------------
Enable JIT via adb:
adb remount
abd pull /system/build.prop build.prop
Open build.prop in Notepad/Wordpad or favorite text editor (file will be in working directory)
find the line:
dalvik.vm.execution-mode=int:fast
replace with:
dalvik.vm.execution-mode=int:jit
SAVE
adb push build.prop /system/
Reboot Phone
------------------------------------------------------------------------------------
Click to expand...
Click to collapse
I'm running CM:E 1.1, and can't seem to find how to disable jit. Framework43's rom. I miss my xda time saver tapatalk. If anyone can help. I would appreciate it, greatly. Thank you much.
Re: [Workaround] XDA/Tapatalk App - JIT
From my testing seem to work only for AOSP based builds. .. must be something in the HTC framework causing interference
-------------------------------------
Sent via the XDA Tapatalk App
zach.xtr said:
From my testing seem to work only for AOSP based builds. .. must be something in the HTC framework causing interference
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Thank you for the response. Ill message framework43 about it to see if he can help me further into this issue of mine.
Confirm Also
I confirm that this worked on CELB v2.5
Turnyface said:
I can confirm that it works.
Eris Lightning Bold 2.5
Thanks!
Click to expand...
Click to collapse
Re: [Workaround] XDA/Tapatalk App - JIT
@zach.xtr
I found out that all I had to do was add the string to build.prop
I followed a POST on "Jcase's Universal JIT Update"
I added these two strings at the bottom of build.prop
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize=38m
That fixed the issue with xda tapatalk closing randomly. I still have yet to re-enable "jit" to see if the workaround works.
Thank you for the help and replies.
-------------------------------------
Sent via the XDA Tapatalk App
Edit: I can confirm that the work around does NOT work on CyanogenEris v1.1 (jit enabled)
(Above shows what to add if missing.)
P.S.
It did NOT work for me, can't confirm it overall.
@someone who can help.
How would I go about fixing the market issues?
Can't install apps, I can only push the ones I have backed up.
jetmclean said:
I confirm that this worked on CELB v2.5
Click to expand...
Click to collapse
I can confirm this as well
If you don't want to disable JIT, or if you're on a ROM where disabling and re-enabling doesn't work, just downgrade to "xda-developers app v0.9" (not sure which version of the real Tapatalk) and it works with JIT.
is 0.9 a google apk search?
have a link?
sweet! found it! much like thenestor, i had to find it using some "crafty" methods! lacks some of the "favorites" w/sub-forums... but works VERY nicely with JIT.
thanks for the tip thenestor... good stuff!
if i'm allowed to post 0.9 version, i will gladly do so! (nothing wrong with it, i hope?).
tenzomonk said:
sweet! found it! much like thenestor, i had to find it using some "crafty" methods! lacks some of the "favorites" w/sub-forums... but works VERY nicely with JIT.
thanks for the tip thenestor... good stuff!
if i'm allowed to post 0.9 version, i will gladly do so! (nothing wrong with it, i hope?).
Click to expand...
Click to collapse
Can you share some of the craft involved in finding this? Thanks!!
Cary
Re: [Workaround] XDA/Tapatalk App - JIT
@zach.xtr
I found out that all I had to do was add the string to build.prop
I followed a POST on "Jcase's Universal JIT Update"
I added these two strings at the bottom of build.prop
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize=38m
That fixed the issue with xda tapatalk closing randomly. I still have yet to re-enable "jit" to see if the workaround works.
Thank you for the help and replies.
-------------------------------------
Sent via the XDA Tapatalk App
Edit: I can confirm that the work around does NOT work on CyanogenEris v1.1 (jit enabled)
(Above shows what to add if missing.)
P.S.
It did NOT work for me, can't confirm it overall.
@someone who can help.
How would I go about fixing the market issues?
Can't install apps, I can only push the ones I have backed up.
Click to expand...
Click to collapse
Thanks for this! I can confirm it works on white widow 3.2. I play toss it quite a bit so downgrading xda wasn't a
complete fix for me.
-------------------------------------
Sent via the XDA Tapatalk App
I'm a noob when it comes to coding and I need help. Not sure where this goes forum wise but can anyone help me remove the 270 rotation and just have the normal 180? Move me if this is general, I just can't stand the 270 anymore. I'm running baked snack 1.4 with acs 1.6 kernel and the frost remix theme. Help!
Sent from my SPH-D700 using XDA App
I would instead like to use this on a stock ROM, so any insight on this would be equally helpful for the opposite
In your build.prop file, change this line...
windowsmgr.support_rotation_270=true
to
windowsmgr.support_rotation_270=false
And how would we go about adding it? I mean, I know it's in the framework, so it means decompiling, right?
Sent from my SPH-D700
Forcystos said:
And how would we go about adding it? I mean, I know it's in the framework, so it means decompiling, right?
Sent from my SPH-D700
Click to expand...
Click to collapse
Its not in the framework, its just part of the build.prop file, thats it (sounds wayyy too simple, I know).
So basically just do the opposite, change false to true. Normally I'd use something like "Root Explorer" and edit the build.prop file in the text edit mode.
schizopunk said:
Its not in the framework, its just part of the build.prop file, thats it (sounds wayyy too simple, I know).
So basically just do the opposite, change false to true. Normally I'd use something like "Root Explorer" and edit the build.prop file in the text edit mode.
Click to expand...
Click to collapse
yup, just checked this out after reading ur first post in here, nice, and way too simple
thanks for the info
And this works on stock ROM? Not baked snack?
Sent from my SPH-D700
Forcystos said:
And this works on stock ROM? Not baked snack?
Sent from my SPH-D700
Click to expand...
Click to collapse
Works on any rooted rom
Just tested, and it worked. I just found it strange that it worked out of the box, since I hadn't seen this on any stock phone.
Sent from my SPH-D700
any froyo fix
Has anyone come up with a froyo fix for the 270° rotation? It used to be an easy fix, but with the froyo I can't find it in the build prop. Any ideas?
easiest way I know...
dl terminal from the market
open up and type "su" and then hit the enter button
then type "180forme.sh" and then hit the enter button
then reboot
Sent through the Matrix
Cool thanks for the lead.
Well no luck with the 180forme.sh in terminal
Any other thoughts?
Did you change directory to the one with the 180 degree script command?
Epic Experience 1.2.0.8/Phoenix 1.49s/Elegant Steel .02
make sure its "terminal emulator" that you downloaded. "su" allows superuser to let terminal make changes. "180forme.sh" should work. its what hero suggested when asked how to go back to 180 rotation. and make sure that you reboot your phone after. it worked perfectly for me. maybe try reflashing and then using terminal.
Sent through the Matrix
fromchaos0646 said:
make sure its "terminal emulator" that you downloaded. "su" allows superuser to let terminal make changes. "180forme.sh" should work. its what hero suggested when asked how to go back to 180 rotation. and make sure that you reboot your phone after. it worked perfectly for me. maybe try reflashing and then using terminal.
Sent through the Matrix
Click to expand...
Click to collapse
That was a custom script that hero wrote for his rom. Its not going to work on anything else as its not included in anything other than baked snack
Sent from my SPH-D700 using XDA App
Thanks for the info, will bide my time. Once the super-customs start rolling, there will be a fix. Thanks
Sent from my brain
Bored at work so take this with a grain of salt. Anyone try and add the line from eclairs build prop to their froyo build prop? Might not work but like I said I'm bored here...
sent from an Epic4g through the cosmos
Edit: added that line with root explorer and cleared dalvik and no go...was worth a try I guess
idkwhothatis123 said:
That was a custom script that hero wrote for his rom. Its not going to work on anything else as its not included in anything other than baked snack
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
thank you for that info. I did not know that. so in that case, disregard my previous posts if your not using baked snack.
Sent through the Matrix
raiderep said:
Bored at work so take this with a grain of salt. Anyone try and add the line from eclairs build prop to their froyo build prop? Might not work but like I said I'm bored here...
sent from an Epic4g through the cosmos
Edit: added that line with root explorer and cleared dalvik and no go...was worth a try I guess
Click to expand...
Click to collapse
Doesn't work bro. I've tried
Captivate currently had TWICS. Its base code from cm9 with TW launcher and Samsung gs3 add on with devil kernel. Running this o my cappy. Super fast and stable. Just an outstanding rom.
Can someone port this to vibrant please!
What are you looking at shortbus......
*NOT SURE/CONFIRMED
But since it is in the line of the original galaxy s, I think you can just flash it, and then change modem/kernel/key layout, which is done by a script (forgot what its called in our development section)
ok, i found it
http://forum.xda-developers.com/showthread.php?t=1623840
Using that, you SHOULD be able to flash any Galaxy S ROM (except the 4G)
If it doesn't work, nothing will go wrong, most likely you will
1) boot loop
2) key layout will be mixed up(easy fix)
3) no connection (change modem/kernel)
*you said this was TWICS, make sure it is ICS and not just themed to look like TWICS.
Link to rom please?
http://forum.xda-developers.com/showthread.php?t=1625619
What are you looking at shortbus......
hey, instead of using it from the captivate, use it from the i9000
http://forum.xda-developers.com/showthread.php?t=1608624
same thing, captivate guy ported from i9000, just you'll probably get updates etc faster.
P.S. tell us how it goes.
xriderx66 said:
hey, instead of using it from the captivate, use it from the i9000
http://forum.xda-developers.com/showthread.php?t=1608624
same thing, captivate guy ported from i9000, just you'll probably get updates etc faster.
P.S. tell us how it goes.
Click to expand...
Click to collapse
OK so I tried it from the captivate before I saw this post. Installed rom and before it gave install complete it auto rebooted. The rom was on my phone but up was down left was right ie screen was in landscape then when I turn it sideways it would go to normal view. I rebooted to recovery and ran patch then reboot and wouldn't get past vibrant screen. I will try again with i9000 rom and let you know the results.
Sent from my SGH-I897 using XDA
Tried it with i9000 rom but it aborted error status 7. I think my zip was bad. Going to try again.?
Sent from my SGH-T959 using xda premium
Edit: just read FAQ need to change some things in rom file. Will update after I try this
samsgun357 said:
Tried it with i9000 rom but it aborted error status 7. I think my zip was bad. Going to try again.?
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
Try to flash the Subzero kernel from here: (use build 80 not 128) http://rootzwiki.com/topic/22833-kernelics15-june-subzero-v14-build-128-brain-dead-and-loving-it/
If you already tried it from Subzero kernel; try the Glitch kernel, its on these dev sections.
Flash either of those to the ROM you currently have, and then try to flash it.
EDIT----------------
"if you are getting status 7 or getprop error then a little work from your side is needed
extract the rom to a folder then go to /extracted folder/META - INF/com/Google/Android from there open updater-script and remove all getprop lines
come back to META - INF folder and delete all three files
zip the file and flash it in recovery
NOTE:- to edit updater script use jota text editor(android), notepad (windows)"
It's in the patch's thread.
Do that.
I followed the thread exactly used jota changed everything and tried again. It just aborts install. I haven't given up. Gonna try again tomorrow. It beat me tonight but not for good! Thanks for everything x.
Sent from my SGH-T959 using xda premium
firstly I want to tell you that because of not having a vibrant to test the patch is in beta
what you can do is open updater script with jota text editor and remove all those getprop lines from the script and as a security step what you can do is press menu button then tap on file and tap on line break then select (lf for android/Linux) save the file go to meta-inf folder and remove all those cert files
zip the package again and flash no need to sign it again for further help you can ask me also in the patch thread
dhlalit11 said:
firstly I want to tell you that because of not having a vibrant to test the patch is in beta
what you can do is open updater script with jota text editor and remove all those getprop lines from the script and as a security step what you can do is press menu button then tap on file and tap on line break then select (lf for android/Linux) save the file go to meta-inf folder and remove all those cert files
zip the package again and flash no need to sign it again for further help you can ask me also in the patch thread
Click to expand...
Click to collapse
Thanks for input. I first tried it using a captivate port and it would install then I would run patch and it wouldn't boot past vibrant screen. Then I got the original galaxy s rom that the cappy rom was ported from. It gave the error so I proceeded to change the file as per op instructions. It would abort install with but no error status. I did it twice to make sure. If I changed all the get prop from i9000 to t959 would it work?
Sent from my SGH-T959 using xda premium
you should not replace them instead just remove them
after flashing if it gives error then reboot device and with any root explorer app go to /cache/recovery and upload both the files I will see what the error is and then I can troubleshoot better
So guys I'm the twics porter to the cappy twics will soon be called remics I've been a part of a team that took over twics and I will soon be releasing to captivate
Sent From My ICS Cappy Using Tapatalk 2
patrick8996 said:
So guys I'm the twics porter to the cappy twics will soon be called remics I've been a part of a team that took over twics and I will soon be releasing to captivate
Sent From My ICS Cappy Using Tapatalk 2
Click to expand...
Click to collapse
Do you think it'd be possible for you to release a version for Vibrant as well? Since not much will have to be changed from Captivate.
Just modem/kernel, and possibly build.prop
dhlalit11 said:
you should not replace them instead just remove them
after flashing if it gives error then reboot device and with any root explorer app go to /cache/recovery and upload both the files I will see what the error is and then I can troubleshoot better
Click to expand...
Click to collapse
I did remove and it just aborts with no explanation.
Sent from my SGH-T959 using xda premium
xriderx66 said:
Do you think it'd be possible for you to release a version for Vibrant as well? Since not much will have to be changed from Captivate.
Just modem/kernel, and possibly build.prop
Click to expand...
Click to collapse
Yes please! I love it on my cappy and want it on my vibrant also!
Sent from my SGH-T959 using xda premium
and what about uploading the error log from /cache/recovery
I took the twics add on from mr.mad for gs1 running cm9/slim and flashed on my vibrant running gummy 1.2.6 and it got stuck on boot . I reflashed gummy without wiping and now have all the apps from add on except for tw launcher. I guess that's a happy medium until we can get a port.
Sent from my SGH-T959 using xda premium
dhlalit11 said:
and what about uploading the error log from /cache/recovery
Click to expand...
Click to collapse
How do I extract it from root browser?
Posse magnet......
samsgun357 said:
How do I extract it from root browser?
Posse magnet......
Click to expand...
Click to collapse
Just go to that file, copy it and paste it into your SD or something, and then upload it from there.
Because I have flashed a new rom and kernel the recovery log doesn't have the abort/error info...
Posse magnet......
This is the fix for Audio/Sound on any Jelly Bean ROM on the HP Touchpad
JB needs this file "/system/etc/media_codecs.xml"
This file is missing, but simply copying the file there using Root Explorer or any file explorer with root access works. This does not require a permissions change. The file is not there originally so you won't be overwriting anything. I did this fix on my Atrix 4G and it worked perfectly. It is universal and will work on any Jelly Bean ROM on any device with this issue.
Here is a link to the file:
http://forum.xda-developers.com/attachment.php?attachmentid=1207669&d=1342668760
Steps:
- Extract "media_codecs.xml"
- Copy it to /system/etc/
- Make sure to mount system as R/W (read/write) before pasting the file
- Reboot
- Sound Fixed!
atrix4g18 said:
This is the fix for Audio/Sound on any Jelly Bean ROM on the HP Touchpad
JB needs this file "/system/etc/media_codecs.xml"
This file is missing, but simply copying the file there using Root Explorer or any file explorer with root access works. This does not require a permissions change. The file is not there originally so you won't be overwriting anything. I did this fix on my Atrix 4G and it worked perfectly. It is universal and will work on any Jelly Bean ROM with this issue.
Here is a link to the file:
http://forum.xda-developers.com/attachment.php?attachmentid=1207669&d=1342668760
Steps:
- Extract "media_codecs.xml"
- Copy it to /system/etc/
- Make sure to mount system as R/W (read/write) before pasting the file
- Reboot
- Sound Fixed!
Click to expand...
Click to collapse
why dont you submit this to the git?
antp121 said:
why dont you submit this to the git?
Click to expand...
Click to collapse
I know about this fix and I know a lot about android but I don't know how git or github works. If you know how that would be great if you could submit it. If you look in the general forum there is a video of JB running and I'm trying to get in contact with the developer that made it (not the OP) this is a really simple fix and can be added to the ROM easily. I'm running JB on my Atrix 4G but not my touchpad I don't have access to a flashable zip for it. If I could get access to one I could confirm this. But I'm sure it will work because there is nothing atrix specific in the file; it is a general file that will work with any device.
atrix4g18 said:
This is the fix for Audio/Sound on any Jelly Bean ROM on the HP Touchpad
JB needs this file "/system/etc/media_codecs.xml"
This file is missing, but simply copying the file there using Root Explorer or any file explorer with root access works. This does not require a permissions change. The file is not there originally so you won't be overwriting anything. I did this fix on my Atrix 4G and it worked perfectly. It is universal and will work on any Jelly Bean ROM on any device with this issue.
Here is a link to the file:
http://forum.xda-developers.com/attachment.php?attachmentid=1207669&d=1342668760
Steps:
- Extract "media_codecs.xml"
- Copy it to /system/etc/
- Make sure to mount system as R/W (read/write) before pasting the file
- Reboot
- Sound Fixed!
Click to expand...
Click to collapse
cm10
!!!!!!!!!!!!!!!!!!
Sent from my cm_tenderloin using XDA Premium HD app
sahhar1993 said:
cm10
!!!!!!!!!!!!!!!!!!
Sent from my cm_tenderloin using XDA Premium HD app
Click to expand...
Click to collapse
yeah mon! I already got it on my Motorola Atrix 4G it's awesome. People say it's not a big update; it is. Google now, offline voice dictation. It's great.
Is it me or are there no jelly bean ROM's out yet for the touchpad?
Sent from my Galaxy Nexus
That's exactly what I was thinking, if there actually is then could someone shed some light on this please?
Regards
Sent from my MT15i using xda premium
waynekirby said:
That's exactly what I was thinking, if there actually is then could someone shed some light on this please?
Regards
Sent from my MT15i using xda premium
Click to expand...
Click to collapse
Someone is developing one. This will solve the sound issue they have and anyone else who builds one can solve this issue. This will help us get closer to an alpha release.
No there aren't. I believe the OP is just making an intelligent guess to fix sound on the preview by Reverendkjr in the general section
Sent from my Desire S using Tapatalk 2
dan-fish said:
No there aren't. I believe the OP is just making an intelligent guess to fix sound on the preview by Reverendkjr in the general section
Sent from my Desire S using Tapatalk 2
Click to expand...
Click to collapse
Correct. However it is not an "intelligent guess" I am runing jelly bean on my Motorola Atrix 4G and this solved the problem. The file is not atrix related and is universal. Anyone wanting to put together jelly bean for the touchpad will need this file. On that youtube video with the preview the person who created the rom (jcsullins) says, "Right now, the biggest issue to be addressed is audio (does not work)."
This provides a fix for him and any other person looking to make it work. I am 99% sure this will work but I do not have a flashable zip of jelly bean to try it. If I was provided with one I could test it out and upload a video to show it works.
Thanks for clarifying this
The sound problem could be related to Audio libs and not a XML or whatever the fix is, hope your right though, can't wait to get JB on my touchpad, I'm sure its a matter of days away
Regards
Sent from my cm_tenderloin using XDA Premium HD app
I don't know how old the video you refer to is but I'm running a CM10 build on my Kindle Fire for a bit over a week now and that file is present. And of course, I have sound. I would think JC Sullins already has access to that file in the github.
EDIT: A quick search reveals that this has already been pushed to various JB githubs over the last week or two since JB was "released", so I don't think this is a secret. I do like CM10 on my KF, so looking forward to a CM10 release for the TP by JC Sullins & Co...when it's ready.
Mike T
waynekirby said:
Thanks for clarifying this
The sound problem could be related to Audio libs and not a XML or whatever the fix is, hope your right though, can't wait to get JB on my touchpad, I'm sure its a matter of days away
Regards
Sent from my cm_tenderloin using XDA Premium HD app
Click to expand...
Click to collapse
Yeah man it's great on the Atrix and I'm sure it will be even better on the touchpad! I don't think it is libs though, because the ones used in CM9 would have worked. I'm close to certain it is this xml. However we will have to wait and see, I wish I could get a flashable zip without audio just to get this working.
webdroidmt said:
I don't know how old the video you refer to is but I'm running a CM10 build on my Kindle Fire for a bit over a week now and that file is present. And of course, I have sound. I would think JC Sullins already has access to that file in the github.
EDIT: A quick search reveals that this has already been pushed to various JB githubs over the last week or two since JB was "released", so I don't think this is a secret. I do like CM10 on my KF, so looking forward to a CM10 release for the TP by JC Sullins & Co...when it's ready.
Mike T
Click to expand...
Click to collapse
Good to know, I do wonder though because the developer that made the CM10 ROM for my atrix made it on the 17th he fixed it last night with that file. If jcsullins (the person that created the jelly bean rom without sound for the touchpad) if he built the ROM without acessing that github project then he may have (like the atrix CM10 developer) ran into this problem. Hopefully he will get back to me (I PM'd him earlier today) and we will see what happens.
atrix4g18 said:
This is the fix for Audio/Sound on any Jelly Bean ROM on the HP Touchpad
JB needs this file "/system/etc/media_codecs.xml"
This file is missing, but simply copying the file there using Root Explorer or any file explorer with root access works. This does not require a permissions change. The file is not there originally so you won't be overwriting anything. I did this fix on my Atrix 4G and it worked perfectly. It is universal and will work on any Jelly Bean ROM on any device with this issue.
Here is a link to the file:
http://forum.xda-developers.com/attachment.php?attachmentid=1207669&d=1342668760
Steps:
- Extract "media_codecs.xml"
- Copy it to /system/etc/
- Make sure to mount system as R/W (read/write) before pasting the file
- Reboot
- Sound Fixed!
Click to expand...
Click to collapse
Thanks, but the issue is more complicated. In CM9, we are using "wrapped" audiolibs from gingerbread. CM10 does not support that (yet).
BTW, I already had the media_codecs.xml file.
jcsullins said:
Thanks, but the issue is more complicated. In CM9, we are using "wrapped" audiolibs from gingerbread. CM10 does not support that (yet).
BTW, I already had the media_codecs.xml file.
Click to expand...
Click to collapse
jcsullins can you release early beta building of jelly bean?
thank you
Doesn't work on cm10 for sensation. File already existed and replacing it didn't so anything. You got me all excited. Thanks for sharing anyway.
jcsullins said:
Thanks, but the issue is more complicated. In CM9, we are using "wrapped" audiolibs from gingerbread. CM10 does not support that (yet).
BTW, I already had the media_codecs.xml file.
Click to expand...
Click to collapse
Oh true, I'm not much of a developer myself, so best of luck to you!
Sorry but is jellybean available for touchpad ?
Not yet
Sent from my rezound
Hello guys this is a fix for notification blur in MiniCM10. I tested it and it's working fine.
Instructions:
1) Open build.prop and add this line: debug.hwui.render_dirty_regions=false (i put this line under debug.enabletr)
2) Make sure that debug.enabletr is set on false (debug.enabletr=false)
3) Save and reboot
4) Enter CWM and wipe cache and dalvik cache
5) Reboot
NOTE: this is not my work. I'm just sharing what i have found on github.
Source: https://github.com/lgics/cm_device_lge_msm7x27-common/commit/bb3cbcd15cf8edb8b06d0f31e31de032089a3d65#commitcomment-1945021
Credits:
Cyanogenmod
WinSuk
Nice man good job. May actually want to go back to MiniCM10 now (that bug was pissing me off). Btw, how's the audio fix going ?
RohinZaraki said:
Nice man good job. May actually want to go back to MiniCM10 now (that bug was pissing me off). Btw, how's the audio fix going ?
Click to expand...
Click to collapse
Is still the same...i don't know how to improve it
Amazing work bro
Sent from my E15i using xda premium
deleted
Godra said:
I just flashed MiniCM10 and its already like that in build.prop
Click to expand...
Click to collapse
Follow the instructions... it's a different line because it starts with debug.hwui
xelyt said:
Follow the instructions... it's a different line because it starts with debug.hwui
Click to expand...
Click to collapse
Yeah, I got it Thank you again
Thanks. It worked flawlessly!
Nevertheless, I didn't need to wipe anything after modifying the "build.prop" file.