I'm trying to edit my build.prop to fool market making it believe tf101 is a Xoom (practically the same hardware). When I boot the system the settings for Manufacturer and some other works, but the ones for model and device doesn't work (it's ok on buiuld.prop but running getprop command returns still TF101), why?
What can i do to change there?
what kind of file editor are you using?
what kind of file editor are you using?and what is your purpose for changing build.prop? if for games just pm me..if for something else use es file explorer and click settings then check UP-TO-ROOT,ROOT EXPLORER,AND MOUNT FILE SYSTEM. so you could change variables
Yeps, its for games, specially the gameloft ones, which i have bought on market. I'm using vi as text editor, but that is not the problem. The editing/save is working fine. I can change ro.product.brand, ro.product.manufacturer just fine. The problem is, even being correctly saved on build.prop the properties ro.product.model and ro.product.device doesn't take effect on reboot. So, when i reboot, the build.prop file has all changed values i added but when i run (via adb shell) the getprop commands i get the following:
getprop ro.product.model ---> Transformer TF101 (should show Xoom)
getprop ro.product.manufacturer ----> Motorola (Ok)
Why is it happening?
is your ro.secure (I think that's what it's called, please correct me) set too 1 or 0. if it's 1 then it can cause problems with editing certain system files sticking.
If you're trying to bypass the device check for gameloft games, I posted a link for how in the themes and apps section for the TF101. Look at the order and chaos 1.1.2 thread.
Sent from my HTC Glacier using Tapatalk 2
Yeps, main reason is order and chaos. I can play the game on my tablet, but it doesn't run smooth. I was hoping to fool gameloft servers making it think it's a Xoom (cause we're almost the same hardware) to download the right files for Tegra. Currently I'm using the version for Milestone2 phone. I just backup the game with titanium backup on phone (app + data), restore backup on tablet, and copy downloaded content from phone sdcard to tablet internal sdcard. It works and game runs, but not smooth. My intention was to download content for xoom on this tablet, making it run smooth (hopefully). Checking your thread now. Thanks.
Thing O Doom said:
is your ro.secure (I think that's what it's called, please correct me) set too 1 or 0. if it's 1 then it can cause problems with editing certain system files sticking.
Click to expand...
Click to collapse
How does ro.secure work? And where can i change its value?
I2IEAILiiTY said:
If you're trying to bypass the device check for gameloft games, I posted a link for how in the themes and apps section for the TF101. Look at the order and chaos 1.1.2 thread.
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Great tip about editing game directly, I'm going to try that as I've done it many times before on other applications. Will post report soon
UPDATE: Doesn't seem to work on version 1.1.3 of the game. Apktool throws NullPointerException when trying to compile game back.
forum.xda-developers.com/showthread.php?t=1193737
Change ro.secure from 1 to 0. I think also flashing a ROM or stock rooted-deodexed/modded works. I've always had 0 though since I rooted.
r2beta0 said:
Great tip about editing game directly, I'm going to try that as I've done it many times before on other applications. Will post report soon
UPDATE: Doesn't seem to work on version 1.1.3 of the game. Apktool throws NullPointerException when trying to compile game back.
Click to expand...
Click to collapse
Not sure if you saw it later in that thread, but for version 1.1.3 you don't have to edit the apk. They took device check out, so all you need to do is pull the apk from your other device, install it, and then let the app download the files itself.
Someone else did manage to edit 1.1.3 and got it working, but I was lazy and decided to see if it works w/o editing the apk lines and it did.
Also, I personally use virtuous ten studio to edit apks. I actually waited til it was released before I started messing with stuff like that, I've never used apktool by itself.
You may have another line in /default.prop forcing ro.secure=1
If this is the case (verify with any text editor) the easiest way to solve is to flash another compatible kernel. The root filesystem "/" is the ramdisk, and is loaded from an image file at boot up, and thus any changes you make to any files in the ramdisk will just be reverted after a period of time or after a reboot.
Flashing a new kernel will essentially create a new image for the ramdisk, and the default.prop in any ramdisk with a custom kernel will definitely have ro.secure=0
Related
After painstakingly researching into jfupdater, fixing a bad adt and sdk installation, and realizing that both the 1.1 and 1.5 sources could not coexist in one project, it is done. This program will work for JACHero 1.7 / TwistedZeroP and later builds. Due to the pre-work nature of TwistedZero, this will ensure that at least one of the system.zip archives is on the ext partition (it may not provide the most updated programs, but it will at least allow the update to be installed) You have the option to poll all updates, just JACHero, just TwistedZeroP or just TwistedZeroM. So far, only JACHero's updates will download because I am still working on getting mine on a dedicated server. I will try to keep as up to date as possible with download availability. Anyway, without any further stalling:
http://twistedumbrella.googlepages.com/heroupdater.ui.apk
Updating to the latest *working* version
You will need to have transferred the build.prop file to the /system/ folder of the phone for this to work.
They are available through my site's main page for my builds, and for now on my google code for JACHero until I get a new page coded for that.
Currently working on getting my builds program ready. Default update type is TwistedZeroP (can be changed in menu). Program is now a free download on market. Hero Update.
Very nice......
great job man
Freakin Sick Just used it and it was awesome! It still displays downgrades buts thats fine! I love it!
kickfliprock13 said:
Freakin Sick Just used it and it was awesome! It still displays downgrades buts thats fine! I love it!
Click to expand...
Click to collapse
It will display downgrades if you either have a version it cannot detect that is compatible with the updates or haven't gone to the configuration menu and unchecked display downgrades
ace. i thought all the hero roms required a wipe before each upgrade so this comes as great news.
thanks
thefunkygibbon said:
ace. i thought all the hero roms required a wipe before each upgrade so this comes as great news.
thanks
Click to expand...
Click to collapse
You're still gonna get wiped depending on the build.
it told me error while downloading what am I doing wrong...?
Very nice . This will truly make things easier. Nice work Twisted and Jac =).
So..I get a message when using update. The update app says "Your system is running an unsupported OS. (Version unknown) Please manually upgrade to JACHero 1.7 / TwistedZeroP or later and try again"
I understand its still a work in progress..just reporting my experience with the process.
Is "M" not a newer version than "P"?
I would assume, that even if the updater could not find an update for M, that M would still be a supported version and that it would just give me an error of not able to find an update for it or something. Not that M is unsupported.
FYI for all..I downloaded the files via the phone, installed linda file manager, android .Zip app(AndroZip) and AppsInstaller app. I Extracted the build.prop with and androzip, moved the file to /system/ on the phone with Linda, installed the HeroUpdater.ui.apk with Appinstaller. And then I get that message about an unsupported OS.
Great idea, thank you Twisted & JAC!
How do I use it? It shows me TwistedZero 1.7P as an update - can I just download it and then it will be installed?
No wipe or something like that?
an error occured while downloading 1.7P ?!
tep065 said:
Very nice . This will truly make things easier. Nice work Twisted and Jac =).
So..I get a message when using update. The update app says "Your system is running an unsupported OS. (Version unknown) Please manually upgrade to JACHero 1.7 / TwistedZeroP or later and try again"
I understand its still a work in progress..just reporting my experience with the process.
Is "M" not a newer version than "P"?
I would assume, that even if the updater could not find an update for M, that M would still be a supported version and that it would just give me an error of not able to find an update for it or something. Not that M is unsupported.
FYI for all..I downloaded the files via the phone, installed linda file manager, android .Zip app(AndroZip) and AppsInstaller app. I Extracted the build.prop with and androzip, moved the file to /system/ on the phone with Linda, installed the HeroUpdater.ui.apk with Appinstaller. And then I get that message about an unsupported OS.
Click to expand...
Click to collapse
Did you reboot after copying the build.prop? Rebooting did it for me (seems like this file is read when the system comes up).
Do I replace the build.prop file I already have on my /system/ folder or do I not even need to worry about the build.prop?
jawash22 said:
Do I replace the build.prop file I already have on my /system/ folder or do I not even need to worry about the build.prop?
Click to expand...
Click to collapse
Yes, the idea is that you replace it. The only difference between both files is a new reference to the build name (so the apk can tell what version you are on). Nevertheless it's always a good idea to back things up before you overwrite any files (learned the hard way throughout the years . So simply do something like 'cp /system/build.prop /sdcard/build.prop.old' from the terminal or 'adb pull /system/build.prop' from your computer before actually replacing the build.prop file.
Configuration menu
jawash22 said:
Do I replace the build.prop file I already have on my /system/ folder or do I not even need to worry about the build.prop?
Click to expand...
Click to collapse
Ok, I just did an overwrite of my existing build.prop and it shows me the twisted 1.7 update, but I am on JAC 1.8. Hitting Menu does not bring up configuration menu...what's wrong?
Backup
DanOtero said:
Yes, the idea is that you replace it. The only difference between both files is a new reference to the build name (so the apk can tell what version you are on). Nevertheless it's always a good idea to back things up before you overwrite any files (learned the hard way throughout the years . So simply do something like 'cp /system/build.prop /sdcard/build.prop.old' from the terminal or 'adb pull /system/build.prop' from your computer before actually replacing the build.prop file.
Click to expand...
Click to collapse
Thanks alot..I should know by now about backing up system stuff. Anyways, I still can't get the Menu and at the bottom it says "Running Version:unknown". I used the JAC 1.8 build prop also. I'll leave it alone for now and see if anyone else on JAC reports bugs....thanks again Twisted! You are appreciated.
man! cyan needs one!
DanOtero said:
Did you reboot after copying the build.prop? Rebooting did it for me (seems like this file is read when the system comes up).
Click to expand...
Click to collapse
Yah...i didnt reboot after...just rebooted and i had an update available thanx..gonna run the update while watching transformerrss in imax theater
where's the file?
"They are available through my site's main page for my builds, and for now on my google code for JACHero until I get a new page coded for that."
That would spare 20minutes of timewasting
How do you transferred the build.prop file to the /system/ folder of the phone? thanks in advance.
Table of Contents:
Status
Purpose
Audience
Instructions
Download
ROM list to use with the app
STATUS:
UPDATE:
I'm abandoning this project for the time being. I would like to have this integrated into the installer as a separate option and not rely on an app to handle this. If anyone wants to pick it up or extend things further, I'm definitely open to it. I just don't see a need for this at this time.
However, the source is still on GC and should help aspiring app makers get an idea for a basic UI and some interesting features.
Beta is out. It's working and ready to install on Cupcake and Donut.
If you are using it to create Hero, make sure you're running it. If you want Donut.. make sure you're running that, etc. It uses the currently running ROM for apps so it must match the new one or you might have issues with it. Requires root access. No way around that.
---------------------------------------------------------------------------------------
Purpose:
Due to issues regarding distribution of closed sources for ports of Android, this will handle backing up your licensed proprietary sources, an update you want to try and will put the sources into a final image and eventually partition if desired. You then rename NEW_system.ext2 to system.ext2 on your SD card's root folder and reboot.
---------------------------------------------------------------------------------------
Instructions
There will be a single app released soon!
1.) Install the APK
2.) Create a folder "update" on the SD card
3.) Place the update.sh file in /sdcard/update/
4.) Place a system.sqsh in the same folder.
5.) Run the app on the phone, click "Begin!" and let it do its thing.
6.) Take the "NEW_system.ext2" file on the SD card, rename it to "system.ext2" and remove or rename any existing system files.
7.) Reboot and enjoy
---------------------------------------------------------------------------------------
Download it here:
Google Code Page
Installable APK v1.0 BETA
Currently requires update.sh
---------------------------------------------------------------------------------------
This is an open project to be developed with others to bring a simple, shared interface that is compatible for any device running Android but of course with our phones in mind.
---------------------------------------------------------------------------------------
I wish I knew anything about development then I'd help, this is a good idea though. I'll try and support it in some way.
TheKartus said:
I wish I knew anything about development then I'd help, this is a good idea though. I'll try and support it in some way.
Click to expand...
Click to collapse
if you can't develop, I'd love feedback, bugs, ideas. I will eventually spin this into an open Market and later a Maps app. There's been talk about replacing these apps but nothing actually done. I was up all night with the Internet in one hand and Eclipse in the other and got this far for never having made anything like this.
This is a fantastic. I will support it fully. I am currently using a 1.5 build but I don't call which one it is because I've gone through so many versions and different roots, images and edits to my default.txt. It's a MUTT, I guess.
I am a Kaiser/Tilt user and was going to leave ATT until I decided to look into Android builds you and others offer.
Thanks a ton.
im getting fc/waits with the beta... by the way how long should the process take to backup. thanks nate
Running Cupcake or Donut? Is that once it starts running? It does not like to have a command run this long so it might just be that. Hasn't happened once for me running my Dark Donut though.
The backup is about 5 minutes or so mostly for dd'ing an ext2 image and then copying the apps. Once I hard code the script in I can make it show the progress. Also, each step will be a separate command so it shouldn't FC/wait on you. You can watch the progress by running:
Code:
tail -f /sdcard/update/update.log
which is what the app will do when I can get the update.sh verified by others that it's working correctly
And it is working for you right?
enatefox said:
Running Cupcake or Donut? Is that once it starts running? It does not like to have a command run this long so it might just be that. Hasn't happened once for me running my Dark Donut though.
The backup is about 5 minutes or so mostly for dd'ing an ext2 image and then copying the apps. Once I hard code the script in I can make it show the progress. Also, each step will be a separate command so it shouldn't FC/wait on you. You can watch the progress by running:
Code:
tail -f /sdcard/update/update.log
which is what the app will do when I can get the update.sh verified by others that it's working correctly
And it is working for you right?
Click to expand...
Click to collapse
it worked, i kept hitting wait and it didnt tell me when it was finished(the ui just froze idk). it gets the job done thanks man!
update.log
Code:
Backing up apps...
Mounting sqsh image...
Creating new system image
Transfering update sqsh to ext2...
edit i was running jeterblur but i was using the ion09/09/09.sqsh
It should say it finished. The log looks like it didn't finish. I'll try testing the script in the app itself and that should alleviate the strain on the system. It taps like 30-40% of CPU while it's running so if you have a bunch of processes it could be interfering. At least you're saying it's working too
I must be doing something wrong.
1. I put the dark donut clean build in my /storage card/updae folder along with the update.sh;
2. Ran android with an old Ion build (brand new data.img file)
3. Installed and ran stay safe
I had to press wait 5 times, and after 5 minutes it finished.4. Before I reset the phone I moved the NEWsystem file into a new folder off the sdcard root
5. Then restarted the phone
6. In W.M. moved the ion data and system files to another folder
7. Renamed the NEWsystem (200mb) file to system
8. Put on root and ran harnet.
It booted, created a data file and is running great.
The issue is, no added apps. It is exactly the same as the clean version.
Any ideas?
If you're making a Donut image, you should be running Donut on the phone to keep the versions correct. I'm going to make an update probably tomorrow that will have better error handling. It does do a cleanup at the end. If you edit update.sh (which is all the app runs) to remove these lines it will keep the apps it backs up:
rm -r "$app_base"
rm -r "$app_mountbase"
rm -r "$app_updatefolder/cmd"
rm -r "$app_ext2mount"
rm -r "$app_sqshmount"
Click to expand...
Click to collapse
It finds the apps through a grep pattern. On the full ROM, run this in ADB/terminal and see if it matches the apps:
ls /system/app/ | egrep -i 'vending|office|maps|street|gmail|market|youtube|setupwizard
Click to expand...
Click to collapse
enatefox said:
If you're making a Donut image, you should be running Donut on the phone to keep the versions correct. I'm going to make an update probably tomorrow that will have better error handling. It does do a cleanup at the end. If you edit update.sh (which is all the app runs) to remove these lines it will keep the apps it backs up:
It finds the apps through a grep pattern. On the full ROM, run this in ADB/terminal and see if it matches the apps:
Click to expand...
Click to collapse
I just tried it with the tmo donut build and your clean dark donut build; same result. So I removed the lines from the update.sh file and now the phone freezes. I let it sit for 30 mins, the rebooted the phone. It did grab the obdx? and apk files, but when I tried to manually install them, (after allowing non market apps) I get a "Program Name couold not be installed on this phone"
slight edit; I re-edited the file, now i does not freeze, but it still does not load the apps and the pulled apps will not install
I'm abandoning this project at this point. I'd like to have this integrated into the rootfs.img as an option at install time. If someone wants to pick it up or wants to take this further, I'm open to that. The source should help people out who would like to make an app though.
I downloaded the netflix.apk that has been floating around, and with a few tweaks to my build.prop, I was able to get it to work on the galaxyXT ROM.
You have two choices, either download the attached build.prop file and stick in into your /system/ directory... or make the modifications yourself. FYI, please make a backup of the original build.prop before you mangle it.
I changed three lines in my build.prop. Just find these lines in your build.prop and change them to this:
ro.product.model=HTC Vision
ro.product.manufacturer=HTC
ro.build.fingerprint=tmobile/htc_vision/vision/vision:2.2.1/FRF91/277427:user/release-keys
Reboot, and that worked for me! If you have different experiences, please be sure to post them here.
FYI, If you make the changes yourself, make sure they are exact, case and everything. Use Notepad++.
Enjoy!
how/where do you access the /system/ directory? I looked on my SD card but cannot find.
thx
c_urbanek said:
how/where do you access the /system/ directory? I looked on my SD card but cannot find.
thx
Click to expand...
Click to collapse
Not on your sd card.
It is in the /system/ Use Root Explorer or something like it.
It's in the phones internal memory, not on your sdcard. You would either need a file explorer with root access (e.g. Root Explorer) or you need to push it with adb.
tried using root explorer & it says the system files are read only...
Nevermind, clicked the R/W button & it allowed...
I'll try Netflix now after a reboot.
At the top of window while in root explorer you'll see a MOUNT R/W button, you need to toggle on read / write access.
Wow! Works Beautifully!
Wow! Works Beautifully! Thank YOU!
Work on Dexter's 1.3 too!
Sorry for the ignorance but what is it?
Streaming movie/TV service. Not everybody has it, but its a big deal for Android phones to FINALLY get it since iphone and Windows 7 phones have had it for a while.
I'm not sure, but there are several apk XDA of netflix, and other folders, I can not understand yet. Apk is installed, replace the buildprop and that would be enough? You may be able to give us the link to the apk please because in my market does not appear.
For the payment of subscription must be from the website or can be within the application?
The truth was unaware of this application, it looks very interesting. Thanks for sharing.
can someone share here the apk..tq
This is where I downloaded it from
3rdstring said:
This is where I downloaded it from
Click to expand...
Click to collapse
Thanks for posting that. I couldn't remember where in the forums I had found it.
Hey I'm running stock 2.1 rooted on the xt720. I swapped out the build.prop you supplied in the .zip and installed numerous versions of the netflix clients to see if any would work. The apps installed fine but when I tried to open them (every single one) just opened to a black screen, then it force closed with a bunch of Japanese lettering. Any suggestions? Thanks.
donovanx3 said:
Hey I'm running stock 2.1 rooted on the xt720. I swapped out the build.prop you supplied in the .zip and installed numerous versions of the netflix clients to see if any would work. The apps installed fine but when I tried to open them (every single one) just opened to a black screen, then it force closed with a bunch of Japanese lettering. Any suggestions? Thanks.
Click to expand...
Click to collapse
Unfortunately
"Latest version: 1.2.0 build 819145-1.2.0-102 (for Android version 2.2 and higher)"
I got Netflix installed and everything seems to work. But when I hit play, it starts to load and says that I don't have a Netflix ready device. I have Dexter Froyo v1.3 on XT720. Anyone have this problem?
see 1st post in this thread....
ErnFuggit said:
I got Netflix installed and everything seems to work. But when I hit play, it starts to load and says that I don't have a Netflix ready device. I have Dexter Froyo v1.3 on XT720. Anyone have this problem?
Click to expand...
Click to collapse
once you install the apk, you need to do the hack rev explained in the 1st post.
New APK
Has anyone tried the new "stock" Netflix apk with the XT720?
I running the 1.20 APK, haven't seen an apk for the 1.21 yet, though I haven't gone looking yet either.
Are there any DSP managers that work with our Motoblur 2.2 ROM other than PowerAmp? PowerAmp is fine for playing stored music; I find myself listening to Pandora more often though. Even on the treble booster audio setting everything sounds muffled.
magicCrazyThing said:
Are there any DSP managers that work with our Motoblur 2.2 ROM other than PowerAmp? PowerAmp is fine for playing stored music; I find myself listening to Pandora more often though. Even on the treble booster audio setting everything sounds muffled.
Click to expand...
Click to collapse
Not positive, but you might be able to use AudioEffectSettings.apk from CM7. Its a Moto DSP app. I've never tried, but then again, I've ran a custom rom since the 4th hour of owning a Bravo. Push\paste it into /system/app and set the permissions to either 644 or whatever the other apps have in the gui of your filemanager.
Open a terminal\command prompt in the folder with the file and use this command
Linux Version
Code:
adb remount && adb push ./AudioEffectSettings.apk /system/app && adb shell chmod 0644 /system/app/AudioEffectSettings.apk && adb reboot
Windows Version
Code:
adb remount && adb push .\AudioEffectSettings.apk /system/app && adb shell chmod 0644 /system/app/AudioEffectSettings.apk && adb reboot
Note that the only difference is ./ to .\ between the two.
The only problem I can see is Android changed the DSP framework from 2.2(stock) to 2.3(CM7\MS2\MIUI). It won't cause bootloops or anything bad to happen, but it might not work.
If you're running stock you should switch to the BravoX rom -- its a stock deodexed rom for the Bravo and it runs much faster and smoother.
If you do try this let us know if it works.
I usually just use cm7, but due to some rather bothersome problems I've had lately I decide to just use BravoX for awhile. I just tend to be a bit of an audiofile.( That was the original reason for my switch to to CM7 actually.)
which is easier to use ADB under: Ubuntu or Windows? I run both on a dual boot. Also could you point me to a tutorial of adb? I always avoided it because of how complicated it seemed.
It depends on which system you're more comfortable using the command line on really; or use the most. I'd use the linux version myself, but linux is my only OS
Go here and you'll find all the instructions you'll need for either windows or linux install.
http://developer.android.com/sdk/index.html
Its a bit complicated but really worth it in the end to have adb installed -- once you get the hang of pushing files to your device you'll never mount your sdcard again. Adb is much safer anyways; less chances of file system corruption from multiple OS's mounting and unmounting the sdcard. It happened to me a lot when I dual booted 7 and Mint 12 -- every time windows would unmount it I'd have file corruption issues. Since I quit using windows I haven't had file corruption anymore.
If you need more help than what that site has, just search the forums here (there are tons of adb tutorials) then post here if you can't find what you're looking for.
//I'm an audiofile myself. The DSPManager not working on CM9\10 really grinds my gears -- its still required to be installed for 3rd party DSPManagers to function (PowerAmp, MortPlayer, etc). There's also a paid equalizer app on the market, but I've never used it at all. Not sure if it supports Froyo, but it does support Gingerbread and up.
If I don't post back anytime soon its because my PC is on the ass end of the next PA compile and it gets really slow on the java compile for the apk's.
I forgot that I already had it all setup in windows. Now I just have to look through some of the tutorials on here.
I actually already had it installed completely under Windows. I just need to learn the commands. I know it's adb push, but from their I'm learning.
opps, My computer didn't show my previous post. so now theirs two. sorry.
I just noticed that you already had the command there. it wont let adb remount run though it just keeps telling me "remount failed: operation not permitted." my phone has android debugging enabled. what would cause that?
okay, I have it all sorted out. It sent the AudioEffectSetting.apk over and so far no problems. It's allowing me to change the audio effects, and the stock music app is working. I don't think it sounds as muffled as it did. would this allow for me to use the CM7 Dsp manager app? would that be the best way to test?
magicCrazyThing said:
okay, I have it all sorted out. It sent the AudioEffectSetting.apk over and so far no problems. It's allowing me to change the audio effects, and the stock music app is working. I don't think it sounds as muffled as it did. would this allow for me to use the CM7 Dsp manager app? would that be the best way to test?
Click to expand...
Click to collapse
Glad that AudioEffects works. Good to know if you run the stock roms.
Just push DSP and try. Worst that'll happen is you'll have to remove it.
I think it relies on the library /system/lib/soundfx/libcyanogen-dsp.so, push it if DSPManager doesn't work.
The permissions are still 0644 for these files. Most libraries and apks are.
to remove
adb remount
adb shell
rm /system/app/DSPManager.apk && rm /system/lib/soundfx/libcyanogen-dsp.so
I've been having adb issues for a while now. Enabling tethering fixes it for me. What sucks is I can't use adb in the bootmenu or pull a logcat on boot.
Something here isn't happening right. Adb says the files are pushing fine. the DSP manager is not showing up anywhere though. as a test I ran the the push command by itself and then ran the second part separately. when It goes to run that second part to set the permission though it tells me that that directory does not exist. it's listing the files as the wrong sizes too. the DSP Manager is only 42Kb, and adb is pushing something that is 660Kb. It's doing that with all of them. the sizes are always listed wrong.
magicCrazyThing said:
Something here isn't happening right. Adb says the files are pushing fine. the DSP manager is not showing up anywhere though. as a test I ran the the push command by itself and then ran the second part separately. when It goes to run that second part to set the permission though it tells me that that directory does not exist. it's listing the files as the wrong sizes too. the DSP Manager is only 42Kb, and adb is pushing something that is 660Kb. It's doing that with all of them. the sizes are always listed wrong.
Click to expand...
Click to collapse
That's weird, the file sizes. How long ago did you set up adb? Its probably been updated since the last time you used it. On my system all I have to do it type "android" and it opens up the sdk to update it. I've never used the sdk under Windows so I'm not sure the proper command to update it (my adb on windows was in a root kit).
Just use a file manager to do it. I recommend Apoonet's MiFileExplorer (here on xda) or Yaffs Explorere by TPruvot (Epsylon3) on the market. I suggest Yaffs because it also shows you the linux chmod code when you change file permissions (useful feature if you're learning chmod).
Since its related I'll add that if you've ever added an app /system/app and it didn't work properly, it requires a lib to be added to /system/lib. You have to do it manually by opening up the apk and copying the lib over (use the arm7 lib if there are more than 1 of the same name). There is no lib in DSPManager but it relies on the one mentioned earlier.
Good Luck
I think what happened with the lib mentioned earlier is that there is no soundfx folder in system/lib/. I went looking for it last night with a file manager. there is one in there called DSP though. I would have justt pushed the audio lib there, but I didn't think the DSPmanager.apk would find it.
The DSPmanager from Cm6 will start up. it won't do anything though. do you know what libs it relies on?
I guess Froyo doesn't have that folder (just checked the SBF)
Here's the soundfx folder from a Defy GingerBread SBF -- non flashable zip.
Just make a soundfx folder in /system/lib and copy all the files to it; same permissions as always.
The dsp folder is codec related, not effects
Not sure what lib is required for CM6 (never used it)
I have everything in the folders now. CM7 DSPManager still won't show up. I went in and found it in Yaff's. When I try to install it through Yaff's it just tells my that there was a problem parsing the package. Also your link isn't showing; I have one of you CM7 Kang zips that I have been pulling files from though.
magicCrazyThing said:
I have everything in the folders now. CM7 DSPManager still won't show up. I went in and found it in Yaff's. When I try to install it through Yaff's it just tells my that there was a problem parsing the package. Also your link isn't showing; I have one of you CM7 Kang zips that I have been pulling files from though.
Click to expand...
Click to collapse
I guess I forgot to upload it. I was sleepy. Its up there now.
It won't install since its a system app. The only way to use it is to place it at /system/app with the correct permissions and reboot. If it doesn't show up it might just not work on Froyo.
Try this flashable zip. Make a nandroid before flashing it. I replaced a few audio libs, changed the DSPManager.apk sdk version to froyo. There's a chance this zip will either work or cause bootloops or do nothing at all. I can't test it since I'm on PA and I don't feel like SBFing back to Froyo, then flashing BravoX.
EDIT
Forgot to add -- if the zip flashes just fine, boots fine, and DSPManager opens but does nothing, add in libaudio.so from CM7 in the zip here to /system/lib and reflash it.
I got stuck on the Red M both times I tried. The first time I was on the BravoX recovery; the second time (after SBFing) I tried under 2nd-init. i'm beginning to wonder if this is possible. I guess I'll start burring my head in lots of forums and try again tomorrow.
You're awesome for all the support you've been giving me though. I get the feeling we're really close to getting this working.
magicCrazyThing said:
I got stuck on the Red M both times I tried. The first time I was on the BravoX recovery; the second time (after SBFing) I tried under 2nd-init. i'm beginning to wonder if this is possible. I guess I'll start burring my head in lots of forums and try again tomorrow.
You're awesome for all the support you've been giving me though. I get the feeling we're really close to getting this working.
Click to expand...
Click to collapse
try removing libeffects.so.
The fourms I found added in libaudiofilinger.so and libaudio.so if needed -- I forgot that our libaudio.so on CM7 is from stock froyo so its not necessary here.
I know that the 3rd Party DSP's on the Market use their own special libraries on Froyo\2.2 roms to give them GB style DSP's. Google upgraded the DSP framework from 2.2 to 2.3.
If you looking for Pure Music functionality and awesomeness then I highly recommend changing to CM7. GB roms have the best mods for audio effects, long press the volume for track changing. The fx folder is necessary (at least in some Miui Ports its was).
That said, I'll jump back to BravoX and see if I can't get it working on my phone. I like a challenge and doing something that benefits a native Bravo rom. Unlike everyone else here, I have a rooted SBF (made it myself) so its not very hard for me to do -- flash sbf, run market enabler, install 2nd-init, flash away . If I had remembered to backup my /data partition into the sbf I wouldn't even have to do that...just sbf and install 2nd-init.
Since you're on BravoX, have you ever tried the BlurLauncher3D Walter79 uses with MS2 Ginger? I'm about to use it with BravoX so I'll find out if it works or not.
---------- Post added at 09:56 AM ---------- Previous post was at 09:05 AM ----------
Back on BravoX. I need to tweak its init scripts to load the multitouch module and overclock module. Also, no tethering sucks.
---------- Post added at 10:40 AM ---------- Previous post was at 09:56 AM ----------
Managed to disable the tethering entitlement check.....only I'm forced to tether with 3g and not my home wifi like I do on CM7 -- that needs to be fixed, but at least I can post on the forums with my Keyboard again. I'm gonna keep messing around and see if I can't get it to use my home wifi instead of 3g.
Btw, to use thethering -- open build.prop and change ro.mot.entitlement_check=true to =false -- that's it. And I was changing smali code until I saw that prop string embedded in it.
Had to jump back to PA -- tethering was eating up my 3g bandwidth.
I started using the Droid 1 CM6 libs -- they don't cause bootloops or issues, but they don't make DSPManager work either. So far I've tried libaudio.so and libaudioflinger.so.
Wow, that was a lot of explanation.lol I haven't had time to try anything. you also tried the only thing I found anything on.
I haven't used tethering so far I never had a reason too. why do you have to use it?
Also, did you ever get blur launcher 3d to work on BravoX. I tried getting it to work with CM7 before, but all I ended up with the many times I tried was everything being deleted from my homescreens and the ROM would become extremely buggy.
magicCrazyThing said:
Wow, that was a lot of explanation.lol I haven't had time to try anything. you also tried the only thing I found anything on.
I haven't used tethering so far I never had a reason too. why do you have to use it?
Click to expand...
Click to collapse
My PC is farther from the router than my longest ethernet wire so I connect to WIFI on the Bravo and tether it. I can only do it on CM7\9\10\Miui. Moto roms have an entitlement check in them. I found the build.prop string to disable the check, but I'm still working on changing the default dhcp settings for tethering -- they're set to 192.168.43.XXX and I need it set to 192.168.0.XXX. I changed the dhcp range values in the smali code of services.jar but it didn't matter. I think there might be another smali file with dhcp ranges somewhere else. I don't want to change my routers dhcp range since all my WiFi devices are set to connect to a static IP (had to for the iPhones in the house -- the iPhone dhcp bug).
I updated my phone to4.4.1 today and ever since I haven't been able to open my music player 'Mixzing'. When I click on the App icon it goes to a black screen momentarily then back to the home screen without starting the app (this is the only app that it happens on)
I have wiped dalvik ect and deleted any folders that have 'mixzing' on and tried re-installing but nothing has helped.
Any ideas?
anyone?
Same here
I couldn't post my question on the corresponding Dev Thread for CM11 on i9300, but found this post for Nexus 5. Unfortunately without an answer.
I have the same problem (MixZing app doesn't open) on i9300 with CM11 nightly (Android 4.4.2). On CM10.2 (Android 4.3.1) it worked fine.
Have you found an answer somewhere else?
storchp said:
I couldn't post my question on the corresponding Dev Thread for CM11 on i9300, but found this post for Nexus 5. Unfortunately without an answer.
I have the same problem (MixZing app doesn't open) on i9300 with CM11 nightly (Android 4.4.2). On CM10.2 (Android 4.3.1) it worked fine.
Have you found an answer somewhere else?
Click to expand...
Click to collapse
Same here, no solution yet.
I made a modded version of the mixzing app to get it to launch for me:
All I did was replace the following in com.mixzing.android.SdCardHandler.getCardId()
Code:
invoke-static {v10}, Landroid/os/FileUtils;->getFatVolumeId(Ljava/lang/String;)I
move-result v4
with
Code:
const/16 v4, 0xBEEF
You should use your own random number instead of BEEF since this effectively means that you are always returning the same value for getFatVolumeId as far as the app is concerned.
Can you explain this to the developer of MixZing? So they can update the original App.
Would be nice, thanks.
storchp said:
Can you explain this to the developer of MixZing? So they can update the original App.
Would be nice, thanks.
Click to expand...
Click to collapse
They have said that they know about it. They were just taking too long for my taste, so I did it myself instead.
If you can't wait I can post my modded version if you want, but I highly recommend doing the mod yourself rather than simply trusting that my posted version does not contain any malware. It's just a good habit to get into IMO.
Never modded an App. But I'm eager to learn. Any resource (document, blogpost, etc.) I should look into?
storchp said:
Never modded an App. But I'm eager to learn. Any resource (document, blogpost, etc.) I should look into?
Click to expand...
Click to collapse
You can technically use a combination of 7zip (or another zip utility), smali, baksmali, and signapk to do this mod, however this is not the most user friendly way to do it. I would suggest using one of the following:
Here is one way, apktool (Linux, Mac OS, Windows): http://forum.xda-developers.com/showthread.php?t=2195680
The other is Virtuous Ten Studio (Windows Only): http://forum.xda-developers.com/showthread.php?t=1619473
*EDIT*
It is important to note that since this is not a system apk -- I.E. one that comes with the phone -- you will have to re-sign the apk after adding, removing, or changing any of the files inside. If it were a system apk, you could place the classes.dex file directly into the apk (which is secretly a zip file) without re-signing. (VTS does this for you automatically).
Thanks, I'll check it out.
Ok, decompiled it and found the lines you mentioned in a file called SdCardHandler.smali.
Before I change it I want to understand a little bit what I'm doing.
The method getFatVolumeId() returns the Id of a given Mount Point. It's a native method call which I guess causes the trouble here.
If I change it to a static value, does it do any harm? I mean I have an internal and external SD card. Does MixZing check both?
You should use your own random number instead of BEEF
Click to expand...
Click to collapse
Just some hex value I can think of? e.g. AEEF, CEEF, ABCD, ...
Couldn't wait, wanted to try anyway
Did the changes, compiled a new apk, signed it, but it doesn't install :crying:
When installing via the phone itself it just tells me that the App hasn't been installed.
When installing via ADB it get an INSTALL_FAILED_SHARED_USER_INCOMPATIBLE error. Need to figure out, how to fix this.
storchp said:
Couldn't wait, wanted to try anyway
Did the changes, compiled a new apk, signed it, but it doesn't install :crying:
When installing via the phone itself it just tells me that the App hasn't been installed.
When installing via ADB it get an INSTALL_FAILED_SHARED_USER_INCOMPATIBLE error. Need to figure out, how to fix this.
Click to expand...
Click to collapse
The problem is that on our devices, that native method does not exist, so we just arbitrarily use a value such that it always returns the same value (I.E. always the same card) As for the error, uninstall any applications signed by the same certificate as Mixzing was or sign your modded copy with debug keys, and it should install just fine.
*edit*
Other fun values:
DEAD, F00D, B00B, BABE, C0DE.
Thanks. A little research brought me to the packages.xml file. In there I found the shared user attribute for the MixZing Upgrader App. I was not sure if I want to edit the file. But after your tip I just uninstalled the Upgrader App and I could install the modded version.
Thanks a lot
Meanwhile they have fixed the App in the store.