Hello everyone. I am new here, sorry if I have posted in a wrong place. I've searched for similar problems, but I haven't found anything. Probably I am just dumb, but...
The problem is, I have Xperia SP C5303 with Android 4.3, rooted and of course bootloader is unlocked. On Google Play there are many Xperia themes that need root to change things like buttons etc. I have rooted my phone, yet they just don't work. It didn't really bother me, until I saw Legend of Zelda theme, which i immediately fell in love with. It says it needs root to work. Ooookay, so I download it, aaaand... Guess what. It didn't work. Please, help a dummy in need. Thanks.
Edit: Also official themes from Sony Select work.And the themes I am talking about don't need themers, I mean things like theme launchers etc. They install just as official themes do.
Doremic said:
Hello everyone. I am new here, sorry if I have posted in a wrong place. I've searched for similar problems, but I haven't found anything. Probably I am just dumb, but...
The problem is, I have Xperia SP C5303 with Android 4.3, rooted and of course bootloader is unlocked. On Google Play there are many Xperia themes that need root to change things like buttons etc. I have rooted my phone, yet they just don't work. It didn't really bother me, until I saw Legend of Zelda theme, which i immediately fell in love with. It says it needs root to work. Ooookay, so I download it, aaaand... Guess what. It didn't work. Please, help a dummy in need. Thanks.
Edit: Also official themes from Sony Select work.And the themes I am talking about don't need themers, I mean things like theme launchers etc. They install just as official themes do.
Click to expand...
Click to collapse
From what I have seen, it's a bug with some Xperia devices running 4.3. Seems like you need to use your root access to convert the downloaded apk into a system app and reboot and then it should show up.
es0tericcha0s said:
From what I have seen, it's a bug with some Xperia devices running 4.3. Seems like you need to use your root access to convert the downloaded apk into a system app and reboot and then it should show up.
Click to expand...
Click to collapse
Oh, okay, thank You. Could You please shortly explain how to do that? I am a dummy in these things on smartphones
This should work:
https://play.google.com/store/apps/details?id=de.j4velin.systemappmover&hl=en
Related
I'm very new to Android, my previous phone was a P3300... got my Legend 2 days ago. Very pleased with it!
Now, I see all this Custom made themes in some sites, that are zipped. I have been reading about it and have a very basic question...
How do you install those? I've read that on Hero you need to root the phone, but that isn't possible to do on the Legend yet.
I know it's really basic, but if someone could give a hand, would be very appreciated.
Thanks
I don't know how to install themes from zip file.
But if you want a different look to your legend look for home screen replacements in android marked. Home++ is my favorite, I hardly use the sense home screen any more..
Be carefull with the themes.
To install it you need start de recovery and install as a rom.
I don´t have sure that without root we can do this.
warriorofice said:
Be carefull with the themes.
To install it you need start de recovery and install as a rom.
I don´t have sure that without root we can do this.
Click to expand...
Click to collapse
I agree root is required for themes , paulobrien from modaco has rooted the legend
I´d recommend downloading ADW launcher, which is free and installing themes for that launcher....there are some free ones available on the market.
it´s really easy to use
Hi,
I´m writing this post to notify that there is a new official update from toshiba.
I cannot give more information, because my folio is in SAT, but the version number might be "18/02/2011 (2.2.5.0131)". I have no info about changes yet, but I´ve red something about preparation for the new flash player and more utilities.
My source:
htcmania.com/showthread.php?p=1874046&posted=1#post1874046
(Sorry, I can´t still post urls, you may add the usual www to check the adress)
Maybe we have new materials for our favourite mods (for me, Folionotion and foliomod, I can´t decide).
Any additional info will be wellcome, thanks
herozote said:
Hi,
I´m writing this post to notify that there is a new official update from toshiba.
I cannot give more information, because my folio is in SAT, but the version number might be "18/02/2011 (2.2.5.0131)". I have no info about changes yet, but I´ve red something about preparation for the new flash player and more utilities.
My source:
htcmania.com/showthread.php?p=1874046&posted=1#post1874046
(Sorry, I can´t still post urls, you may add the usual www to check the adress)
Maybe we have new materials for our favourite mods (for me, Folionotion and foliomod, I can´t decide).
Any additional info will be wellcome, thanks
Click to expand...
Click to collapse
New update is fantastic, touchscreen is super sensitive, battery lenght really improve, And rotation od screen is super fast and smooth. Flash work perfectly. Really a great update. Finally I can say thanks Toshiba.
Impressive the laggs are completly removed
MCLP said:
Impressive the laggs are completly removed
Click to expand...
Click to collapse
Is there support to market place?
Will we have it in mods ???
I have installed it.
It seems to be more performance in 3D games.
Flash plugin preinstaled, and it can run the flash animation in Toshiba's web page .
It solves some bug about brong accelerometer axis in some games.
But no Android Market, only the same *sigh* Toshiba Market.
The question is whether we can install FolioMod on top of this update or not. For me,it's not worth updating this without DexterMod, which is already very good imo
xitrumch said:
The question is whether we can install FolioMod on top of this update or not. For me,it's not worth updating this without DexterMod, which is already very good imo
Click to expand...
Click to collapse
if you wantt custom mods, you avoid the update!!!!
THIS UPDATE WILL BLOCK YOUR UPDATE OPTIONS, AND BYE BYE CUSTOM ROMS
I confirm that the root of 5.0131 is ok yessssssss !
I'm guessing this updates the recovery kernel, and the recovery kernel is the only place that the recovery kernel is visible from to write? So root access is not enough for a simple way of updating the whole OS partition.
tshoulihane said:
I'm guessing this updates the recovery kernel, and the recovery kernel is the only place that the recovery kernel is visible from to write? So root access is not enough for a simple way of updating the whole OS partition.
Click to expand...
Click to collapse
they might have blocked it on the new update as well, making it really hard to get revert.. but on previous editions you can easily write a new recovery.
the partition is visible at partition 7, but this might have changed.
i have not had the luxury to look at the actual update, so what is inside, is for me to find out.. then we get all the nasty details.
ok guys... anyone having installed this update pls kindly report the following:
1. stability status
(crashes freezez sod)
2. software issue - can sideloaded applications be installed and used?
3. root ability ?
4. 3d games like dangeon defenders working ?
5. custom flashing ability?
sader0 said:
ok guys... anyone having installed this update pls kindly report the following:
1. stability status
(crashes freezez sod)
2. software issue - can sideloaded applications be installed and used?
3. root ability ?
4. 3d games like dangeon defenders working ?
5. custom flashing ability?
Click to expand...
Click to collapse
1. no craches or freezing
2.3d games like the one mentioned should work has a charm
3.root ability yes
4.ability to sideloads apps not tested but should be fine since you can root its easily
5 custom flashing ability yes using adb to instal first the old kernel
basicly the tablets works has it was ment to be i think that toshiba might even suprise everyone by realeasing honeycomb for this tablet in future
When I go to Toshiba Service Station, there is no update available(using Dexters wonderful foliomod). How do I get to see it and if I want to install how do I keep all the wonderful stuff on it already. This is my wifes and not mine so she will get pissed off if she loses everything on it again?
Thanks.
go back to stock rom and update it should work
MCLP said:
2.3d games like the one mentioned should work has a charm
Click to expand...
Click to collapse
you will need build.prop changes to some games working, and gameloft is still the same as CPU has not changed..
MCLP said:
4.ability to sideloads apps not tested but should be fine since you can root its easily
Click to expand...
Click to collapse
So you can use market now
MCLP said:
5 custom flashing ability yes using adb to instal first the old kernel
Click to expand...
Click to collapse
guess how many users will ask how do it i think its a step backwards, and too complex for regulars...
MCLP said:
basicly the tablets works has it was ment to be i think that toshiba might even suprise everyone by realeasing honeycomb for this tablet in future
Click to expand...
Click to collapse
unless it got market, gmail and syncing support, its not like its meant to be yet..
and honeycomb will not appear as display is just 1024x600, so no chance of a google certification for folio100 here, same as with gapps support. so forgot toshiba solving that..
Saw people got honeycomb running on nook color with the same resolution screen... no certification does not mean that is not possible...so we still can have our fingers crossed on that
sader0 said:
Saw people got honeycomb running on nook color with the same resolution screen... no certification does not mean that is not possible...so we still can have our fingers crossed on that
Click to expand...
Click to collapse
i wrote: Toshiba do not deliver, that does not mean i can't
I don't doubt you can. But I guess this screen resolution difference could cause troubles in some apps again
Just read about the new update and the issues with it. I have my Folio sent in for repair and they always update to the latest firmware before sending back to customer, so it looks like im in deep ****. I know how to use adb and fastboot, use them all the time on my desire hd and my VEGA. Maybe someone could write a good guide on how to flash this old recovery and which of all the rooting procedures that works with the new firmware. I also dont know how to get Folio in fastboot. But if we have a working root we can flash the old recovery or clockwork recovery, is that right? Because if not i might as well throw it away. No use in trying to sell it, no one will buy a useless tablet anyways. HOPING FOR A GUIDE CALLED: HOW TO RESTORE YOUR FOLIO WITH FLASHABLE RECOVERY
Hi,
I recently installed a custom ROM in my phone.
What I noticed is that the problem is either that my phone drivers can't be installed for some reason (I have a SGS being treated as a Google Nexus S), or I just can't implement applications.
I mean that when I try to build an application on Eclipse, my phone is not recognized, like I don't have it plugged in.
Which one is it?
anyone?
spyshower said:
Hi,
I recently installed a custom ROM in my phone.
What I noticed is that the problem is either that my phone drivers can't be installed for some reason (I have a SGS being treated as a Google Nexus S), or I just can't implement applications.
Which one is it?
Click to expand...
Click to collapse
What do you mean by "I just can't implement applications"?
Do you mean you cannot install apps from the market? If so, are you sure you installed a ROM for the Samsung Galaxy S? Have you manually changed your screen DPI or is the ROM modified in any way regarding the screen DPI?
polobunny said:
What do you mean by "I just can't implement applications"?
Do you mean you cannot install apps from the market? If so, are you sure you installed a ROM for the Samsung Galaxy S? Have you manually changed your screen DPI or is the ROM modified in any way regarding the screen DPI?
Click to expand...
Click to collapse
I didn't describe my problem, my bad.
I mean that when I try to build an application on Eclipse, my phone is not recognized, like I don't have it plugged in.
I am pretty sure there is a simple answer and tons of people know if developing apps on custom roms is available. I dont get why none answers
spyshower said:
I didn't describe my problem, my bad.
I mean that when I try to build an application on Eclipse, my phone is not recognized, like I don't have it plugged in.
Click to expand...
Click to collapse
spyshower said:
I am pretty sure there is a simple answer and tons of people know if developing apps on custom roms is available. I dont get why none answers
Click to expand...
Click to collapse
Install the drivers for your device.
Comes up I had the drivers. I tried reinstalling them and it didn't work again.
I also tried it in another PC with no luck
Not sure if it matters but the custom ROM I have is Dark Knight 3.
I've never had luck getting fonts changed on ICS and now Jellybean for this device. Every time I attempt I bootloop and give up. Granted I'm only using the ROM Toolbox method as of now, but other program methods changed nothing as far as I could tell.
Is there a process that I'm missing? Attached is a zip containing the orgininal font and the modified version (to remove the [][][] boxes that were popping up)
Any insight would be greatly appreciated, as this font is gorgeous on smaller screens!
Try font changer in the play store. I havent used it with ICS or Jelly Bean. But I used it on Gingerbread and it worked perfectly.
jsgraphicart said:
Try font changer in the play store. I havent used it with ICS or Jelly Bean. But I used it on Gingerbread and it worked perfectly.
Click to expand...
Click to collapse
I guess I forgot to add, I used both that program and ROM Toolbox on Gingerbread (CM7) and it worked wonderfully. I didnt know if there was something else thats different about the install process. Or maybe due to the Alpha nature I shouldnt get my hopes up?
For the love of God, Mother Mary and all the saint's of the church, never use ROM Manager.......ever. That's like the golden rule. (for the X2, that is)
Well if font changer doesnt work, I dont know what else to say. Thats the only method I have used but like I said, I havent tried it on ICS or JB. ICS and JB might have a different method for fonts which may cause Rom Toolbox and font changer not to work. Do some google searches. I found this that might work for you. I would backup your rom before trying though.
http://forum.xda-developers.com/showthread.php?t=1821743
tallyforeman said:
For the love of God, Mother Mary and all the saint's of the church, never use ROM Manager.......ever. That's like the golden rule. (for the X2, that is)
Click to expand...
Click to collapse
Rom Toolbox =/= Rom Manager
magimog said:
Rom Toolbox =/= Rom Manager
Click to expand...
Click to collapse
For the Droid X2, either ROM Toolbox or ROM manager isnt recommended. These two apps can make changes to the ROM that our device doesnt support. Like stuff that requires an unlocked bootloader, which our device doesnt have. People have said that changing fonts or a boot animation will work fine but anything other than that, it can potentially cause big problems. So bottom line, be careful with what you do with it.
jsgraphicart said:
Well if font changer doesnt work, I dont know what else to say. Thats the only method I have used but like I said, I havent tried it on ICS or JB. ICS and JB might have a different method for fonts which may cause Rom Toolbox and font changer not to work. Do some google searches. I found this that might work for you. I would backup your rom before trying though.
http://forum.xda-developers.com/showthread.php?t=1821743
Click to expand...
Click to collapse
jsgraphicart said:
For the Droid X2, either ROM Toolbox or ROM manager isnt recommended. These two apps can make changes to the ROM that our device doesnt support. Like stuff that requires an unlocked bootloader, which our device doesnt have. People have said that changing fonts or a boot animation will work fine but anything other than that, it can potentially cause big problems. So bottom line, be careful with what you do with it.
Click to expand...
Click to collapse
I was pointing out that Rom Manager is in no way the same thing as Rom Toolbox. The former deals with rom downloads, mods and recovery installation, whereas the other is a collection of root tools. Toolbox is just a hub for the multitude of JRummy apps. I've only used it to have a one-stop for adblocking, root browser and animation/theme changing. Those 3 tasks work perfectly in CM9/10.
I will just try manually switching out the fonts to see if that changes anything. I was looking to see if there were other X2 users who were successful in performing this task within a CM9/10 environment. I'll assume no one has for now.
Well I havent seen anyone else ask about changing fonts in ICS or JB. I wouldnt know how to do it if the other two methods dont work. Again, I would search around for a Universal method rather than one specifically for the DX2. I think the usual methods not working are more due to the change of the way ICS and JB handle things than our ROM not being complete though.
Hey guys, my question is essentially what the title says. I find that in CM10 based roms, that whenever I use the stock cyanogen mod browser, it automatically goes into desktop mode (and is stuck there. The desktop mode checkbox, however, is unchecked.) I'm fairly sure it worked before I used the touch pad fix here - http://forum.xda-developers.com/showthread.php?t=1893343 - So I think it might be a framework/build.prop issue, but I'm not sure. I've been looking to fix this problem everywhere but haven't really been able to find a solution. Do you guys have any idea what the fix might be?
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
smokerman said:
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
Click to expand...
Click to collapse
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
fishvtt said:
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
Click to expand...
Click to collapse
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Hey, smokerman, would you know how to mess with .jar files. I kinda want to go exploring to see if I can do anything.
you have here a simple guide by @CriGiu
http://forum.xda-developers.com/showthread.php?t=2322231
could help you.:good:
fishvtt said:
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
Click to expand...
Click to collapse
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
Oh ok, I'll try testing that out.
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
All right, well that seems to do the trick. When I try to use the touchpad activator app, it gives me the "error 5 expected reciever of type android.view.ViewRoot, but got android.view.ViewRootImpl". But, Dead Trigger works perfectly how it's supposed to, and the stock browser is using the mobile version now. Just remember to make the necessary build.prop changes as outlined in Fahrenheit's guide.