A few of you have been asking for a howto guide on improving the performance on your devices, and I have listened!
I have made for you all a video guide on how to get your 7.7 flying!
Enjoy!
Galaxy Tab 7.7 Speed Tweaks ADW EX [ROOT]
Thanks, some nice stuff in there, even if a lot of it is really a ADW.EX tutorial.
Just fyi, you have a typo in the video description--you say ADX EX launcher.
About Customize Menu--you can reorder (or remove theoretically, but this was buggy for me) the items that appear on the top bar and in the drop-down when you push the menu button. I use this so that I can have Add in the menu, because I keep the top bar hidden and there is no other easy access to add/remove/move home screen pages.
teiglin said:
Thanks, some nice stuff in there, even if a lot of it is really a ADW.EX tutorial.
Just fyi, you have a typo in the video description--you say ADX EX launcher.
Click to expand...
Click to collapse
Not bad for a single take and no editing though lol!
how did you set up you dolphin for tab browser to have the 4d scrolling between tabs
adinis78 said:
how did you set up you dolphin for tab browser to have the 4d scrolling between tabs
Click to expand...
Click to collapse
It's a native function of the Dolphin for Pad Beta v1.0
Jade Eyed Wolf said:
It's a native function of the Dolphin for Pad Beta v1.0
Click to expand...
Click to collapse
hmmm can seem to get mine to due it
EDIT: got it i saw the video again, i wasnt using the two finger tap
adinis78 said:
hmmm can seem to get mine to due it
Click to expand...
Click to collapse
Two finger tap on the edge of the web page?
Jade Eyed Wolf said:
Two finger tap on the edge of the web page?
Click to expand...
Click to collapse
Yep
Sent from my SGH-T959 using XDA App
Thanks for the hardwork on this tutorial on what your settings are and also I've seen a better view of your screen which apparently confirms my findings from your other video.
EDIT:
The ro.HOME_APP_ADJ=0 tweak really does wonders!
Thanks alot J.W. very nice job! & thanks for stepping up when all of us asked you to!!!!
EarlZ said:
Thanks for the hardwork on this tutorial on what your settings are and also I've seen a better view of your screen which apparently confirms my findings from your other video.
EDIT:
The ro.HOME_APP_ADJ=0 tweak really does wonders!
Click to expand...
Click to collapse
I have to try this when I get home, the homescreen redraw drives me nuts, and its completely unecessary imo!
EDIT - OMGGGGGGGGG finally, the tablet has no effing homescreen redraw lag, thank you Jade Eyed Wolf!
Oh, oh. Just did this and now the tablet won't start!!!! I just get the initial "galaxy tablet 7.7" screen and then it stays black....
Any ideas? The only thing I changed was this
"Add this line to "/system/build.prop":
ro.HOME_APP_ADJ=0"
Help!!!!!
can someone post a copy of their build.prop (6810)? Would that help?
I can get into recovery, but rebooting form there doesn't do anything.....
Anyone with any bright ideas?
I can get into recovery, but I can't connect to the device via the pc to get at the files. well, that isn't quite true, I can see them if I use a pgr called DROIDEXPLORER, I can copy from the device to the PC but not back the other way. So I tried to edit the build.prop locally and push it back (using droidexplorer) but the one on the device just stays the same with the edit above in it...
I'm now considering flashing a new FW as the only way to get the tab going again.
Any help?
followed instructions and still couldn't write to sd card with ES File Explorer. Can't tell with homepage redraw... What's bad is that this killed my internet connection. After rebooting, the status bar shows me connected to either my home wifi or my H+ service provider but I can't access the internet nor my local network... Restarting the 7.7, deleting the relevant lines, restarting my router/cable modem (still have internet on my main comp and ipad) all didn't help.
I guess I have to reflash my 7.7.
OK, so after a sleepless night (the little one was on full song) I reflashed my Tab this morning and way hey! It is back in the land of the living.
Pheww.
Jade, I think the hack to keep the homescreen in memory might need to be revisited? I followed the instructions to the letter. After applying the hack the device just would not come to life. It wasn't a case of screen-off, device on either. I plugged it in to a PC and there was nothing. The only way I could get the PC to see it was to start it in recovery.
Maybe it is just a combination of things on my machine and I guess these things can just happen, but I think it might be worth checking?
I'm totally happy with flashing now though
Just thought this could use a bump since it was so helpful to me.
daigled said:
Just thought this could use a bump since it was so helpful to me.
Click to expand...
Click to collapse
Thanks!
palexr said:
OK, so after a sleepless night (the little one was on full song) I reflashed my Tab this morning and way hey! It is back in the land of the living.
Pheww.
Jade, I think the hack to keep the homescreen in memory might need to be revisited? I followed the instructions to the letter. After applying the hack the device just would not come to life. It wasn't a case of screen-off, device on either. I plugged it in to a PC and there was nothing. The only way I could get the PC to see it was to start it in recovery.
Maybe it is just a combination of things on my machine and I guess these things can just happen, but I think it might be worth checking?
I'm totally happy with flashing now though
Click to expand...
Click to collapse
It worked for me (Galaxy Tab 7.7 wifi) so you probably entered something wrong... Actually I realised that after entering "ro." the keyboard inserted a space after the dot, so it looked like this: ro. HOME_APP_ADJ=0 and it is like this: ro.HOME_APP_ADJ=0 see the difference?
I realised right away and fixed it. If I were you I would try it again....
It works for me alright, I don't know if at the end uses too much ram and slows down other things, if it does I'll just delete that line and that's it....
Thanks to Jade W. good idea...
Dusko75 said:
It worked for me (Galaxy Tab 7.7 wifi) so you probably entered something wrong... Actually I realised that after entering "ro." the keyboard inserted a space after the dot, so it looked like this: ro. HOME_APP_ADJ=0 and it is like this: ro.HOME_APP_ADJ=0 see the difference?
I realised right away and fixed it. If I were you I would try it again....
It works for me alright, I don't know if at the end uses too much ram and slows down other things, if it does I'll just delete that line and that's it....
Thanks to Jade W. good idea...
Click to expand...
Click to collapse
Nope, just tried it again, result dead tablet... My tablet definitely does not like this line in build.prop
So, I would advise caution with this line. Take a backup before trying it or get comfortable with reflashing.
palexr said:
Nope, just tried it again, result dead tablet... My tablet definitely does not like this line in build.prop
So, I would advise caution with this line. Take a backup before trying it or get comfortable with reflashing.
Click to expand...
Click to collapse
HAs anyone got any bright ideas about pushing the original build.prop file back? ADB push just gives me "failed to copy 'build.prop' to '/system/build.prop': Read Only File
I'd rather just get the correct one in there than re-flash...
Related
Found This sweet Tutorial to get full screen apps like Engadet app!
You've probably noticed that there are apps that don’t scale to full screen. Thankfully the guys at jkkmobile.com have some instructions (video tutorial below) on how to enjoy your favorite apps that aren't yet optimized for Samsung’s Galaxy Tab 7-inch screen in full screen mode.
Here is a summary of the steps outlined in the video. Watch it if you still have questions.
Grab the “Spare Parts” app from the Android Market and install it.
Start the “Spare Parts” app and scroll down to “Compability Mode”. de-select the box and re-select it. Restart your tablet.
Start the “Spare Parts” again, go down to “Compatibility Mode” and de-select the box. Restart your tablet.
Good luck, your smaller apps should now be scaled to full-screen!
http://www.youtube.com/watch?v=zasSIA7sexM&feature=player_embedded#at=16
The tutorial is wrong.
All you have to do is untick compatibility mode and reboot. Voila -most things will now run fullscreen.
thats what I put !!DE-SELECT!!
zerolimit1 said:
You've probably noticed that there are apps that don’t scale to full screen. Thankfully the guys at jkkmobile.com have some instructions (video tutorial below) on how to enjoy your favorite apps that aren't yet optimized for Samsung’s Galaxy Tab 7-inch screen in full screen mode.
Click to expand...
Click to collapse
Not exactly new news! Most of us have been aware of this for as long as the Tab's been out!
Regards,
Dave
foxmeister said:
Not exactly new news! Most of us have been aware of this for as long as the Tab's been out!
Regards,
Dave
Click to expand...
Click to collapse
In Fairness i didnt know, so cheers mate have a thanks on me
thought everyone knew this by now
Someone else showed me how to do this... the only problem I have is some applications that now fit the screen look... odd. Oh well, it does what it's suppose to do though.
I didn't know about this =)
so i thought i would help new comes like me. But for some reason some apps still dont go full screen. Like WSP is not full screen and Dinner Dash 2 is not full screen! But almost everything else is good to go!
Thank you! I did not know about this either. Works great!
zerolimit1 said:
I didn't know about this =)
so i thought i would help new comes like me. But for some reason some apps still dont go full screen. Like WSP is not full screen and Dinner Dash 2 is not full screen! But almost everything else is good to go!
Click to expand...
Click to collapse
Games are more likely not to scale as they cos be coded natively.
Can I suggest that anyone who didn't know about this and is reading this thread, goes away and reads the "Galaxy Tab Bible" thread here as you may find lots of other bits of useful information (including this tip!) that you weren't aware of!
Regards,
Dave
Hi
I am using IGO GPS after i install the "Spare Parts" app the map still same cannot get full screen so anyone can help? thanks alot
zerolimit1 said:
thats what I put !!DE-SELECT!!
Click to expand...
Click to collapse
What i mean is that you only have to reboot once!
thanks for the information, trying it right now.
Great device!
Anybody managed to get the Quick controls from the "Lab" settings to work in the stock browser. It seems there are some problems with this feauture on the gal tab.
Also, are there any international versions out there yet? Mine only support UK/US English and Spanish. Samsung Netherlands "promised " that there will be an update. Wonder if there are roms floating around that have international support yet.
Nope. I wriggled my way back into the settings (I think through bookmarks) and disabled it after it nukes my address bar and tabs.
alumine said:
Nope. I wriggled my way back into the settings (I think through bookmarks) and disabled it after it nukes my address bar and tabs.
Click to expand...
Click to collapse
Pretty big omission. Will see if I can get the browser of the Xoom system dump to work. Btw there may be some interesting other goodies in this dump. The dump is posted in the Xoom development forum.
Update: I've just got it to work. There's a trick to it: you've got to slide 1 finger from the frame onto the screen.
Got this from:
Prjctmobile.com
alumine said:
Update: I've just got it to work. There's a trick to it: you've got to slide 1 finger from the frame onto the screen.
Got this from:
Prjctmobile.com
Click to expand...
Click to collapse
Yes I'm familiar with it. I used it on the Xoom. But it doesn't seem to work on my Tab.
Umm.. weird. But try this anyway: I've got it to work once I got into debug mode. I'm pretty sure it didn't work before. So try it out, who knows.
appelflap said:
Yes I'm familiar with it. I used it on the Xoom. But it doesn't seem to work on my Tab.
Click to expand...
Click to collapse
Can't get it to work either...frustrating
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..
Let me elaborate:
So earlier today I was messing around with Density Changer while going to Kingsville to see my brother. I was messing around with the DPI value, changing it from 480 to 420 and such. I changed it to 520 and, like normal, asked me to reboot. I rebooted.
The phone started up a lot longer than usual. I thought that this was just a simple glitch, but it took longer for a reason. The time and date on my lock screen wasn't working. Messaging, Contacts, Camera, Samsung keyboard, and the sort wasn't working. Worst of all, TouchWiz wasn't working either. In panic, I tried to open Density Changer from settings but couldn't. I reset my phone to the factory settings. It was rather quick to format (I didn't have much except for some PSP roms and gallery images). I was relieved for a bit, but when it booted it was still unfunctional, not to mention the keyboard still didn't work, so I had to skip a ton of steps. Since TouchWiz was still broken, I set the home screen to Easy Mode. When I looked around with Easy Mode, I realized that you can run apps there without it crashing. I felt so dumb. So now I can't log in to the Play Store to undo what I did, I don't have the app anymore, TouchWiz won't work, I don't even know if I can recieve messages, yada yada. I feel like I am so screwed.
TL;DR changed the DPI from 480 to 520, all hell went loose. did factory reset in panic, even more screw.
Does anyone know what I can do instead of sending it for repair? I don't think AT&T will be able to repair it anyways-- just to give me a new phone.
Try download the last official att rom and use odin. You can find it here in XDA forum. Good luck
Sent from my SGH-I337M using XDA Premium 4 mobile app
wawis said:
Try download the last official att rom and use odin. You can find it here in XDA forum. Good luck
Sent from my SGH-I337M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I appreciate that you want to help! It means a lot. But before I attempt this, does this change absolutely EVERYTHING to default? I think the reason why my phone got so messed up was because the DPI was too high. :/
Do you know what firmware you're on? And if you have a custom recovery did you make a nandroid before you started messing around? If you did, like you should have, just restore that.
Dabreaker9 said:
I appreciate that you want to help! It means a lot. But before I attempt this, does this change absolutely EVERYTHING to default? I think the reason why my phone got so messed up was because the DPI was too high. :/
Click to expand...
Click to collapse
MAKE SURE YOUR NOT ON THE MF3 UPDATE. IF YOU ARE DO NOT ATTEMPT.
If your running MDL or lower, then download the MDL package and flash it with odin. It will indeed make everything stock.
MDL Package
http://www.androidfilehost.com/?fid=23134718111253756
Odin
http://www.androidfilehost.com/?fid=23134718111253763
1. Place phone in download mode
2. Hook to computer via USB
3. Open Odin
4. Click the PDA button and place the MDL file you just downloaded there.
5. Click start.
The process will take a few minutes, so don't panic. Let me know if that fixed it.
Shoot, man. I'm on the MF3 update. I have root though, will that help with fixing it?
jd1639 said:
Do you know what firmware you're on? And if you have a custom recovery did you make a nandroid before you started messing around? If you did, like you should have, just restore that.
Click to expand...
Click to collapse
I'm on the MF3 firmware. I didn't make any custom recovery file things.
Dabreaker9 said:
I'm on the MF3 firmware. I didn't make any custom recovery file things.
Click to expand...
Click to collapse
Go to a Best Buy that has a Samsung Experience booth and see if they will restore factory MF3 for you. Then, I suggest you don't do ANYTHING to your phone but use it for calls and stock abilities.
it really amazes me just how many people in the past few days have screwed up their phones, and the ONLY reason is because they didn't read
deadenz said:
it really amazes me just how many people in the past few days have screwed up their phones, and the ONLY reason is because they didn't read
Click to expand...
Click to collapse
Yep, the more popular the phone, the more people that get a hold of it that shouldn't be doing anything with it except making calls. Laziness and ignorance will create a brick every time. The truly funny part is how quick they run here to make a post for people to fix their screw-ups, but they wouldn't come here to take a little time and effort to learn and read about what to do and how to do it in the first place.
deadenz said:
it really amazes me just how many people in the past few days have screwed up their phones, and the ONLY reason is because they didn't read
Click to expand...
Click to collapse
Hey, now. I almost have it fixed. I just need the .apk file for Density Changer so I can install it, paste "480" into the box and reboot. Would someone be so kind to do it for me? This laptop is a school laptop which has Fortinet as an antivirus and a website restrictor. I would do it myself but my parents are considering taking me to AT&T ASAP when I go back home tomorrow.
But, yeah. I should have read on. I know that bigger values made the screen smaller, but I guess the S4 goes crazy when that happens.
Dabreaker9 said:
Let me elaborate:
So earlier today I was messing around with Density Changer while going to Kingsville to see my brother. I was messing around with the DPI value, changing it from 480 to 420 and such. I changed it to 520 and, like normal, asked me to reboot. I rebooted.
The phone started up a lot longer than usual. I thought that this was just a simple glitch, but it took longer for a reason. The time and date on my lock screen wasn't working. Messaging, Contacts, Camera, Samsung keyboard, and the sort wasn't working. Worst of all, TouchWiz wasn't working either. In panic, I tried to open Density Changer from settings but couldn't. I reset my phone to the factory settings. It was rather quick to format (I didn't have much except for some PSP roms and gallery images). I was relieved for a bit, but when it booted it was still unfunctional, not to mention the keyboard still didn't work, so I had to skip a ton of steps. Since TouchWiz was still broken, I set the home screen to Easy Mode. When I looked around with Easy Mode, I realized that you can run apps there without it crashing. I felt so dumb. So now I can't log in to the Play Store to undo what I did, I don't have the app anymore, TouchWiz won't work, I don't even know if I can recieve messages, yada yada. I feel like I am so screwed.
TL;DR changed the DPI from 480 to 520, all hell went loose. did factory reset in panic, even more screw.
Does anyone know what I can do instead of sending it for repair? I don't think AT&T will be able to repair it anyways-- just to give me a new phone.
Click to expand...
Click to collapse
You can try using a root level file explorer to navigate to /system, long press build.prop to open with a text editor, find the following line and change it to 480, then reboot. Root Explorer or ES File Explorer will do what you need.
ro.sf.lcd_density=480
upndwn4par said:
You can try using a root level file explorer to navigate to /system, long press build.prop to open with a text editor, find the following line and change it to 480, then reboot. Root Explorer or ES File Explorer will do what you need.
ro.sf.lcd_density=480
Click to expand...
Click to collapse
Keyboard doesn't work. I was almost going to do that until I realized it. I'm just looking around for any DPI changing applications that allow it to any number (LCD Density Changer only allows it to 280).
I would set it to 280 if I could handle the small-ass icons. I can't, so I'm not gonna bother with that.
scott14719 said:
Yep, the more popular the phone, the more people that get a hold of it that shouldn't be doing anything with it except making calls. Laziness and ignorance will create a brick every time. The truly funny part is how quick they run here to make a post for people to fix their screw-ups, but they wouldn't come here to take a little time and effort to learn and read about what to do and how to do it in the first place.
Click to expand...
Click to collapse
God damn, man. You say it like you've never messed up something on your phone before. I know, I'm a **** for not reading if it was safe, but I'm almost positive you've messed up one way or another before?
Dabreaker9 said:
Keyboard doesn't work. I was almost going to do that until I realized it. I'm just looking around for any DPI changing applications that allow it to any number (LCD Density Changer only allows it to 280).
I would set it to 280 if I could handle the small-ass icons. I can't, so I'm not gonna bother with that.
Click to expand...
Click to collapse
Ooops. missed the keyboard part.
What ROM are you running? Stock MF3?
upndwn4par said:
Ooops. missed the keyboard part.
What ROM are you running? Stock MF3?
Click to expand...
Click to collapse
The default MF3, yeah. Fixed it with www-57.zip-pysha-re.co-m/v/78538033/file.html (remove those dashes). I went on Google Chrome and used voice recognition to get 460, pasted it in the DPI box, applied it. Everything's good now.
Dabreaker9 said:
God damn, man. You say it like you've never messed up something on your phone before. I know, I'm a **** for not reading if it was safe, but I'm almost positive you've messed up one way or another before?
Click to expand...
Click to collapse
Umm... Yeah Scott is a little grumpy when he sees things over and over again lol. I'm glad you were able to get it fixed.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Dabreaker9 said:
God damn, man. You say it like you've never messed up something on your phone before. I know, I'm a **** for not reading if it was safe, but I'm almost positive you've messed up one way or another before?
Click to expand...
Click to collapse
Well, it's really not about messing up. What is done is done. It's about learning from it and not doing it again. I can tell you are on the right path because you are trying to fix it. You screwed up... a lot of people screw up...what is important is not doing it again. Always read as much as you can about anything before you try it. It's just a phone and it is always replaceable but you can save yourself a lot of trouble by reading before doing. Like I said, i think you realize that. I'm sure you don't want to go through this type of trouble again to just get the phone working. What you did (change the dpi) isn't a big deal but it has big consequences. I was mostly referring to people that that try to "root", put custom recoveries on their phones, custom ROMs, etc. There is so much information about these things in the XDA forums it isn't funny, yet people think they don't need to read and learn about it or they think their time is too valuable. But as soon as they screw up (and they always do), all of the sudden, they find the time to come to XDA and beg for someone to fix their phone. As soon as someone points out that they should have read and learned in the first place, they get a smug attitude and act like people "owe" them a fix for their stupidity. Like I said, not necessarily your situation, but it happens all of the time regardless.
**Edit**
I'm am glad you fixed your phone and is is encouraging to see how much work and effort you put into fixing it. It would be nice if everyone put that kind of effort into fixing their phones. I have a feeling you will do just fine with modifying your phone.