Develop Bugs

rooting 'Infotmic sawee10'

i am having trouble finding a thread on how to root and rom flash the "infotmic sawee10" if someone could help me out with a link or smething it would be much appreciated!!!!

gearhead3585 said:
i am having trouble finding a thread on how to root and rom flash the "infotmic sawee10" if someone could help me out with a link or smething it would be much appreciated!!!!
Click to expand...
Click to collapse
flytouch 2 or 3? w/ android 2.2 right?

Solidus_n313 said:
flytouch 2 or 3? w/ android 2.2 right?
Click to expand...
Click to collapse
shizznit! its for a friend.... its on 2.2 i kno that....
what other specs are needed?
she said its an "infotmic sawee10"..... from websurfing i found out its a clone of flytouch but that about it..... ppl @slatedroid are no help, all they do is delete my post...

i dont own one personally, but ive used a friends once or twice, and he asked me the same thing its relly difficult to pinpoint the model, but these are usually the differneces:
1. what color is the power light / Charge
2. does it vibrate on start up
3. any model info
4. WMT version, Can be found in setting about(if its a WonderMedia Technologies)
5. Download and use Android system info look at the memory (There are some vendors that fake the mem.)
6. look at the build.prop for any vendor info
EDIT** these instructions should help you root:
http://thebelv.altervista.org/Flytouch3/rooting/rooting_flytouch3.html

cool brah! thnx! ill get the spec asap! really appreciate the help!! ppl @ slatedroid were making me RAGE!! lolz

also, do you know the specs for screen resolution (1024x600 or 1024x576) and charger (9v or 5v)?

ok regardless of HW info, im 99% certain you have a KIRF, so your options are limited (read* non-existant ) for ROMS...
root wont be a problem, there are several methods. but the big issue is flashing roms over USB+mem stick(only gaurenteed method) has been known to cause more bricks than quality results with the SAWEE10/MERCURY...
i recommend ROOT + Titanium Backup (clear bloat) + System Panel/task killer (eliminate unnecessary processes) + New Launcher (your choice [or hers, whichever], its ALWAYS user preference ;P) to optimize the tablet.
ill PM you a bunch of links to help with these efforts and shed some light on this mess of a shadow tablet

Hey Gearhead I don't know what was happening with your post on my thread at SlateDroid. My last post to you however asked for specs on your tablet to make certain the firmware I have available in my roms section would work for her tablet. As Solidus mentioned, you really do run the risk of bricking because of the type of tablet you have. However, if you still intend to take the risk and flash, the usb flashing method is preferred over the IUW burning method as IUW is virtually almost irreversible unless you truly know what you're doing. On post 2 of my slate thread I go into great detail on root and bloat removal for improving your current system's performance. All the info you need is provided there in addition to what Solidus may have already provided to you. I know you have a bad taste in your mouth for that community now because you thought someone was deleting your post. However, I came up with that thread because I too could not find any info on my shadow of a tablet. If you look all over the internet you practically can't find device specific info for it.
Whether it's here on XDA, androidpassions, or SlateDroid, feel free to pm me and I will help you with what I can. Don't forget though that the people on that thread including myself have her tablet so all the problems she will face ahead will most likely been faced and overcome by them.
Thanks for providing a link to this XDA thread. Doing so may have further allowed me to assist you since you may not return to Slate.

IAmTheOneTheyCallNeo said:
Hey Gearhead I don't know what was happening with your post on my thread at SlateDroid. My last post to you however asked for specs on your tablet to make certain the firmware I have available in my roms section would work for her tablet. As Solidus mentioned, you really do run the risk of bricking because of the type of tablet you have. However, if you still intend to take the risk and flash, the usb flashing method is preferred over the IUW burning method as IUW is virtually almost irreversible unless you truly know what you're doing. On post 2 of my slate thread I go into great detail on root and bloat removal for improving your current system's performance. All the info you need is provided there in addition to what Solidus may have already provided to you. I know you have a bad taste in your mouth for that community now because you thought someone was deleting your post. However, I came up with that thread because I too could not find any info on my shadow of a tablet. If you look all over the internet you practically can't find device specific info for it.
Whether it's here on XDA, androidpassions, or SlateDroid, feel free to pm me and I will help you with what I can. Don't forget though that the people on that thread including myself have her tablet so all the problems she will face ahead will most likely been faced and overcome by them.
Thanks for providing a link to this XDA thread. Doing so may have further allowed me to assist you since you may not return to Slate.
Click to expand...
Click to collapse
wow, i miss people like you here on XDA

