Related
Im actually not sure if its from donut, anyone know?
Im talking about the 4x1 widget included in cyanogen's builds with all of the settings to toggle, can it be taken from his builds and installed with an app installer onto an unrooted mytouch?
i like the look of it and from what i understand it includes a one-click gps toggle...thanks
the widget is called
'power control'
As to the question, i'm not sure about if it can be taken
fair enough, thanks for the response. At least maybe my xda/google search attempts will be more effective using the actual name of it...
It might be from donuts.
If youy DL SDk 1.6 you will find this widget in the emulator.
The Widget is in the Settings.apk.
maxisma said:
The Widget is in the Settings.apk.
Click to expand...
Click to collapse
thanks maxisma. sorry i have to ask this because im sure the answer is obvious to most, but it said 'settings app cannot be installed on this phone..." Is there anything else i need to install to get it to work? As when I installed pdf onto my g1 there were 2 other files i had to install through the emulator, which, since my mytouch is not rooted I dont think would be possible.
Any suggestions would be great, thanks
by the way i used settings.apk from cyanogen 4.0.2, its the last one i downloaded...
I think I remember reading that it was from/for Donut. I never found it in the market though.
1-click GPS toggle, its only just occured to me that someone solved it. Awesome.
Alright, first of all, this is an internal device, I will not be using these changes on my own device.
We use tablets (previously Galaxy Tabs) in our office for employees to use an internal application. Our application manages its own navigation, and users do not need to access anything else other than the application. I made it a home screen launcher so it's the first thing that loads. On the Galaxy Tab (Android 2.3), I'm also hijacking all the hardware buttons in the device and I can properly secure the device.
However, on Android 3.0, there are no hardware buttons anymore, and you cannot hide the system bar, I have no way to secure the device if the system bar is always there. I understand why it needs to be there, but this is really killing me.
I have 3 options:
Root the device, try to disable the system bar by editing the framework-res.apk --- Already tried this, unsuccesful since I couldn't find anything in there.
Wait for Android 3.0 to drop in AOSP, build my own custom rom which hides the system bar and do my own modifications on it.
Build Android 2.3 from AOSP for the XOOM -- this will be a lot of work, and I would need help, is anyone interested on helping me with this?
Thanks everyone.
velazcod said:
Alright, first of all, this is an internal device, I will not be using these changes on my own device.
We use tablets (previously Galaxy Tabs) in our office for employees to use an internal application. Our application manages its own navigation, and users do not need to access anything else other than the application. I made it a home screen launcher so it's the first thing that loads. On the Galaxy Tab (Android 2.3), I'm also hijacking all the hardware buttons in the device and I can properly secure the device.
However, on Android 3.0, there are no hardware buttons anymore, and you cannot hide the system bar, I have no way to secure the device if the system bar is always there. I understand why it needs to be there, but this is really killing me.
I have 3 options:
Root the device, try to disable the system bar by editing the framework-res.apk --- Already tried this, unsuccesful since I couldn't find anything in there.
Wait for Android 3.0 to drop in AOSP, build my own custom rom which hides the system bar and do my own modifications on it.
Build Android 2.3 from AOSP for the XOOM -- this will be a lot of work, and I would need help, is anyone interested on helping me with this?
Thanks everyone.
Click to expand...
Click to collapse
Downgrading to 2.3 might be your best bet, wish 3.0 AOSP would hurry up, want to get somethings working differently as well myself. Let us all know if you downgrade and how it went! Wouldn't mind trying to sneak the shut off animation onto 3.0 if possible.
kenhunt said:
Downgrading to 2.3 might be your best bet, wish 3.0 AOSP would hurry up, want to get somethings working differently as well myself. Let us all know if you downgrade and how it went! Wouldn't mind trying to sneak the shut off animation onto 3.0 if possible.
Click to expand...
Click to collapse
Yeah, I haven't gotten into it yesterday, but the only thing I'm concerned about running 2.3 on the Tab is the whole issue with Dual-core support, not sure if I would even be able to do it thanks to that, but I'll see. I'm also trying to call a few contacts to see if we can get into some kind of agreement with Moto to try to get the source code early... we'll see...
Have you tried running a different launcher? They allow you to hide system bars on the old android os...might work on 3.0
Sent from my PC36100 using Tapatalk
bwcorvus said:
Have you tried running a different launcher? They allow you to hide system bars on the old android os...might work on 3.0
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Yeah, that won't work, the system bar is part of the framework, it's very very low level, you can't hide it since it allows the user to navigate through the device. Before 3.0, devices were required to have hardware buttons, that's not a requirement anymore because of this system bar, it will always always be there.
Atrix runs 2.3 and the same processor
destroyerbmx said:
Atrix runs 2.3 and the same processor
Click to expand...
Click to collapse
True, hopefully they release the kernel source soon so I can take a look and see if I can try to make 2.3 work on the XOOM with the same kernel that's working with 3.0.
here is Tegra 2 with many options running various versions of 2.2 and 2.3.
you should reach out to GoJimi over there.
destroyerbmx said:
Atrix runs 2.3 and the same processor
Click to expand...
Click to collapse
I'm pretty sure atrix is running 2.2.
u can't do anything until source drops. You need baksmali for framework and custom recovery to flash.
I think your best bet would probably be changing the DPI settings somehow (Like they did for the HC build on some phones to get the tablet version) and it would cause you to go into the "phone" version of HC (Doesn't have the system bar) then I would say modify the volume buttons and lock button long presses to recreate the home/back/multitasking buttons if you really want them (such as they have done for the i*hone android ports because ios is dumb and has 1 button). Just a suggestion and honestly I have no idea if this would work.
I'm sure the system bar has a process you can kill with root. I know the status bar can be killed this way on 2.3. Watch logcat and see what you can find. Anyone know more on this?
Porting 2.2 from the g-tab maybe. Similiar hardware I think.
Sent from my Nexus One using XDA Premium App
Just installed lcd denisty on mine and put it at 240 from the default 160...the system bar was gone.
bwcorvus said:
Just installed lcd denisty on mine and put it at 240 from the default 160...the system bar was gone.
Click to expand...
Click to collapse
Glad to see it worked now hopefully the OP sees it. GL to all
Sent from my SCH-I500 using XDA App
Could you please check your /system/build.prop to see whether the lcd density app has added any code?
I usually tweak density directly through this file but the code isnt there atm on my xoom.
I tried changing the density yesterday and was disappointed to discover that the LCD density wasn't in the build.prop. adding the line of code didn't work, either.
XOOM'd from the XDA app.
ftgg99 said:
Could you please check your /system/build.prop to see whether the lcd density app has added any code?
I usually tweak density directly through this file but the code isnt there atm on my xoom.
Click to expand...
Click to collapse
Looking at the date on my build.prop it hasn't been modified. And just to be sure i looked through the file, nothing in there.
Huh, I wasn't receiving notifications on email even though I'm subscribed for instant notifications...
anways, will try the density trick, but that seems like a pain in the butt to redo all the layouts in our app, but that is a very very clever idea, might work.
Update: Yes it works, but only if you use one of those apps, not when editing the system.prop file, anyone care to share what's exactly being edited here?
Thanks again!
Update 2: Actually, I had a typo on the line I wrote on the build.prop, if you write 'ro.sf.lcd_density=240' (or whatever density you want to use), push it and reboot, it does work as it should.
how are u going to press "home" or "back"?
xoom doenst have physical buttons like phones.
how do u get back to home screen if u downgrade to 2.x？
Hi,
I don't know if someone else found this problem. I made a video:
http://www.youtube.com/watch?feature=player_embedded&v=RS9j4uiTDaE. It's also in FullHD.
And wrote a post in my blog in my native language, spanish: http://retreteinformatico.blogspot.com/2012/01/touchwiz-40-y-problemas-con-la.html
The video description is english. I'll also explain the problem here:
Simply put, TouchWiz does not save the icons in the place where I leave them. At first I organized all of them in two screens: one with folders and the other with most frequently used icons. After doing a power on-off cycle the icons are all scattered without alphabetical order in three screens instead of two. The folders maintain their ordering and screen. An icon (AllShare) is put between two folders and the other icons are divided in two screens, disordered, not alphabetical.
In the video you'll see first what I found after the icon position screwing. Then I get three or four apps out of their folder (Google Talk, Gmail, Maps, Market) and put them with the rest of the icons and the AllShare app is put with the rest, out of the screen with the folders. Then I power off the phone and turn it on again to find that GTalk, Maps, Market and AllShare are out of their place.
After that, I put the icons more or less where I want to put them (in two screens) and I do again a power cycle to show how did TouchWiz screw my icon organization.
I'm using Android 2.3.4 XWIK4 with baseband XXKI1.
If someone is able to reproduce the problem just tell it. Maybe touchwizh has problems if you put in folders the Samsung apps (Hubs and more), I don't know, but it's a big problem.
Folder/Icon rearrangement is a known problem with TouchWiz since day 1 when SGS2 got released.
Best way to get around is to use AppSorter and sort your App Drawer everytime you create a folder.
Posting problems about 2.3.4 when everyone else is on 2.3.6 = VERY SERIOUS BUSINESS!
Update your phone and test it and give feedback!
Hmmm, I didn't know. How comes that Samsung hasn't fixed this in 8 monts?
This is ludicrous.
Beta is bad
Filiprino said:
Hmmm, I didn't know. How comes that Samsung hasn't fixed this in 8 monts?
This is ludicrous.
Click to expand...
Click to collapse
Love the name of your blog: informatic toilet (retrete informatico) ahahah
Anyway: They suck on fixing bugs.. if we users and devs cant fix'em we are screwed lol
Also, why any reviewer spoted this problem? Add to this the Fujitsu camera module problem and you get the idea that QA on Samsung is really poor. Just remember the GPS problem on Samsung Galaxy S1.
ForTR said:
Beta is bad
Click to expand...
Click to collapse
I didn't say to update to ICS beta... just update to XWKK5 and he should be alright!
Anyway i tried to do the same he did in my SGS2 and it keeps icons in their folders..
Using checkrom revo v4
zylor said:
I didn't say to update to ICS beta... just update to XWKK5 and he should be alright!
Anyway i tried to do the same he did in my SGS2 and it keeps icons in their folders..
Using checkrom revo v4
Click to expand...
Click to collapse
My icons are kept in their folders. The problem is the icons that are out of their folders. I'm using original Android, no beta nor custom ROMs.
Filiprino said:
My icons are kept in their folders. The problem is the icons that are out of their folders. I'm using original Android, no beta nor custom ROMs.
Click to expand...
Click to collapse
i rooted my phone and installed checkrom revo v4 and don't have that problem! What is weird to me is that i always used folders and that issue never came to me
zylor said:
i rooted my phone and installed checkrom revo v4 and don't have that problem! What is weird to me is that i always used folders and that issue never came to me
Click to expand...
Click to collapse
I read your first post about upgrading to 2.3.6. Well, if I just use the default Samsung support, I'm stuck to 2.3.4, as my phone is Austrian version and Samsung didn't release nothing newer than 2.3.4 for those phones.
So Samsung sucks big as a company and client support.
Of course if I start to root the phone and installing custom ROMs the problem would disappear, but flashing your phone and breaking your warranty is not something the user should do for something that's supposed to work from the beginning. Different thing is if the user wants extra functionality, but this is not the case.
So, all in all, I'll wait until ICS gets released and after that if it doesn't convince me, I'll root and who know if I flash a custom ROM.
I had that trouble before where one app ended up going to the next page and kept going back there. I think simply restoring the order, going to TwLauncher in the application list and then force stopping should make it remember the order you gave it once you go back.
ProtoKun7 said:
I had that trouble before where one app ended up going to the next page and kept going back there. I think simply restoring the order, going to TwLauncher in the application list and then force stopping should make it remember the order you gave it once you go back.
Click to expand...
Click to collapse
If I force stop TwLauncher the apps are again "out of control" :-/
I'll try to clear the cache although I'm reluctant because I'll need to recreate all folders again
I have partially solved the problem by clearing the cache of TouchWiz launcher.
Now the SIM service app keeps going back to the same place out of its folder, but I refuse to clear again the cache and organize all my apps. Maybe it's because the SIM service app is something variable. If I kill touchwiz process that app appears inside it's folder (once the cache corruption is solved), but if I turn off the phone and turn on again, the SIM app appears out of the folder.
This is crap.
Well, know what? I've installed some applications at one time, all from Samsung Apps, and after rebooting the phone all my folders are empty and the apps inside them are all spread across 6 screens instead the 2 screens I managed to sort. The apps and folders have lost the position I assigned to them.
Now I have a bunch of icons in random order and I don't want to organize again 6x8 = 48 icons plus the home screens which would turn to default state after clearing the cache of the touchwiz manager.
It's very annoying and unusable. I want to throw the phone through the window.
What I can't understand is how this bug has been happening since launch date and Samsung hasn't been able to solve it. My only hope is the ICS update and I don't have much confidence on it. Probably I'll have to flash a custom ROM and then try to get some Samsung software on it.
The free games offer is very good
PS: Well, maybe it has some explanation->Samsung's poor software development quality assurance. Camera's firmware also suffer from it.
Filiprino said:
I read your first post about upgrading to 2.3.6. Well, if I just use the default Samsung support, I'm stuck to 2.3.4, as my phone is Austrian version and Samsung didn't release nothing newer than 2.3.4 for those phones.
So Samsung sucks big as a company and client support.
Of course if I start to root the phone and installing custom ROMs the problem would disappear, but flashing your phone and breaking your warranty is not something the user should do for something that's supposed to work from the beginning. Different thing is if the user wants extra functionality, but this is not the case.
So, all in all, I'll wait until ICS gets released and after that if it doesn't convince me, I'll root and who know if I flash a custom ROM.
Click to expand...
Click to collapse
With all due respect, and not aiming to sound rood to you, with that mentality (it should work fine out of the box and I don't care if somewhere else there's a newer version...) you shouldn't be posting on XDA because people we'll obviously tell you to upgrade to the latest version, whether it's from a different operator/country (legit) or simply a leak.
You can't expect people here to act like the only way to use the phone is by following what Samsung/your operator is dictating you. We all know and have long ago agreed that operators and manufacturers are lazy when it comes to QA, and that's why a place like XDA exists
zsidane said:
With all due respect, and not aiming to sound rood to you, with that mentality (it should work fine out of the box and I don't care if somewhere else there's a newer version...) you shouldn't be posting on XDA because people we'll obviously tell you to upgrade to the latest version, whether it's from a different operator/country (legit) or simply a leak.
You can't expect people here to act like the only way to use the phone is by following what Samsung/your operator is dictating you. We all know and have long ago agreed that operators and manufacturers are lazy when it comes to QA, and that's why a place like XDA exists
Click to expand...
Click to collapse
The camera firmware bug affects to all people, doesn't matter if you have stock Android or custom ROM. So we're all in the same bag. And this is Galaxy S II General forum, so I post this here because norms allow it.
Anyways, thanks for your reading.
Actually clearing the cache helped! Ever since I updated to 2.3.6 I have had this problem but after clearing the cache it has been resolved. But initially after the update the folders did remember for a couple of days after which the problem started for me. But for now clearing the cache worked well.
Hello, did u guys already tried Menu>Save in app drawer after modifying/rearranging apps/folder?
Sent from my GT-I9100
Oh no. Here I am posting again within a few days with another issue.
My previous issue can be found here:
http://forum.xda-developers.com/showthread.php?t=1459225
I just turned my phone off to attend a few classes and when I turned it on my lockscreen was invisible (so could not unlock phone) and I saw an error on the top bar saying my memory storage was empty. If I reinsert my sd card the error goes away but lockscreen is still invisible. The phone does nothing. I hate to say it but I'm thinking about switching outta this ROM. It's moving fast when it DOES work so would love some help on this.
Thanks in advance.
This happened to me when flashing, i had to flash, reflash reflash reflash until it finally came up, Maybe try rebooting it a bunch of times?
This happened to me as well when I tried MikG 3.0. You might want to try going into recovery and selecting the mounts and storage option and choose mount emmc. If it gives you an error, then your EMMC is borked and you must flash back to a stock incredible based from (such as TeeRom, Ice Cream Sense, or Stock GB) to format phone storage. You'll lose everything on EMMC but it will fix your issue. I also took out my SD card before choosing to format phone storage just to be safe
Looks like something is causing this issue on Mik3.0 and I unfortunately must advise backing up your emmc before using it.
Sent from my Droid Incredible using the XDA app.
What Mods are the two of you using? Ext4, themes not in the MikG forum? I need to know so I can try to recreate the problem. As I said in another post, this ROM does NOT even touch the emmc partition. Let me know what changes you've made. I can't help you with no information. There's been a hundred downloads and you two are the only ones I see with an emmc issue. Are your phones new, used, eBay? Thanks for the info.
EDIT: Also, what CWM recovery are you using?
Sent from my HTC Droid Incredible
My info:
- Bought brand new 1.5 years ago
- CWM 5.0.2.0
- Hboot 0.92
- Nothing additional was flashed, not even tiny's kernel
- Wiped Data/Factory Reset, boot and system from CWM before flashing
- Restored apps with data from Titanium
- Set up Google and Facebook accounts
- Installed and applied Slate.apk
- Applied the following tweaks:
Font: Roboto
Autobrightness: Lowest
Boot Animation: HTC Stock
Down Animation: ATTEMPTED to switch to HTC Stock, however it was hanging on the download so I hit home to get out of the screen.
Status Bar Transparency: Switched to transparent, switched back
Rosie Drawer Scrolling: Disabled
Quick Settings: Disabled various quicksettings (4G, ADB Wireless, Silent, Vibrate)
Animation speed: Switched from Normal to slow on both transition and window
- Edited build.prop ro.fingerprint to reflect GB instead of Froyo so I don't get the OTA nag
- Set up everything all nice and stuff
I may have missed something, but that's pretty much what I did.
Div033 said:
My info:
- Bought brand new 1.5 years ago
- CWM 5.0.2.0
- Hboot 0.92
- Nothing additional was flashed, not even tiny's kernel
- Wiped Data/Factory Reset, boot and system from CWM before flashing
- Restored apps with data from Titanium
- Set up Google and Facebook accounts
- Installed and applied Slate.apk
- Applied the following tweaks:
Font: Roboto
Autobrightness: Lowest
Boot Animation: HTC Stock
Down Animation: ATTEMPTED to switch to HTC Stock, however it was hanging on the download so I hit home to get out of the screen.
Status Bar Transparency: Switched to transparent, switched back
Rosie Drawer Scrolling: Disabled
Quick Settings: Disabled various quicksettings (4G, ADB Wireless, Silent, Vibrate)
Animation speed: Switched from Normal to slow on both transition and window
- Edited build.prop ro.fingerprint to reflect GB instead of Froyo so I don't get the OTA nag
- Set up everything all nice and stuff
I may have missed something, but that's pretty much what I did.
Click to expand...
Click to collapse
Only thing I see I don't like and don't recommend is TB with data. I have never had ANY luck keeping things stable doing that. Not saying that's it, just pointing it out. Still not seeing anything. Sorry. Just not sure how the ROM can do this. I asked Aamikam, the dev for the EVO version of this for his thoughts. He's not sure how this is even possible since the ROM doesn't touch emmc. Not sure.
Sent from my HTC Droid Incredible
countryfolk07 said:
Only thing I see I don't like and don't recommend is TB with data. I have never had ANY luck keeping things stable doing that. Not saying that's it, just pointing it out. Still not seeing anything. Sorry. Just not sure how the ROM can do this. I asked Aamikam, the dev for the EVO version of this for his thoughts. He's not sure how this is even possible since the ROM doesn't touch emmc. Not sure.
Sent from my HTC Droid Incredible
Click to expand...
Click to collapse
There are four reported cases of this issue on these forums so far; the OP of this thread, two more in the rom thread and myself. Still not as widespread as it could be, but it must be a rom issue. I've been restoring apps with APP data (never system data) through titanium in every rom flash and never have any issues, so I do not believe that is it. However I am not ruling it out. I forgot to mention I have an AMOLED screen if that makes any difference.
Div033 said:
There are four reported cases of this issue on these forums so far; the OP of this thread, two more in the rom thread and myself. Still not as widespread as it could be, but it must be a rom issue. I've been restoring apps with APP data (never system data) through titanium in every rom flash and never have any issues, so I do not believe that is it. However I am not ruling it out. I forgot to mention I have an AMOLED screen if that makes any difference.
Click to expand...
Click to collapse
I also have AMOLED. What I'm not understanding is that I have flashed the exact .zip the reported cases have flashed. I've not seen the issue. Very frustrating, this is my favorite ROM and just wanted to be able to share with others, because this has always been a favorite.
Sent from my HTC Droid Incredible
Those having various issues, there is an updated build.prop on the mikmik site. Try it please.
Sent from my HTC Droid Incredible
countryfolk07 said:
I also have AMOLED. What I'm not understanding is that I have flashed the exact .zip the reported cases have flashed. I've not seen the issue. Very frustrating, this is my favorite ROM and just wanted to be able to share with others, because this has always been a favorite.
Sent from my HTC Droid Incredible
Click to expand...
Click to collapse
Good ol' software.
I'll try and troubleshoot it tomorrow perhaps. I love this rom as well and if I can get MMS over Wifi working like you say you have then it'll be a daily driver for sure.
What we know:
- Issue happens after a reboot
- EMMC is repartitioned as something completely different/is corrupted, making the volume unreadable.
- Upon boot, apps and whatnot seem to start up but no lock screen is present. The entire device does not respond to touches, including the capacitive buttons and hardware buttons excluding the power button (holding it does nothing though) to turn the screen off and on. Perhaps its having trouble loading Rosie.apk?
Also, I remember I did freeze some HTC stuff I don't use, but I don't recall freezing anything out of the ordinary. When I go back to troubleshoot I'll redo everything step by step, rebooting after each change.
Sent from my Droid Incredible using the XDA app.
Ok guys. I'be figured out what happened, just have to fix it. There is no emmc on the EVO. I have to trick our phone into seeing it. Talking to Newt to figure this out. Thanks for your patience.
Sent from my HTC Droid Incredible
countryfolk07 said:
Ok guys. I'be figured out what happened, just have to fix it. There is no emmc on the EVO. I have to trick our phone into seeing it. Talking to Newt to figure this out. Thanks for your patience.
Sent from my HTC Droid Incredible
Click to expand...
Click to collapse
This is great news! Keep us posted
I've been having the same issues mentioned, I took me 3 flashes to get the lockscreen to work and occasionally when I do reboots it won't show up and I'll have to do a battery pull. I also get the sd notifications sometimes, the sd card still works but the notification stays there. Another problem I've been having is that annoying system update from verizon, it keeps popping up and I don't know how to get rid of it. Any ideas?
Stratman14 said:
I've been having the same issues mentioned, I took me 3 flashes to get the lockscreen to work and occasionally when I do reboots it won't show up and I'll have to do a battery pull. I also get the sd notifications sometimes, the sd card still works but the notification stays there. Another problem I've been having is that annoying system update from verizon, it keeps popping up and I don't know how to get rid of it. Any ideas?
Click to expand...
Click to collapse
Build prop update at the mikmik will help with the update nag. Also, I finally got the SD/emmc , and lockscreen issue, all at the same time after doing a font. For two weeks I had no issues, until I decided to change fonts in tweaks. Anyone having these issues after changing fonts? Just trying to troubleshoot some more.
Sent from my ADR6300
countryfolk07 said:
Build prop update at the mikmik will help with the update nag. Also, I finally got the SD/emmc , and lockscreen issue, all at the same time after doing a font. For two weeks I had no issues, until I decided to change fonts in tweaks. Anyone having these issues after changing fonts? Just trying to troubleshoot some more.
Sent from my ADR6300
Click to expand...
Click to collapse
I switched to Roboto font during my run, but I did a bunch of other tweaks previously mentioned before rebooting so I couldn't single it out for sure. Sure does seem like the culprit now though!
Sent from my Droid Incredible using the XDA app.
Div033 said:
I switched to Roboto font during my run, but I did a bunch of other tweaks previously mentioned before rebooting so I couldn't single it out for sure. Sure does seem like the culprit now though!
Sent from my Droid Incredible using the XDA app.
Click to expand...
Click to collapse
Yes it does.!!!!!! Maybe were on to something. Everyone else with the lockscreen/emmc issue, please, please, please, let me know if you switched fonts. Thank you.
Sent from my ADR6300
I have the issues and I did not switch fonts...
Stratman14 said:
I have the issues and I did not switch fonts...
Click to expand...
Click to collapse
Aghhhhhh!!!!!! Your emmc was wiped out? Or just lockscreen issue?
Sent from my ADR6300
I haven't had the lockscreen issue in a while but I keep getting a notification that won't go away saying "Phone storage is empty or has unsupported files". And how do you push build.prop with root explorer?
Stratman14 said:
I haven't had the lockscreen issue in a while but I keep getting a notification that won't go away saying "Phone storage is empty or has unsupported files". And how do you push build.prop with root explorer?
Click to expand...
Click to collapse
Download the file to your SD card. Make a backup of your current build.prop. Call it build.prop.old. Copy the downloaded build.prop and paste to /system directory. Then change permissions to rw-r--r-- . Do all of this before a reboot. To change permissions, make sure system is r/w enabled, then long press file and select permissions.
Sent from my ADR6300
What's the best way to get Emoji's working? Being able to see them would be nice... but just sending them would be fine. Anyone have a way of doing this? I know about Handcent/GO SMS emoji extensions but I like the stock TW messaging app, so I don't wanna do that.
EDIT: Also, I'm talking about being able to send them everywhere (Messaging, Twitter, Instagram, etc.). Seeing them everywhere would also be a plus as mentioned above
Well if you don't want to use a different messaging app, then you have to replace the system font with one that has emoji support I believe.
Edit: Or you can flash the zip here for the default android emoji http://www.androidcoliseum.com/2013/06/how-to-get-422-emoji-keyboard-on-your.html
Stealyourface said:
Well if you don't want to use a different messaging app, then you have to replace the system font with one that has emoji support I believe.
Edit: Or you can flash the zip here for the default android emoji http://www.androidcoliseum.com/2013/06/how-to-get-422-emoji-keyboard-on-your.html
Click to expand...
Click to collapse
Thanks! I also found a workaround: http://forum.xda-developers.com/showthread.php?t=1792745
That let's me see them, and your link will let me send them, SWEET! Now if only they were in color lol -___-
Joe0113 said:
Thanks! I also found a workaround: http://forum.xda-developers.com/showthread.php?t=1792745
That let's me see them, and your link will let me send them, SWEET! Now if only they were in color lol -___-
Click to expand...
Click to collapse
Well from 4.1 and up you should be able to see it by default because they baked it into jellybean. That's where the keyboard comes from. Color though, good luck with that one
Stealyourface said:
Well from 4.1 and up you should be able to see it by default because they baked it into jellybean. That's where the keyboard comes from. Color though, good luck with that one
Click to expand...
Click to collapse
My friend was sending me em... and I saw all of them except for a few. Did that little trick in the post I mentioned above, and went back into my messaging app and was able to see every single one! And yeah I know I wish we could do that somehow!
Joe0113 said:
My friend was sending me em... and I saw all of them except for a few. Did that little trick in the post I mentioned above, and went back into my messaging app and was able to see every single one! And yeah I know I wish we could do that somehow!
Click to expand...
Click to collapse
i clicked on the s3 link you referred to. the xml file is no longer downloadable but i was able to grab the 9.83mb font file. So all you did was replace the original droidsansfallback with the modified 9.83mb file one and rebooted your phone?
I tried doing that and still cannot see received iphone sms emojis. (i can see emojis on all other apps besides the sms apps, including Handcent + emoji plugin)
yellowxboy said:
i clicked on the s3 link you referred to. the xml file is no longer downloadable but i was able to grab the 9.83mb font file. So all you did was replace the original droidsansfallback with the modified 9.83mb file one and rebooted your phone?
I tried doing that and still cannot see received iphone sms emojis. (i can see emojis on all other apps besides the sms apps, including Handcent + emoji plugin)
Click to expand...
Click to collapse
Here.
Try using the stock TW messaging app.