Related
I'm running TAZv9 mod and have a nice looking color mod that makes my phone look and run really nice. Just curious if there was anyway to change the color on the screen that comes up when you are in a call. It has a red background when the call ends and green while you are in the call. Is there anyway to change this to a blue or whatever when you are in the call...basically is this something that can be skinned with one of the programs that is out there(MetaMorph).
I'm 41 years old and my 20 yr. old son has gotten me into this whole rooting thing. I appreciate you all letting an old guy hang in your forum. I write test software for a living so I am interested in maybe getting to the point where I can start messing with my own software apps, etc.
I'm sorry if the question seems really dumb to all you bright young people, but I couldn't find anything about it on the search button.
Thanks for any info and help,
THEEDGE
I can probably put together a quick metamorph for you. The file is in Phone.apk
So instead of the green gradient you want a blue gradient? And keep the red gradient when it ends?
Just place the attached file on your sdcard in "AndroidThemes" and use Metamorph.
Yep. That is exactly what I want. Thanks!
Sent from my Cyanogen Froyo using XDA App
Hey, not sure if you have had a chance to make that blue gradient yet? I was thinking I might just try to do it myself. So, do I just find the file on my phone, copy it to my
Sent from my Cyanogen Froyo using XDA App
Its attached to my post above.
Copy it to my computer and then use something like photoshop to edit it?
Sorry about the two posts...I was replying from my phone and somehow hit the menu and send as I was typing away. Is that file recognized by most picture editing software packages or do I need to convert it somehow? Thanks for any and all information. If there is a post or Wiki about this somewhere Im sorry...please point me in the right direction.
Thanks
THEEDGE
Sent from my Cyanogen Froyo using XDA App
Crap...sorry, I can't see it from the app on my phone.
Thanks again!
Sent from my Cyanogen Froyo using XDA App
fzpb61 said:
Copy it to my computer and then use something like photoshop to edit it?
Sorry about the two posts...I was replying from my phone and somehow hit the menu and send as I was typing away. Is that file recognized by most picture editing software packages or do I need to convert it somehow? Thanks for any and all information. If there is a post or Wiki about this somewhere Im sorry...please point me in the right direction.
Thanks
THEEDGE
Sent from my Cyanogen Froyo using XDA App
Click to expand...
Click to collapse
Just download the file and your computer. Hookup your phone and mount the sdcard. Then create a folder on it called "AndroidThemes". Next download "Metamorph" from the market. Run it and select the "blue-in-call" theme, and apply it.
Yes...I figured that out and it looks great. My questions were about what you used to modify the graphic (Photoshop)? Im hoping to start modifying some stuff and make my own graphics to use with Metamorph.
Thanks again for your help and for not flaming the old guy!
Sent from my Cyanogen Froyo using XDA App
fzpb61 said:
Yes...I figured that out and it looks great. My questions were about what you used to modify the graphic (Photoshop)? Im hoping to start modifying some stuff and make my own graphics to use with Metamorph.
Thanks again for your help and for not flaming the old guy!
Sent from my Cyanogen Froyo using XDA App
Click to expand...
Click to collapse
There was a blue gradient in the apk already. I just renamed the file.
fzpb61 said:
I'm running TAZv9 mod and have a nice looking color mod that makes my phone look and run really nice. Just curious if there was anyway to change the color on the screen that comes up when you are in a call. It has a red background when the call ends and green while you are in the call. Is there anyway to change this to a blue or whatever when you are in the call...basically is this something that can be skinned with one of the programs that is out there(MetaMorph).
I'm 41 years old and my 20 yr. old son has gotten me into this whole rooting thing. I appreciate you all letting an old guy hang in your forum. I write test software for a living so I am interested in maybe getting to the point where I can start messing with my own software apps, etc.
I'm sorry if the question seems really dumb to all you bright young people, but I couldn't find anything about it on the search button.
Thanks for any info and help,
THEEDGE
Click to expand...
Click to collapse
Can i ask how u got v9 when i never released it? Lol
LOL..yeah sorry. I had Version .8 I guess and then my son upgraded me I guess to version .9 and I thought it was 9...sorry!
what should i do? haha
clintceastwood said:
what should i do? haha
Click to expand...
Click to collapse
Holy sh##, I wonder if thats what happened to mine then.... I had it for 3 hours, installed extended controls on it, turned the brightness all the way down and it died. Battery pull would get me the samsung screen but it would stop after the galaxy animation. I did a factory reset, still did it.
Is that about the same?
I figured that I just had a bad unit so I took it back to the store.
Edit. Just did a little research and we are not the only two this has happened to...not seeing a fix though...
If you have cwm installed or debug enabled you should just adb to your device and delete the offending widget app.
Sent from my SCH-I500 using XDA App
man, that sucks.
Happened to me too... If only we had the notification brightness slider the vibrant has. I had to take miner back too... Didn't know of cwm and I was smart enough to turn debugging mode off so no adb for me.
Sent from my SCH-I500 using XDA App
wizang said:
If you have cwm installed or debug enabled you should just adb to your device and delete the offending widget app.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
It persisted after a factory reset on mine. Offending app was all gone... Will be interesting to see if the op can get his working by doing that. Personally I just thought I had a bad phone.
thanks for the help guys put i adb pulled and it solved my problem ... i was freaking for a second
clintceastwood said:
thanks for the help guys put i adb pulled and it solved my problem ... i was freaking for a second
Click to expand...
Click to collapse
Awesome. Wonder why my factory reset didn't fix mine... Weird.
Bigger question... What do the application developers need to change too keep this from happening?
well the truth in my case is i downloaded a version off mediafire to see if i liked it before i donated and the thing was the version i downloaded had an error that to this day has been corrected. so if i wouldve just been legit from the beginning it wouldnt of happened
I always keep adb on after this lesson...
http://forum.xda-developers.com/showthread.php?t=785603&highlight=horror
clintceastwood said:
well the truth in my case is i downloaded a version off mediafire to see if i liked it before i donated and the thing was the version i downloaded had an error that to this day has been corrected. so if i wouldve just been legit from the beginning it wouldnt of happened
Click to expand...
Click to collapse
Extended trial eh? looked at extended controls change log, none on theirs yet. Guess I'll try power widget instead.
I was a victim of this as well with the extended controls widget. I emailed them and they didn't seem overly concerned, though to be fair there is a language barrier. I would have expected profuse apologies and a refund, at the very least.
I use the one called "Backlight!" but when I installed and saw the default value levels of 0,50,150,255 and saw a zero that instantly threw up a red flag. Before using widget I just edited the custom brightness levels to 34,65,103 which translates to 13%,25%,45%. Are there other devices where you could assign the toggle to a hard button? That's the only way I can see having a 0 default level on a device.
good day.
I submitted a ticket to the extended controls group and they just updated it after fixing the issue... Said it is now fixed and will be in the next release.
this has been posted in the forum, the phone still works, the display is just completely blacked out. 0% apparently meant different for the Samsung Fascinate phones than other Android phones. Power Control widget had updated their log a few days ago saying this was resolved in the last update here:
http://www.appbrain.com/app/power-control-plus-(widget)/com.siriusapplications.eclairwidgets
good thing the brand new version that i tried to pay for still blacked out my screen
Thank God I found this thread! Same here!! Power Strip. Was so depressed when I noticed I couldnt wake my screen back up after boot and locking it! Phew.... AWESOME PHONE!
Yea this happened to me as well and I didn't have de bugging on to use adb. Took it to the store they were like "we have never seem this happen before...sorry sure have this new one!" LoL
Sent from my rooted 1.2 voodoo Fascinate
Mine did it from a Ringer Profile app. I was trying to get my Fascinate to act more like a Blackberry in regards to notifications and such. All seemed well until I re3booted the phone. I went through 2 phones from this. The app did have functions for setting screen brightness for different profiles. Since I got that one solved, the phone's been great!
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？
Alright. Well. This is interesting.
I've fixed the original HTC touchscreen driver for use in ICS. I'm assuming it will work on other HTC phones as well, since the fix is FAR less intrusive in terms of changing existing code, or trying to port other drivers.
I was working on trying to map out the Samsung and HTC drivers in terms of data they let the system see as they are running. Getting no where fast, I remembered a couple days ago when I was attempting to get the touch keys working with the Samsung driver. Originally, I had added this code to the mxt224 driver above the line 'set_bit(EV_ABS, ts->input_dev->evbit);':
added to mxt224.c
Code:
set_bit(EV_SYN, ts->input_dev->evbit);
set_bit(EV_KEY, ts->input_dev->evbit);
set_bit(BTN_TOUCH, ts->input_dev->keybit);
set_bit(BTN_2, ts->input_dev->keybit);
I assumed this may have something to do with the softkeys, since it was present in the HTC driver with all four lines. By this I mean that in the HTC driver, that section looked like this:
atmel.c
Code:
set_bit(EV_SYN, ts->input_dev->evbit);
set_bit(EV_KEY, ts->input_dev->evbit);
set_bit(BTN_TOUCH, ts->input_dev->keybit);
set_bit(BTN_2, ts->input_dev->keybit);
set_bit(EV_ABS, ts->input_dev->evbit);
It worked fine in CM7 after doing this, but I lost all touchscreen in ICS, with it not even registering touch data anymore.
Back to my main point, I decided to see what would happen if I totally removed those four lines from the atmel.c file (HTC driver) and see what happens in ICS. Long story short, it works. Apparently ICS doesn't use or absolutely hates one or all four of those input preprocessors. So yeah I kinda **** bricks that it was that simple.
I'm going to try to see if its one or just all of these keybits that's causing the problem and I'll report back.
Instructions
If you want to try this, follow along:
Get rid of build settings for the Samsung driver if you've been messing with that
open up our favorite driver driver/input/touchscreen/atmel.c
CRTL+F, search for EV_SYN
Comment or delete all of the set_bit() lines except for the last one, EV_ABS
Your atmel.c should only have this line now, where all five were before:
Code:
set_bit(EV_ABS, ts->input_dev->evbit);
Clean your make environment and make sure your config files are set to use atmel-touchscreen
**** bricks
so it should look like:
Code:
ts->input_dev->name = "atmel-touchscreen";
// set_bit(EV_SYN, ts->input_dev->evbit);
// set_bit(EV_KEY, ts->input_dev->evbit);
// set_bit(BTN_TOUCH, ts->input_dev->keybit);
// set_bit(BTN_2, ts->input_dev->keybit);
set_bit(EV_ABS, ts->input_dev->evbit);
?
twistedumbrella said:
so it should look like:
Code:
ts->input_dev->name = "atmel-touchscreen";
// set_bit(EV_SYN, ts->input_dev->evbit);
// set_bit(EV_KEY, ts->input_dev->evbit);
// set_bit(BTN_TOUCH, ts->input_dev->keybit);
// set_bit(BTN_2, ts->input_dev->keybit);
set_bit(EV_ABS, ts->input_dev->evbit);
?
Click to expand...
Click to collapse
Yeah try that. I've run into something though, which must be something stupid I'm doing but I can't figure out what the hell it is.
I've gone through each of those that I commented out to see if it was just one of the set_bits that was making it not work. But even with them all on now it's still working in ICS. I've cleaned my builds between each time. I think I'm going crazy! Because it didn't work before!
swm5126 said:
Yeah try that. I've run into something though, which must be something stupid I'm doing but I can't figure out what the hell it is.
I've gone through each of those that I commented out to see if it was just one of the set_bits that was making it not work. But even with them all on now it's still working in ICS. I've cleaned my builds between each time. I think I'm going crazy! Because it didn't work before!
Click to expand...
Click to collapse
I'm building now and I will see what I can find out. It might be as simple as it forced the build to refresh in some way? Ill see what happens and let you know.
I'm already engaged, but I think she will understand... Will you marry me? haha, it worked!
And then I see this : http://android.modaco.com/topic/348194-04-nov-icl23d-galaxy-nexus-boot-recovery-system-dump/
Can you post the zip with it working? Please
w9jds said:
Can you post the zip with it working?
Click to expand...
Click to collapse
http://dl.dropbox.com/u/11023553/imoseyon_leanKernel_184Mhz_vAOSP.zip
That is the Thunderbolt version
swm5126, I cannot than you enough for all the help. I really wouldn't have gotten anywhere without it. Least we can toast to a success!
But I am still looking into what needs to be commented, just a little excited to actually touch ICS. lol.
twistedumbrella said:
I'm already engaged, but I think she will understand... Will you marry me? haha, it worked!
And then I see this : http://android.modaco.com/topic/348194-04-nov-icl23d-galaxy-nexus-boot-recovery-system-dump/
Click to expand...
Click to collapse
Unfortunately I'm engaged too, so no dice!
Can't wait to take a look at those
Quick question, does your pointer in ICS seem to go back up to the top left hand corner of the screen? Or aren't you in pointer mode?
for me it does!!
but I still can't unlock the F screen...
LorD ClockaN said:
for me it does!!
but I still can't unlock the F screen...
Click to expand...
Click to collapse
Awesome! Glad I'm not crazy and this works. They must have deprecated some of the input preprocessors. I'm just surprised using them in the driver basically made the touchscreen inoperable in ICS.
One step closer...to something! Now to figure out those pesky idc files to get this to work without the pointers.
maybe better to focus on Paul's dump.. could be different regarding TS
My post for the stuff inside the new idc configurations system is here http://forum.xda-developers.com/showthread.php?t=1320170&page=16
hope it helps
swm5126 said:
Awesome! Glad I'm not crazy and this works. They must have deprecated some of the input preprocessors. I'm just surprised using them in the driver basically made the touchscreen inoperable in ICS.
One step closer...to something! Now to figure out those pesky idc files to get this to work without the pointers.
Click to expand...
Click to collapse
It reverts to the corner. I am working on a fix for that right now. Congrats, btw.
w9jds said:
My post for the stuff inside the new idc configurations system is here http://forum.xda-developers.com/showthread.php?t=1320170&page=16
hope it helps
Click to expand...
Click to collapse
What he said, lol
Sent from my ADR6400L using Tapatalk
LorD ClockaN said:
maybe better to focus on Paul's dump.. could be different regarding TS
Click to expand...
Click to collapse
Trying to haha filesonic is only letting me get one file at a time *sigh*
I already downloaded those.. I have a paid acount for filesonic
I posted this in DHD thread also:
my Touchscreen works, but it doesn't unlock anything... I mean, I pull the ring to unlock icon, it vibrates and it doesn't change screen..
so I unlock screen with adb shell, and when it gets unlocked I'm welcomed with SystemUi FC.. and every time like that.. if I turn off screen and back ON after trying to unlock screen, my touches are not working.. it must be because systemui already crashed... but it doesn't show it..
LorD ClockaN said:
I already downloaded those.. I have a paid acount for filesonic
I posted this in DHD thread also:
my Touchscreen works, but it doesn't unlock anything... I mean, I pull the ring to unlock icon, it vibrates and it doesn't change screen..
so I unlock screen with adb shell, and when it gets unlocked I'm welcomed with SystemUi FC.. and every time like that.. if I turn off screen and back ON after trying to unlock screen, my touches are not working.. it must be because systemui already crashed... but it doesn't show it..
Click to expand...
Click to collapse
With the fix from here for the driver? Or without anything?
with your fix here
Awesome! Now if only I could find someone to reverse engineer the 3D camera and Gallery for the HTC Evo 3D, I would be fat from all the Ice Cream Goodness I would be devouring! Good job guys
I got money for whomever gets a decent working (radio, touch screen, texts) ICS DINC build by the end of this weekend.....
wetbo529 said:
I got money for whomever gets a decent working (radio, touch screen, texts) ICS DINC build by the end of this weekend.....
Click to expand...
Click to collapse
Can we not do that? That's how things get sloppy. Just donate it to swm, he deserves it.
Sent from my ADR6400L using Tapatalk
Hello,
I am writing this to help other newbies who may want to switch to Cyanogen for the first time on their Epic 4G. There were a few things I needed to do after to get everything working the way I liked and I figure this will save some people time.
What do I need to do prior?
There are many how-to's which will help but I had my Epic stock rom rooted so it was as simple as flashing cyanogen through recovery. Here is the link for a "how-to" root the stock rom if you wish to do it this way. It was the easiest way for me though the official guide says "Rooting the stock firmware is neither recommended nor necessary."
http://www.youtube.com/watch?v=C9eaCtiS0Bo
Where do I get Cyanogen?:
You can download it here. I am running the 10.0.0 stable build.
http://wiki.cyanogenmod.org/w/Epicmtd_Info
I have no google apps:
This is a problem with any Cyanogen installation. Easy fix, download & install the gaaps package from the link below and your marketplace will be back.
http://goo.im/gapps
I don’t have Navigation:
Easy fix again, download the google maps app. Here is the app store link.
https://play.google.com/store/apps/...DMsImNvbS5nb29nbGUuYW5kcm9pZC5hcHBzLm1hcHMiXQ..
I don’t have voicemail:
While you can use any voicemail app I wanted the one I had on the stock rom. I linked the app below and your voicemail will be back as soon as you install it. You need to open the app after so that it will activate.
https://od.lk/d/MjRfMjc2MDY5MF8/vtt-sprint.apk
I am getting texts from 9016 every time I get a voicemail:
From reading it seems the stock rom blocks us from seeing these but they are in fact needed for voicemail to work. To fix this I used a free app called “RedList”. Simply add 9016 to the RedList within the app, change the settings to disable both notifications, and this will problem will be solved. Here is the app store link.
https://play.google.com/store/apps/...=W251bGwsMSwxLDEsImNvbS5saW5ub3IuUmVkTGlzdCJd
Text messages no longer have separate colors for me and my recipient:
The stock android text display is white and I hated this after getting used to Samsung’s nice colors but luckily you can solve this in two ways.
(One) A theme manager is built into the interface section of your settings page. After searching through almost every free CM10 theme I found this one I liked. It does NOT touch too many things only adding a brushed metal look and displaying text messages how I wanted them. There are a few colors to choose from but I went with Blue.
http://forum.xda-developers.com/showthread.php?t=1992980
(Two) Replace only the MMS app with one that is color coded. Please note that unlike the above, to reverse this down the road you will need to find a stock mms app package with an installer. This is good for people who are sure they want this and only wish to change the colors of the messenger, while the above is good for people who like to switch themes often being able to revert back at any second. Link for the colored mms app.
http://www.mediafire.com/?hcjukwwkj4y41h3
Morror: https://od.lk/f/MjRfMjc2MDY5MV8
Facebook pictures no longer sync with my existing contacts:
This is a small problem, but still one that I got used to having with the stock rom and wanted to correct. From reading this seems to be a problem related to later Android versions, not just Cyanogen. The fix for this is easy as well, search out a free app called “UberSync for Facebook”. I had the regular facebook app installed & logged in prior and UberSync logged right in, got the pictures, and updated my contacts.
https://play.google.com/store/apps/...wsMSwxLDEsInJvLndlZWRuZXQuY29udGFjdHNzeW5jIl0.
I no longer have Swype:
Despite having the nice physical keyboard (the whole reason I got the Epic) I still got used to using Swype here or there. I don't think I will be allowed to link this file here but you can find it on "certain" sites.
Notes:
Despite reports that Bluetooth can be problematic, I use it daily with an earpiece and have yet to experience any issues. GPS & 4G also work great. If any links are broken send me a PM! I check my email daily.
Get rid of the dropbox download links. Those are absolutely horrible when posting a guide for others to use.
nikon120 said:
Get rid of the dropbox download links. Those are absolutely horrible when posting a guide for others to use.
Click to expand...
Click to collapse
Why are they so bad? The bring you right to the download and I won't be deleting these files from my dropbox. Much better IMO than dealing with one of those sites where you have to wait 45 seconds for a download link to appear in a sea of other spam download buttons.
protivakid said:
Why are they so bad? The bring you right to the download and I won't be deleting these files from my dropbox. Much better IMO than dealing with one of those sites where you have to wait 45 seconds for a download link to appear in a sea of other spam download buttons.
Click to expand...
Click to collapse
Well...
No MD5/SHA1 to compare against to make sure you have a complete download.
People's dropbox tends to get too much traffic and the link becomes dead.
You basically cut out the original author(s) of the file.
Based off # 3: They could need the ad revenue, and/or want to track download activity if they're self-hosting.
nikon120 said:
Well...
No MD5/SHA1 to compare against to make sure you have a complete download.
People's dropbox tends to get too much traffic and the link becomes dead.
You basically cut out the original author(s) of the file.
Based off # 3: They could need the ad revenue, and/or want to track download activity if they're self-hosting.
Click to expand...
Click to collapse
I know this isn't directed at me, but the things I have on my box account are older things( Samsung Moment update tool), things I've done for myself, or things that I've found for other people. In other words, things many people don't care about.
Sent from my SPH-D700 using Tapatalk 2
nikon120 said:
Well...
No MD5/SHA1 to compare against to make sure you have a complete download.
People's dropbox tends to get too much traffic and the link becomes dead.
You basically cut out the original author(s) of the file.
Based off # 3: They could need the ad revenue, and/or want to track download activity if they're self-hosting.
Click to expand...
Click to collapse
#1 - I think more people are concerned with a working link, if they download the archive after and it somehow gets corrupted i'm sure they will just try again
#2 - Valid point though my files don't have a great enough of demand to warrant this. If this changes I will change my links.
#3 The only thing that wasn't mine with a dropbox link was the MMS app and I only mirrored it in case the original link were ever taken down. If it will make you happy I can include the original link as well. For the voice mail app, its simply the sprint one ripped from a stock rom.
Though your points are valid, I think you are sort of just being picky bud
Thanks for the VM download link. Only thing I want is task manager which I had installed on CM9. Is there stockish one that works for 10?
Try the flashable one from here
http://forum.xda-developers.com/showthread.php?t=1452004
Sent from my SPH-D700 using Tapatalk 2
swype
I reinstalled swype 3 or 4 times with various upgrades and it would always "expire" and I'd have to figure out how to get it working again. I am running 10.1 RC5 now and it has a decent generic swype-ish virtual keyboard. The thing missing is that you can't finish your text and go back and fix any misspelled words by touching alternate suggestions. You have to catch them as they come up. It seems like at first I could still do that, but I can't figure out how to get the suggestions to come back up.
I'm over swype.
Just flashed CyanogenMod 10.1... is there any built in overclocking?
I installed SetCPU and it won't step above 1000 MHz.
Kernel
Steelcitymetal said:
Just flashed CyanogenMod 10.1... is there any built in overclocking?
I installed SetCPU and it won't step above 1000 MHz.
Click to expand...
Click to collapse
You need a different Kernel. I have been using didy's kernel for a while. You flash CM10.1 and then you flash the kernel. CM10.1 has its own kernel that overwrites what you flash. So when you update, i think you have to reflash the kernel. I haven't screwed around with it since I installed rc5. I think I did CM, then the kernel, then the big mem patch. I never was able to figure out how to update the radio. I always ended up with "no voice service" or worse.
There is a thread in the developer forum that has the links to the kernel downloads. I am running one from may 30 and haven't updated.
boocephus said:
You need a different Kernel. I have been using didy's kernel for a while. You flash CM10.1 and then you flash the kernel. CM10.1 has its own kernel that overwrites what you flash. So when you update, i think you have to reflash the kernel. I haven't screwed around with it since I installed rc5. I think I did CM, then the kernel, then the big mem patch. I never was able to figure out how to update the radio. I always ended up with "no voice service" or worse.
There is a thread in the developer forum that has the links to the kernel downloads. I am running one from may 30 and haven't updated.
Click to expand...
Click to collapse
I think I found it... Is didy the same as didhiy?
[KERNEL][CM10.1]Nitest Kernel for Crespo4G/Epic4G Modem with Voodoo Sound&Color
When you say you couldn't update the radio, you just mean the cell service radio, right? Not wifi? I don't have cell service on my Epic, so that wouldn't be a problem for me... just as long as the wifi radio still works
Also, what specifically do you mean by "or worse"?
Steelcitymetal said:
I think I found it... Is didy the same as didhiy?
[KERNEL][CM10.1]Nitest Kernel for Crespo4G/Epic4G Modem with Voodoo Sound&Color
When you say you couldn't update the radio, you just mean the cell service radio, right? Not wifi? I don't have cell service on my Epic, so that wouldn't be a problem for me... just as long as the wifi radio still works
Also, what specifically do you mean by "or worse"?
Click to expand...
Click to collapse
Yeah. That's the one. I looked at my about phone and it said "didy".
I saw a thread about the nexus radio being hot **** and I fooled around with it. I got either "no voice service" or no nuthin. I was able to flash back to the regular epic radio. there is another thread that had all the flashable zips with different modems. luckily the epic one undid my stupidity - at least on my phone.
boocephus said:
Yeah. That's the one. I looked at my about phone and it said "didy".
I saw a thread about the nexus radio being hot **** and I fooled around with it. I got either "no voice service" or no nuthin. I was able to flash back to the regular epic radio. there is another thread that had all the flashable zips with different modems. luckily the epic one undid my stupidity - at least on my phone.
Click to expand...
Click to collapse
Thanks man, I'll give it a shot. CM10.1 is running pretty smoothly on my phone, but it could be better and battery life is not an issue for me.
I'll be sure to run backups before I do though :good:
Thanks
These tips helped - I just made the jump to CM 10.1, and although there are a few quirks it has been great. Your list really helped.
FYI, one thing I ran into was the auto-rotate didn't work. I followed the directions here:
http://epiccm.blogspot.com/2012/01/boot-el30-stock-from-sdcard.html
the first time, there was no change. I tried again (and calibrated like 6 times) and it worked.
Has anyone noticed the physical keyboard doesn't always work the same? In some places, you have to hold down shift or Fn while pressing the key you want (for example - hold shift while pressing A, rather then pressing shift then pressing A). It's not consistent - some inputs work like the keyboard did before. Does anyone have any suggestions how to fix this. Not the worst thing (I'm just glad I still have a physical keyboard), but I would prefer it work the way it did before, or if that's not possible, at least be consistent.
And the smiley face button on the physical keyboard doesn't work either. I mean, it's like 2005 where I have to type out my 's!!
any phantom voicemail fix?
phantom voicemails?
TheSkipperCDB said:
Has anyone noticed the physical keyboard doesn't always work the same? In some places, you have to hold down shift or Fn while pressing the key you want (for example - hold shift while pressing A, rather then pressing shift then pressing A). It's not consistent - some inputs work like the keyboard did before. Does anyone have any suggestions how to fix this. Not the worst thing (I'm just glad I still have a physical keyboard), but I would prefer it work the way it did before, or if that's not possible, at least be consistent.
Click to expand...
Click to collapse
I have noticed that the physical keyboard doesn't work right in the browser. Shift and Fn don't seem to work. I am usually in such a hurry that I just close it up and use the virtual keyboard if I want to have punctuation. It honestly didn't occur to me that it might be fixed. I can't offer that fix. I am just offering emotional support and validation.:good:
boocephus said:
I have noticed that the physical keyboard doesn't work right in the browser. Shift and Fn don't seem to work. I am usually in such a hurry that I just close it up and use the virtual keyboard if I want to have punctuation. It honestly didn't occur to me that it might be fixed. I can't offer that fix. I am just offering emotional support and validation.:good:
Click to expand...
Click to collapse
I noticed that the default browser you have to hold the shift or fn key while pressing the desired key to get it to work. Apps and os seem to work with a tap od these keys and then a hit of the desired key.I recall a while back a thread about the smiley and since it was not a default key the consensus was that they would not be adding the functionality to cm. While on the topic...same goes with the .com function.
Sent from my SPH-D700 using xda app-developers app
I'm sorry i want to ask, how we modify system setting look in CM? Thank you..