Solidus_n313 said:
wow, i miss people like you here on XDA
Click to expand...
Click to collapse
Thanks Yeah this place has become a demanding :handouts now: type of place lately with people who will chastise you should you accidentally ask a question that was previously answered in some hidden grave deep within the thread lol. However there are still a lot of good people here. I support the Droid Incredible on xda along with all my mods and tweaks that are across platform, and then my tablet on slatedroid. I don't know what was happening to this new user's posts but it really set him off. I'm glad you were able to provide him some info. If you feel like exploring a new community bent on being "chastise free", look up AndroidPassions.com. ****Mods and Admins my post is in no way intended to pull members away from this site but rather offer another avenue for additional support of their device: ) ****
Sent from my ADR6300 using Tapatalk

hahaha nice cover
ive been with xda for a LONG time, and delt with A LOT of trolls and useless blockheads who would rather you fix the problem than learn to fix it themselves with the help of others, hence the current state of XDA...people with more money than brains who think they deserve your hands on help becuase they figured out how to register to the forum
so i dont think ill ever actually leave permanantly, but ill say this, this isnt my first account :/

IAmTheOneTheyCallNeo said:
Hey Gearhead I don't know what was happening with your post on my thread at SlateDroid. My last post to you however asked for specs on your tablet to make certain the firmware I have available in my roms section would work for her tablet. As Solidus mentioned, you really do run the risk of bricking because of the type of tablet you have. However, if you still intend to take the risk and flash, the usb flashing method is preferred over the IUW burning method as IUW is virtually almost irreversible unless you truly know what you're doing. On post 2 of my slate thread I go into great detail on root and bloat removal for improving your current system's performance. All the info you need is provided there in addition to what Solidus may have already provided to you. I know you have a bad taste in your mouth for that community now because you thought someone was deleting your post. However, I came up with that thread because I too could not find any info on my shadow of a tablet. If you look all over the internet you practically can't find device specific info for it.
Whether it's here on XDA, androidpassions, or SlateDroid, feel free to pm me and I will help you with what I can. Don't forget though that the people on that thread including myself have her tablet so all the problems she will face ahead will most likely been faced and overcome by them.
Thanks for providing a link to this XDA thread. Doing so may have further allowed me to assist you since you may not return to Slate.
Click to expand...
Click to collapse
thanks neo!!! idk what happened over there... all i kno is that my post werent showing.... n i was getting heated.lol.
ill be keeping THIS thread up-to-date with all steps n issues if any!! appreciate the help!

Solidus_n313 said:
i dont own one personally, but ive used a friends once or twice, and he asked me the same thing its relly difficult to pinpoint the model, but these are usually the differneces:
1. what color is the power light / Charge
2. does it vibrate on start up
3. any model info
4. WMT version, Can be found in setting about(if its a WonderMedia Technologies)
5. Download and use Android system info look at the memory (There are some vendors that fake the mem.)
6. look at the build.prop for any vendor info
EDIT** these instructions should help you root:
http://thebelv.altervista.org/Flytouch3/rooting/rooting_flytouch3.html
Click to expand...
Click to collapse
look at build.prop for vendor? where do i find this? about tablet?

spec info:
infotmic sawee10
power / charge light - red
vibrates on start-up - yes
loading screen number - 0.6.1.2(672)
settings->about device:
model number- sawee10
android version - 2.2 v2.1:#3925
baseband version - unknown
kernel version - 2.6.32.9 [email protected] #82
build number - frf858
got the link to "rooting flytouch3" thanks!!
android system info installed from market.
let me kno what else is needed!! thanks!

gearhead3585 said:
spec info:
infotmic sawee10
power / charge light - red
vibrates on start-up - yes
loading screen number - 0.6.1.2(672)
settings->about device:
model number- sawee10
android version - 2.2 v2.1:#3925
baseband version - unknown
kernel version - 2.6.32.9 [email protected] #82
build number - frf858
got the link to "rooting flytouch3" thanks!!
android system info installed from market.
let me kno what else is needed!! thanks!
Click to expand...
Click to collapse
Yours vibtates? Hrrmmmmm.... that's interesting.. Hey my rooting method on slate is probably the simplest. I also included z4root as a direct download. Should be in post #2. Rooting with z4method can't screw it up
Sent from my ADR6300 using Tapatalk

Ok sounds great! And what about the rom flash to 2.3?? That's all good too then also??
Sent from my HTC Glacier using XDA App

