Guest isambard Posted February 28, 2011 Report Posted February 28, 2011 (edited) OK. Version 1.0 of Blade Buddy PRO released. Features include: - Un-lock your Blade - Re-lock your Blade and reset # unlock attempts - Re-designed modular UI (this will allow me to more easily add features) - Ability to remount /system as read-write or read-only, effectively turning any explorer into a Root Explorer - Gen1/Gen2 device detection and /proc/iomem output - Integration with basic settings Spare Parts Plus! (see below) Get it now from the Android Market: As a sneak peak and to show what future ideas I have on the roadmap, see screenshots below: I also wrote a free app: Spare Parts Plus! Which has also been released today. This is a basically like Spare Parts we know and love without the Ad Mob adverts and with integration to Blade Buddy. Get it now for free from the Android Market: Edited April 27, 2011 by isambard
Guest markusj Posted February 28, 2011 Report Posted February 28, 2011 (edited) Nice work, buddy! These changes need a reboot, don't they? A notification would be great. also, a market link (for one-click installation): https://market.android.com/details?id=com.d...gram.bladebuddy Edited February 28, 2011 by markusj
Guest isambard Posted February 28, 2011 Report Posted February 28, 2011 Nice work, buddy! These changes need a reboot, don't they? A notification would be great. also, a market link: https://market.android.com/details?id=com.d...gram.bladebuddy Thanks. If you like the app, please do support me by rating it :huh:
Guest markusj Posted February 28, 2011 Report Posted February 28, 2011 Thanks. If you like the app, please do support me by rating it :huh: It was the first thing I've done :)
Guest Sebastian404 Posted February 28, 2011 Report Posted February 28, 2011 - How to detect device is Blade or Blade compatible (anyone have a list of Blade compatible devices?) check for the existence of /init.blade.rc look for either 'ro.product.device=blade' or 'ro.product.board=blade' in /system/build.prop
Guest Simon O Posted February 28, 2011 Report Posted February 28, 2011 What Sebastian404 said. Most (all?) of the roms have those two set two blade in build.prop and the init.blade.rc should be in all boot images.
Guest Ralph Martin Posted February 28, 2011 Report Posted February 28, 2011 How about a list here of the things you can edit, please?
Guest wbaw Posted February 28, 2011 Report Posted February 28, 2011 (edited) check for the existence of /init.blade.rc look for either 'ro.product.device=blade' or 'ro.product.board=blade' in /system/build.prop This app isn't really Blade specific at all, at the moment, it should work on all Android phones. It's just less useful to people that aren't running one of the 2.2 roms on the blade, I'm not sure other phones/roms have such issues with stagefright. Isambard, read the settings using getprop. That will solve the problem over whether settings are valid for that phone or not. It'll also be an easier & more reliable way of getting the current settings than parsing all the .prop files & will stop the error if any dont exist. Edited February 28, 2011 by wbaw
Guest wbaw Posted February 28, 2011 Report Posted February 28, 2011 (edited) How about a list here of the things you can edit, please? Here's a screenshot. It's just enable/disable stragefright, hardware acceleration & the boot animation. Edited February 28, 2011 by wbaw
Guest isambard Posted February 28, 2011 Report Posted February 28, 2011 (edited) Here's a screenshot. It's just enable/disable stragefright, hardware acceleration & the boot animation. I think you have an old version. I already added several new settings this morning. Re: getprop, as per my email, getting settings via getprop is to be implemented soon! Edited February 28, 2011 by isambard
Guest Pelemane Posted February 28, 2011 Report Posted February 28, 2011 I installed this on my CM7 nightly 8 (and I gave you 5 stars before I even tested this :)). It shows that my stagefright options are on false by default but I thought that stagefright was fixed in CM7 cause it's 2.3. So what happens if I mess with these settings? :huh: Btw I have exactly the same version that wbaw:s picture shows. So there is newer version somewhere? (This is newest in market)
Guest wbaw Posted February 28, 2011 Report Posted February 28, 2011 (edited) I think you have an old version. I already added several new settings this morning. Re: getprop, as per my email, getting settings via setprop is to be implemented soon! You can't set the settings using the java setprop, it only changes it for the app that does it. You'd have to use the terminal command. Even then, I think all these settings might require a reboot. I did have the old version, updating now ... Edited February 28, 2011 by wbaw
Guest isambard Posted February 28, 2011 Report Posted February 28, 2011 You can't set the settings using the java setprop, it only changes it for the app that does it. You'd have to use the terminal command. Even then, I think all these settings might require a reboot. I did have the old version, updating now ... i meant getting via getprop. setting will be done via prop files. i tested a few settings e.g. resolution via setprop, but unsurprisingly this didn't work without a reboot. i guess technically, there must be some way of doing e.g. by re-initialising the screen etc. but sounds like too much trouble.
Guest Frankish Posted February 28, 2011 Report Posted February 28, 2011 Any chance of an option to enable and disable menu unlock button? I want an easier way than editing framework each time :huh:
Guest wbaw Posted February 28, 2011 Report Posted February 28, 2011 (edited) i meant getting via getprop. setting will be done via prop files. i tested a few settings e.g. resolution via setprop, but unsurprisingly this didn't work without a reboot. i guess technically, there must be some way of doing e.g. by re-initialising the screen etc. but sounds like too much trouble. getProperties() should return NULL if the setting doesn't exist. On my CM7, after deleting the /data/local.prop & rebooting, it's saying all the stagefright options are off. Are they really? They should default to on I think. Those options might not be set at all in CM7 / 2.3, they don't seem to make any difference if it's true/false or doesn't exist. So for the stagefright options, I think you could check if those settings exist at all by checking if getProperties() returns NULL & don't show them if they don't exist. It will save you from having to detect the phone version & android version & should work more reliably. Edited February 28, 2011 by wbaw
Guest wbaw Posted February 28, 2011 Report Posted February 28, 2011 Any chance of an option to enable and disable menu unlock button? I want an easier way than editing framework each time :huh: Doesn't 0x90 do that?
Guest isambard Posted February 28, 2011 Report Posted February 28, 2011 Btw I have exactly the same version that wbaw:s picture shows. So there is newer version somewhere? (This is newest in market) newest version is 4.0b. It shows that my stagefright options are on false by default but I thought that stagefright was fixed in CM7 cause it's 2.3. known issue: http://droidgram.com/forum/6-Blade-Buddy fix will be to hide irrelevant settings e.g. stagefright by detecting android version and then removing irrelevant settings.
Guest wbaw Posted February 28, 2011 Report Posted February 28, 2011 newest version is 4.0b. known issue: http://droidgram.com/forum/6-Blade-Buddy fix will be to hide irrelevant settings e.g. stagefright by detecting android version and then removing irrelevant settings. I don't think you need to detect anything, just if getProperties returns NULL or not.
Guest Frankish Posted February 28, 2011 Report Posted February 28, 2011 Doesn't 0x90 do that? It'd discontinued.
Guest wbaw Posted February 28, 2011 Report Posted February 28, 2011 (edited) It'd discontinued. Maybe we could badger 0x90 for source code, if he hasn't released any & continue it. I guess it'd have to be different for every version of every rom though, which would be the reason he discontinued it, having to replace large system files isn't ideal. If you could explain how it could be done without changing it every time somebody updates a rom, then we might have a better chance of getting it. Edited February 28, 2011 by wbaw
Guest isambard Posted February 28, 2011 Report Posted February 28, 2011 just if getProperties returns NULL or not. yes, this is detecting :huh:
Guest wbaw Posted March 1, 2011 Report Posted March 1, 2011 yes, this is detecting :huh: That might not work for the nobootanimation one though, but that should work on every phone I think.
Guest AsusFreak Posted March 1, 2011 Report Posted March 1, 2011 Very nice tool. As a recommendation: the used functions are not self explaining to all users. It could be helpful to explain the features in this thread or on the linked market page. Otherwise your app will stay as a tool for freaks - but maybe this is what you want it to be ? :huh: Thanks for your work.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now