Advanced Feed Development Request For Rooted Users topic
Alright everyone, I'm Trailblazer101, an Android Developer who likes to take advantage of, and make better, the unique features of the phones I purchase. I started off with the Samsung Continuum back in 2010, which had a ticker ahead of its time, and went from there. I work 2 jobs, so time is tight sometimes, but I still manage to work on these things, a fun passion/hobby.
But I need you! Or, well, those of you who are rooted and adept at replacing /System/Priv-App apps, capturing/reading Log Cats, the works. Also you have to be willing to take risks/know how to come back from a boot-loop (reflashing, etc).
If you feel like you're up to the job, you lucky rooted Sprint/T-Mobile users you, then please feel free to continue, with the steps following!
Request(s)!
Alright, so first thing's first, you have to remove /system/priv-app/CocktailBarService and replace it with mine. You can do it however you'd like, as long as you do without soft-bricking :3 The signature is different, for obvious reasons, so there might be some hiccups with that. Like I said, I'd do all this exploration myself, if I had my own Sprint/T-Mobile version, but alas. (Side note: if you're interested in furthering development and have an extra S6 Edge (for whatever reason that might be!?)/money to spare. Broken screen would be fine, as long as the touch still mostly works, it'd find a safe spot here, which would allow for me to do these things!) Anyways, my version of the CocktailBarService is at the bottom of the thread.
Next, we can install normally, just download and click, my Custom Cocktailbar Feed. You would need to enable it in Settings->Edge Screen -> Information Stream -> Manage Feeds, Reorder (this kickstarts the Feed in gear, sometimes, when there's a problem otherwise) and restart for good measure. Right now a simple 'We Did It!" text will display, but that is only temporary to make sure the Feed is actually getting loaded. Once we know it is, I will enable the Quick Launch functionality, which is written, just not tested/enabled, and we can debug that next.
Anywhere along these steps we can expect errors galore, so please be keen on looking in DDMS (or whatever the cool kids use these days for LogCat-ing ). If you see the person above you is having problems, I'd suggest you don't go through with it too. I'd rather not get flooded with "ahh it doesn't work, boot-loops, etc", and just work on it error at a time, until we get something more substantial. But I don't want to lock this down to just Private Messaging, not posting a thread, because I feel like I should share my information/knowledge with other people, who can then take it and run with me!
So, quick review of what we gotta do:
1. Remove old CocktailBarService from /system/priv-app
2. Copy my own apk to its place, with right permissions, etc.
3. Install my Custom Cocktail Feed App, to see if it worked!
Developer/Advanced Information!
We can make our own Feeds no problem, without root, they are just forced to use a RemoteView directly, which for all intents and purposes, is a pain in the kiester. Instead, it would be a lot nicer/convenient, without even mentioning the more advanced functionality we could bring, to use our own Views. However the version of SlookCocktailManager.UpdateCocktail that allows this is only found within a more advanced API, one I don't have access to directly. BUT, I can still access it by decompiling for example the Edge RSS app from the Samsung AppStore, and putting/replacing the "sdk" folder from that into my own decompiled app, and recompiling. Easy enough, with apktool! (Of course with the headache of adding in my own temporary shell classes, in the project, so that I can actually write the calls, and just change the reference within the smali code once that sdk is replaced) The problem is, even when you do this, and it builds fine, installs great, and even begins initializing properly, we get an error from within CocktailBarService, the file I'm having you replace. More specifically, I tracked down the actual problem, and it comes back to "CocktailWhiteList", a class within CocktailBarServices, then checks the signature of the calling application, our Custom Feed, and sees if it comes from Samsung. This none of my expertise can fix, without being rooted, but trust me I tried.
But I need you! Or, well, those of you who are rooted and adept at replacing /System/Priv-App apps, capturing/reading Log Cats, the works. Also you have to be willing to take risks/know how to come back from a boot-loop (reflashing, etc).
If you feel like you're up to the job, you lucky rooted Sprint/T-Mobile users you, then please feel free to continue, with the steps following!
Request(s)!
Alright, so first thing's first, you have to remove /system/priv-app/CocktailBarService and replace it with mine. You can do it however you'd like, as long as you do without soft-bricking :3 The signature is different, for obvious reasons, so there might be some hiccups with that. Like I said, I'd do all this exploration myself, if I had my own Sprint/T-Mobile version, but alas. (Side note: if you're interested in furthering development and have an extra S6 Edge (for whatever reason that might be!?)/money to spare. Broken screen would be fine, as long as the touch still mostly works, it'd find a safe spot here, which would allow for me to do these things!) Anyways, my version of the CocktailBarService is at the bottom of the thread.
Next, we can install normally, just download and click, my Custom Cocktailbar Feed. You would need to enable it in Settings->Edge Screen -> Information Stream -> Manage Feeds, Reorder (this kickstarts the Feed in gear, sometimes, when there's a problem otherwise) and restart for good measure. Right now a simple 'We Did It!" text will display, but that is only temporary to make sure the Feed is actually getting loaded. Once we know it is, I will enable the Quick Launch functionality, which is written, just not tested/enabled, and we can debug that next.
Anywhere along these steps we can expect errors galore, so please be keen on looking in DDMS (or whatever the cool kids use these days for LogCat-ing ). If you see the person above you is having problems, I'd suggest you don't go through with it too. I'd rather not get flooded with "ahh it doesn't work, boot-loops, etc", and just work on it error at a time, until we get something more substantial. But I don't want to lock this down to just Private Messaging, not posting a thread, because I feel like I should share my information/knowledge with other people, who can then take it and run with me!
So, quick review of what we gotta do:
1. Remove old CocktailBarService from /system/priv-app
2. Copy my own apk to its place, with right permissions, etc.
3. Install my Custom Cocktail Feed App, to see if it worked!
Developer/Advanced Information!
We can make our own Feeds no problem, without root, they are just forced to use a RemoteView directly, which for all intents and purposes, is a pain in the kiester. Instead, it would be a lot nicer/convenient, without even mentioning the more advanced functionality we could bring, to use our own Views. However the version of SlookCocktailManager.UpdateCocktail that allows this is only found within a more advanced API, one I don't have access to directly. BUT, I can still access it by decompiling for example the Edge RSS app from the Samsung AppStore, and putting/replacing the "sdk" folder from that into my own decompiled app, and recompiling. Easy enough, with apktool! (Of course with the headache of adding in my own temporary shell classes, in the project, so that I can actually write the calls, and just change the reference within the smali code once that sdk is replaced) The problem is, even when you do this, and it builds fine, installs great, and even begins initializing properly, we get an error from within CocktailBarService, the file I'm having you replace. More specifically, I tracked down the actual problem, and it comes back to "CocktailWhiteList", a class within CocktailBarServices, then checks the signature of the calling application, our Custom Feed, and sees if it comes from Samsung. This none of my expertise can fix, without being rooted, but trust me I tried.
xda-developers
0 commentaires:
Enregistrer un commentaire