gearhead3585 said:
Ok sounds great! And what about the rom flash to 2.3?? That's all good too then also??
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
It's not a real 2.3.. it's a 2.2 mutant lol it lies. I discourage your flashing of the roms mainly because yours came sawee and not tab10. Although the rom most likely will work, you run the risk or losing wifi.. even mine having been tab 10 even providing the correct drivers/firmware was unable to get the internal wifi functional again. So I purchased a $13 nano USB dongle and it works fantastic. Should you decide to take the risk, I would try the official ibex build on my page or the sawee build.
Sent from my ADR6300 using Tapatalk

ok cool. ill just do a theme upgrade with adw or something then, really appreciate the help guyz!!

Issues with FIFA and other large file games?

So I am trying to download FIFA 12 (my favorite game on Android), and the additional files download keeps stopping at 50% (in this case, 1595MB). Is there any way to push these additional files on there? Is anyone else having this problem? Will be such a bummer if I can't play my favorite game on here. Thanks in advance!

I thank you for pointing this one out: I can see that I am not the only one having this problem.
My issue is identical to yours: installation stuck at 50%, error message "please quit the app and try again", start back from 580MB and sticking back to 595.
I suggest you to contact directly EA (which still has to answer me). The more we are, the sooner they are likely to intervene.

here too....

EA hasn't replied to me yet either y'all. I tried pushing files from the backup I made on my GNex (I know it shouldn't work, but I had to try something!) and yeah, it didn't work. I hope they fix this :/

I'm still awaiting a reply from them.

Just saw a video of this game working on a Nexus 4 http://www.youtube.com/watch?v=i__o8E6fCoA

I'll give it another try asap, then. Thanks for the heads up

I have the same issue stuck at 595 MB.

ksumanth said:
I have the same issue stuck at 595 MB.
Click to expand...
Click to collapse
Yes, the version has not changed, if anyone can install this game, please report. All the others, send messages to EA please!

I've heard of similar issues on the Galaxy Nexus and have had this ZIP saved which was intended to fix it.
It might instead eat your device whole (though I doubt it), but try if you want.

Unfortunately, I'm not rooted (nor I plan to), but this might help somebody else

Ranguvar said:
I've heard of similar issues on the Galaxy Nexus and have had this ZIP saved which was intended to fix it.
It might instead eat your device whole (though I doubt it), but try if you want.
Click to expand...
Click to collapse
Sorry if this is a stupid question, but for the sake of you saying it might eat my device whole, do I flash this ZIP via CWM and then try and download the game again?
If so, I will make a nandroid backup and give this a shot. Thanks!

nakunz said:
Sorry if this is a stupid question, but for the sake of you saying it might eat my device whole, do I flash this ZIP via CWM and then try and download the game again?
If so, I will make a nandroid backup and give this a shot. Thanks!
Click to expand...
Click to collapse
I have no idea, I'm just taking a shot in the dark.
It's just a binary program in /system/bin, but I didn't want to make anyone think I knew what I was doing.

I have just received a first answer from EA, in which they basically ask for the same information I have given in the first message. I wonder if they take the time to read what we write them...
I'll report back for further developments, everyone else with the same problem, please contact EA as well!

Looks like they took it off our market as not compatible. Hopefully this is temporary so they can fix it. I paid for this app!

nakunz said:
Looks like they took it off our market as not compatible. Hopefully this is temporary so they can fix it. I paid for this app!
Click to expand...
Click to collapse
I can see it here in the market in France.

Same issue here
Hopefully EA sort this issue out..

As promised, update: they have forwarded the bug alert to the dev team, which will start working on it "as soon as possible".
Of course they weren't able to give me an ETA, so I suppose that all we can do is sit and wait.
Oh, and keep sending them bug alerts related to this issue, for all those that haven't done it yet. The more we are, the harder the pressure they will have, the quicker they will sort this out.

EA can't even get there console games fixed never mind the mobile platform games its a shambles
Sent from my Nexus 4 using xda premium

News????

[Q] Couldn't establish a secure connection. [SOLVED]

Using the latest rom from Task650 2013.02.23 I'm not able to connect to some secure sites. One example is https://stripe.com/ but there are plenty of others, but no names off the top of my head (just want to point out it's not unique to Stripe, happens with about 1 in 4 sites I've tried to use.) I ran into this quirk with older versions of this rom as well. Happen on a clean install, both stock browser and Chrome.
I'd potentially post in the development thread but where I'm a newbie it won't let me, sorry about that!
Any tips on how I might resolve this would be greatly appreciated. Or if you know where I might look to find a more verbose error log, that would be pretty awesome as well.
Thanks!
Edit: can't explain what happened, but after logging in to a Google Account on the device and installing a handful of apps/updates everything works as expected. Case closed, for now. If I figure out what happened I'll come back to post about it for others who might run into it.

Re: [Q] Couldn't establish a secure connection.
maττ said:
Using the latest rom from Task650 2013.02.23 I'm not able to connect to some secure sites. One example is https://stripe.com/ but there are plenty of others, but no names off the top of my head (just want to point out it's not unique to Stripe, happens with about 1 in 4 sites I've tried to use.) I ran into this quirk with older versions of this rom as well. Happen on a clean install, both stock browser and Chrome.
I'd potentially post in the development thread but where I'm a newbie it won't let me, sorry about that!
Any tips on how I might resolve this would be greatly appreciated. Or if you know where I might look to find a more verbose error log, that would be pretty awesome as well.
Thanks!
Click to expand...
Click to collapse
I'm able to get to the above website, as well as all the SSL sites I visit, credit cards, bank, mint, credit scores, ect.. without fail. I'm also on the 2/23 build from task. when flashing sometimes things can happen like this, even on a clean flash.
You may have to Odin back to stock to do a complete fresh reinstall of tasks ROM.
unrelated, I had to do so with a recent LTE issue that is now fixed.
Sent from my SGH-I747 using xda app-developers app

RPelham said:
I'm able to get to the above website, as well as all the SSL sites I visit, credit cards, bank, mint, credit scores, ect.. without fail. I'm also on the 2/23 build from task. when flashing sometimes things can happen like this, even on a clean flash.
You may have to Odin back to stock to do a complete fresh reinstall of tasks ROM.
unrelated, I had to do so with a recent LTE issue that is now fixed.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply RPelham!
I have jumped back to older versions of the rom but it still happens. I wipe caches, format /system and proceed with a clean install each time. The checksum matches on all files used so I'm relatively sure I'm downloading what's expected.
Your comment about LTE perks my curiosity. Although not on LTE myself, now that I'm home I've I connected to wifi and this issue isn't presenting. The only time I run into problems is when trying to connect to secure sites over cellular data.
My data plan isn't limited or being misused so I don't suspect they've throttled the connection. Not lucky enough to be on any unlimited data plan and no high usage coming from me. No high connection counts... really nothing all that notable. E-mails and calendar sync mostly.
Does Bell muck up HTTPS traffic? I would call them up but I feel tier 1 technical support isn't going to be much help until I narrow it down more.

maττ said:
I have jumped back to older versions of the rom but it still happens.
Click to expand...
Click to collapse
RPelham was referring to going back to stock (TW) and starting over with tasks aokp. that usually resolves almost every issue.

xBeerdroiDx said:
RPelham was referring to going back to stock (TW) and starting over with tasks aokp. that usually resolves almost every issue.
Click to expand...
Click to collapse
Oh I see. Perhaps this will sound silly, but how exactly does one do such a thing? Is there a thread somewhere on here with stock Bell I747 roms I can install using recovery?

maττ said:
Oh I see. Perhaps this will sound silly, but how exactly does one do such a thing? Is there a thread somewhere on here with stock Bell I747 roms I can install using recovery?
Click to expand...
Click to collapse
Search for stock firmware in the Android development section. Your bell version will be listed with the others. You'll need odin installed on your pc.

first though before you actually odin stock
Check your date & time setting
Click to expand...
Click to collapse

pcshano said:
first though before you actually odin stock
Click to expand...
Click to collapse
Time and date appear to be accurate. Haven't located the official roms just yet, will poke around and see what's around.

I loaded the stock rom and HTTPS sites works as expected. Rooted again, and installed the latest from Task (2013.02.26) and back to having these connection issues. Going to go post on the development thread, but any tips or ideas more than welcome! Thanks fellas

maττ said:
I loaded the stock rom and HTTPS sites works as expected. Rooted again, and installed the latest from Task (2013.02.26) and back to having these connection issues. Going to go post on the development thread, but any tips or ideas more than welcome! Thanks fellas
Click to expand...
Click to collapse
make sure you did a full wipe before posting in tasks thread. cheers

xBeerdroiDx said:
make sure you did a full wipe before posting in tasks thread. cheers
Click to expand...
Click to collapse
Well he was quick to reply and inform me my carrier is unsupported. Yeesh, like... really quick. You would think he lives here on xda. That aside I decided to try the slim rom and I hit the same issue. So it's not unique to task. However, I'm completely stumped at this point. It would be sweet if the browser would give a better error message! Keeping my eyes peeled for others with the same issue and possible solutions, but thanks again for the advice so far!

BUG: JB 4.1.2 update - Pressing Home Button to wake brings up task manager sometimes?

I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.

mkanet said:
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
Click to expand...
Click to collapse
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...

Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
dwitherell said:
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Click to expand...
Click to collapse

My annoying fix...
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.

I forgot to mention that lock screen prevents this bug from happenening. I'm guessing that's why not everyone has complained about the issue.. and why the bug somehow sneaked passed beta testing of 4.1.2. I would think this changed behavior was a new "feature" as horrible as it is, but it looks like it dad unintentional since its not consistent behavior.
I'm hoping that a kind android developer who also can't stand this problem, Kay offer a small script or app for rooted user to patch this problem.
mrtolles said:
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
Click to expand...
Click to collapse

mkanet said:
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
Click to expand...
Click to collapse
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test

You did it! Your fix works perfectly! The bug is gone! ...like the bug was never there. My understanding is the fix prevents the phone from stupidly trying to launch the task manager when the screen wakes by the home button. I also donated for you time and effort. Thanks a million.
dwitherell said:
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
Click to expand...
Click to collapse

No, thank you for making me learn how to put an odexed mod together and testing it for me!
So this fix will work for anyone running a stock odexed version of 4.1.2 UVBMB4 - you just need to be rooted, and having a custom recovery would be nice so you could flash it but you could also just copy the files over. That being said - would this be worthwhile to post?

I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.

mkanet said:
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
Click to expand...
Click to collapse
The flashable zip is just one method to get the files where they need to go. Literally all it does is overwrite the 2 files in /system/framework by moving the 2 files over from the zip - but there are definitely other ways to do such things. Some are more comfortable with this route, others are more comfortable w/ getting /system to be rw and move the files manually.
I'll likely post this at some point in the next few days

I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you

kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
Glad to hear

Is it possible that my phone isn't affected? If its a 4.1.2 bug, it should be in all phones with same version right?
This is not happening to my phone. Whether I have lock screen activated or not. I'm rooted but running stock ROM and I have Nova launcher installed if thats even important.

It's not all notes.
Sent from my SGH-T889 using xda premium

kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?

wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Yes you'll need to be rooted unfortunately - sorry

wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Absolutely. just PM me. Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.

kabuk1 said:
...Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
Click to expand...
Click to collapse
^^^ THIS - a thousand times over

[Q] CWM Recovery from GT-I9195 on SCH-l435?

Every day I get up and think to myself "there are only two things left that I'd like to do in terms of tweaking this phone":
The first is a succesful implementation of the v6 supercharger script, which at the moment has to be run manually. That's because there's a bug with SManager Script Manager that only effects Samsung devices. I'm in communication with the developer and that will hopefully be remedied soon.
The other is what I'd like to ask all of you about. It's regarding CWM Recovery.
My impatience has google repeatedly bringing me back to the same article on how to root/cwm GT-I9195.
Namely, this link: http://www.andromint.com/root-install-cwm-recovery-samsung-galaxy-s4-mini/
Now, my phone is SCH-l435 (Verizon). I'm already rooted. Are the odds good that CWM from GT-l9195 would work on my device?
Talk me down, wisers. Talk me down.

No
Sent from my SCH-I435 using Tapatalk

justlovejoy said:
No
Sent from my SCH-I435 using Tapatalk
Click to expand...
Click to collapse
Sorry if I seemed rude but my girl was asleep and the dang keys were waking her but I didn't want a potential brick of sorts to occur as I read the post in its freshness...
But no I dont think that'll work

hahaha
You had me at "no".
Waiting for someone else to solve all my troubles ...

RobinDean said:
hahaha
You had me at "no".
Waiting for someone else to solve all my troubles ...
Click to expand...
Click to collapse
I would ask @Phil3759 in this topic http://forum.xda-developers.com/showthread.php?t=2463322
If u can provide him with some info about your phone maybe he can help u out
Follow what fburgos did for I9192 and do the same
Don`t bother him on PM just mention him on that topic and wait patiently

If anything I've been working on it since last night, took a nap and I am back at it today, either way it shouldn't be long from now

Thanks, both of you. I'll check out the links as well this weekend.
As for your effort to get it going, wow ... you've got my gratitude!
Let me know if there's any way I can help. I'm not a developer but I am programmatically tech-savvy.

RobinDean said:
Thanks, both of you. I'll check out the links as well this weekend.
As for your effort to get it going, wow ... you've got my gratitude!
Let me know if there's any way I can help. I'm not a developer but I am programmatically tech-savvy.
Click to expand...
Click to collapse
well if you get a chance I need some help just message me

justlovejoy said:
well if you get a chance I need some help just message me
Click to expand...
Click to collapse
I have one of these phones and am willong to help in any way to get cwm. Samsucks software is killing me