• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] CTMod 3.80 (04/06/13)

when you go to samsung phone site and type in the model # (sph-m840) it calls it the rush2.... just so others know.... not sure if there are posts about the rush2 or not i havent searched it lol
Somewhere else it's called something else as well I forgot the name. But that was what I was hinting at to many names for the same phone
 
There's a device tree name given by CM. Then there's the build name given by manufacturer. Then sometimes there's a remake of the device. Aka prevail2. They all have a reason for existing. ;)
 
rush2/ prevail2/ ring ..... those are the 3 i know of... :)

Ring thats it . thank u Desilynn I'm guessing why this is ? because you have maker of phone then providers each offer their own branded apps n logos to help tell them apart from provider to provider to help tell them apart? Example in my opinion would be say we both had same phones makers but if u told me galaxy 2 ring then I would assume that u was on virgin mobile. N if I said I was galaxy 2 prevail then one could assume I was on boost mobile and galaxy 2 rush would be t mobile or Verizon. I'm just askng if I'm correct.
 
i think so but i always root mine so im running virgin mobile modified stock rom on my boost mobile lol as i have soft bricked etc this phone while playing around :D
me and hubby have talked about an upgrade for me and i will probably go to the s4... and of course root and custom rom and kernel it etc
i use very little of what comes stock on the phones so i remove nearly all if not all that isnt required for the phone to operate;)
 
Noooooooooooooooo! Whatever you do.. don't get a triband device. I'm ready to throw this at a wall. Hope you can get an older s4. The triband s4 has a 'T's at the end of the model #. Spark is the worst system for data sharing ever.. Lol. No chance (from what I understand) to receive any kinda svlte or svdo. Sprint publicly said it's over their heads and they're not trying.
Someone please say I'm wrong.
 
There's a device tree name given by CM. Then there's the build name given by manufacturer. Then sometimes there's a remake of the device. Aka prevail2. They all have a reason for existing. ;)

Example: My Phone is the 'new' S4 from Sprint. Samsung named it L720.
Okay.. now. Cyanogenmod picked it up. And slapped their device tree name on it. Jfltespr.

After awhile (atleast Sprint) a new one has come out. Almost identical in hardware. Named L720t. This 't' stands for triband. Triband runs 3 lte signals simultaneously between 800mhz and the 2500mhz range. In order to make this happen.. all sprint did was change up the radios/modems. So a Rom can easily be flashed, as roms do not affect radios, to the 't' variant.

Now back to the devices at hand. The prevail and prevail2 are very different devices. It is not just a re-radioing. I am unsure but I believe the name 'ring' is a Cyanogenmod device tree for the prevail2. (Siting needed) and as yet again to my belief.. the old m820 or prevail1 has no Cyanogenmod tree. (Not worth a device tree I guess) so it has 2 names 'M820'. And prevail.

Whereas the M840 (a kind of remake) has prevail2 and a Cyanogenmod device tree 'ring'.

I hope this can clear up some confusion.
 
Hey all. Question, I dont understand what the difference is here:

How to add removed app's:
-Download this: RemovedApps.zip and CLICK HERE for instructions on how to add them
-If you need Talk or Genie Widget use the apk's from here: Goo.im - gapps-gb-20110828-signed.zip

RemovedApps.zip
gapps-gb-20110828-signed.zip

I dont understand what the difference is between these 2. I'm using CTMod 3.80, but what
is the difference?, which should I use?, what is signed gapps compared to the other?
 
nevermind. I went back and reviewed all my old posts in this forum about the same exact question from over a year ago. There are some things I want, but they are only available from the RemovedApps.zip file, like the android keyboard, for just one example.
But I thought that zip was for ctmod 3.75 only. Dont know. Whats in RemovedApps.zip is not in gapps-gb-20110828-signed.zip and vise-versa.
 
This is a Question, not a reply, sorry, could not find the New Post button anywhere.

My Phone's Power Button on the top-right side of the Prevail stopped working, no idea why, I even did a new CTMod install & tried everything else possible. Buying a new phone is not an option right now. So I'm stuck with my dying prevail still.

As a result of this, every time I make a phone-call, just after it starts to dial out that "lock screen" thing comes up where it displays "Press POWER KEY at top to UNLOCK".

Well the Power Key don't work, so as a result I am stuck in-call. So if I have to leave someone a message, I cannot hang up the phone, all I can do is pull the battery out and reboot the phone that way. There is oviously other problems with the phone, I mean, it is old as hell but I can't buy a new phone right now, and I can still use it. But as you can imagine, lol, after I pull the battery after leaving someone a message, they try calling me right back, but it takes a minute to boot back up, so I wind up playing phone tag. Plus because of this lockup issue, I can';t really check my voice mail messages or delete them, well I can listen to a new message left, just not access the keypad or do anything else.

When I pull the battery and stick it back in, the phone just turns on and boots up all by itself. So if you are wondering how I turn it on without the power button working, that is why I am able to turn it on at all.

Since I cannot press the power button to unlock the screen while in a call, can anyone tell me how to turn that lock-screen in-call feature off, access it, or something else?

I have Tasker installed as well as the Secure Settings Plugin, and I tried a bunch of different combinations to make it unlock the screen while in call, but I cant get it to work. So maybe I am not programming Tasker correctly to do it right, or maybe it just can't be done, which is why I am here.

~thanks
 
Go into settings n disable proximity sensor or it will say something like " power button ends call " had same issue with mine. Go into the phone dialer as if ur going to make a call n choose menu button then settings sorry. Then choose above what I suggested
 
Thanks, but there is no proximity sensor on the prevail, and the power button to end call is unchecked already. I even tried enabling it, that dont work either.

I actually read both of what you suggested in other forums already.
 
What about remapping the power key? Change, say the camera button into the power button.

Go to system/usr/keylayout/ and open generic.kl as a text file.

You should see something like this:


Locate the key assigned to camera and the one assigned to power and switch the numbers.

so if it says
Code:
key 108 power
key 153 camera

Then change it to

Code:
key 153 power
key 108 camera

Save the file and reboot
 
To help clean things up here if u seen my suggestions there. A simple sorry did not work for me would be nice so others can see what works. Also u didn't specify model of which prevail u had as for u could have had the m890 or the prevail 2 which has proximity sensors.. I suggest trying what lordvincent supplied here is very well over his answers . there's no other way to say this but the lord knows his stuff...
 
Thanks for your replies, I will try your remapping suggestion. I was not aware that could be done.
I have the Original Prevail, I actually have been on this forum since it was first started and the first prevail came out, I am familiar with Lordvince, so I will try your suggestion.

thankyou.
 
just tried what you said and there is no generic.kl file in that folder.
Can you post a screen shot of that folder?
I have the Original Prevail, I actually have been on this forum since it was first started and the first prevail came out, I am familiar with Lordvince, so I will try your suggestion.

thankyou.
I certainly know who you are as well.

If you'd like, you can message me on hangouts and we can tackle this one on one.

Lordvincent90@gmail.com
 
Hey Lord, long time no post.
Yeah, I'm still on my prevail lol.
Interesting side note, my sdcard first stopped working, then this power button problem started.
The sdcard cannot be formatted, or even written too, and there are some android folders like "permanantly" written on it. So I have replaced that card with the original 2GB card that came with the phone. And I am currently using Data Mode with the swap/stl13-turned to memory deal setup. Anyway, it's clear that the phone is dying and on it's way-out. So if I can get this problem taken care of for now, I will probably get a new phone in 2 more months.
I'm not on hangouts', would rather not set that up.
Anyway, here is the contents of system/usr/keylayout/

AVRCP.kl
qwerty.kl
sec_jack.kl
sec_key.kl
vino-headset.kl
vino-keypad.kl
 
Ah, Samsung. That's right ;)

Try sec_key.kl :)

With touchwiz most system related apks are sec_*.apk (sec_settings.apk etc) so I'd imagine it's the same with the key layout (.kl)
 
Lord, IT WORKED.

Thanks a lot Lord, and everyone else for your suggestions.
Just for anyone to know, for reference, this is what the sec_key.kl file showed:

# Copyright (c) 2009, Code Aurora Forum.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
#key 1 MENU WAKE_DROPPED
key 2 1 WAKE_DROPPED
key 3 2 WAKE_DROPPED
key 4 3 WAKE_DROPPED
key 5 4 WAKE_DROPPED
key 6 5 WAKE_DROPPED
key 7 6 WAKE_DROPPED
key 8 7 WAKE_DROPPED
key 9 8 WAKE_DROPPED
key 10 9 WAKE_DROPPED
key 11 0 WAKE_DROPPED
#key 12 FOCUS WAKE_DROPPED
#key 13 P WAKE_DROPPED
key 14 DEL WAKE_DROPPED
#key 15 I WAKE_DROPPED
key 16 Q WAKE_DROPPED
key 17 W WAKE_DROPPED
key 18 E
key 19 R
key 20 T
key 21 Y WAKE_DROPPED
key 22 U WAKE_DROPPED
key 23 I WAKE_DROPPED
key 24 O WAKE_DROPPED
key 25 P WAKE_DROPPED
key 26 SPACE WAKE_DROPPED
#key 27 SEARCH WAKE_DROPPED
key 28 ENTER
#key 29 EMPTY
key 30 A
key 31 S WAKE
key 32 D WAKE_DROPPED
key 33 F WAKE_DROPPED
key 34 G WAKE_DROPPED
key 35 H WAKE_DROPPED
key 36 J WAKE_DROPPED
key 37 K WAKE_DROPPED
key 38 L
#key 39 EMPTY
#key 40 EMPTY
#key 41 EMPTY WAKE_DROPPED
#key 42 EMPTY WAKE_DROPPED
#key 43 EMPTY WAKE_DROPPED
key 44 Z WAKE_DROPPED
key 45 X WAKE_DROPPED
key 46 C WAKE_DROPPED
key 47 V WAKE_DROPPED
key 48 B
key 49 N
key 50 M
key 51 COMMA WAKE_DROPPED
key 52 PERIOD WAKE_DROPPED
#key 53 T WAKE_DROPPED
#key 54 R WAKE_DROPPED
#key 55 ENVELOPE WAKE_DROPPED
#key 56 E WAKE_DROPPED
key 57 SPACE WAKE_DROPPED
#key 58 EMPTY
#key 59 EMPTY
#key 60 EMPTY
#key 61 EMPTY WAKE_DROPPED
#key 62 V WAKE_DROPPED
#key 63 C WAKE_DROPPED
#key 64 X WAKE_DROPPED
#key 65 Q WAKE_DROPPED
#key 66 ALT_LEFT WAKE_DROPPED
#key 67 VOLUME_DOWN WAKE_DROPPED
#key 68 EMPTY
#key 69 EMPTY
#key 70 EMPTY
#key 71 EMPTY
#key 72 W WAKE_DROPPED
#key 73 SHIFT_LEFT WAKE_DROPPED
#key 74 SMILY
#key 75 A WAKE_DROPPED
key 103 DPAD_UP WAKE_DROPPED
key 108 DPAD_DOWN WAKE_DROPPED
key 105 DPAD_LEFT WAKE_DROPPED
key 106 DPAD_RIGHT WAKE_DROPPED
key 352 DPAD_CENTER WAKE_DROPPED
#key 77 EMPTY
#key 78 EMPTY
#key 79 EMPTY
#key 80 EMPTY
key 249 SHIFT_LEFT WAKE_DROPPED

# handling for touch-key codes
key 102 HOME WAKE
key 139 MENU WAKE
key 158 BACK WAKE
key 114 VOLUME_DOWN WAKE_DROPPED
key 115 VOLUME_UP WAKE_DROPPED
key 116 POWER WAKE_DROPPED
key 212 CAMERA WAKE_DROPPED
key 528 FOCUS WAKE_DROPPED
key 215 AT WAKE_DROPPED
key 217 SEARCH WAKE

# Fake Focus
key 250 SYMBOL WAKE_DROPPED
key 251 ALT_LEFT WAKE_DROPPED
key 252 VST_LAUNCH
#key 252 SPEAKER WAKE_DROPPED
#key 254 ZOOM WAKE_DROPPED

#key 214 QUESTION WAKE_DROPPED
key 247 SMILY WAKE_DROPPED
# Platform Dump

------------------------------------------------------------

I just switched the numbers in this section like was suggested:

# handling for touch-key codes
key 102 HOME WAKE
key 139 MENU WAKE
key 158 BACK WAKE
key 114 VOLUME_DOWN WAKE_DROPPED
key 115 VOLUME_UP WAKE_DROPPED
key 116 POWER WAKE_DROPPED
key 212 CAMERA WAKE_DROPPED
key 528 FOCUS WAKE_DROPPED
key 215 AT WAKE_DROPPED
key 217 SEARCH WAKE

TO:

# handling for touch-key codes
key 102 HOME WAKE
key 139 MENU WAKE
key 158 BACK WAKE
key 114 VOLUME_DOWN WAKE_DROPPED
key 115 VOLUME_UP WAKE_DROPPED
key 212 POWER WAKE_DROPPED
key 116 CAMERA WAKE_DROPPED
key 528 FOCUS WAKE_DROPPED
key 215 AT WAKE_DROPPED
key 217 SEARCH WAKE

* Then I made sure the permissions were still the same, rebooted, and now I can access the dialer by unlocking the screen during a call by pressing the Camera Button.

Very simple fix.

Thankyou guys very much.
 
...of course just to mention for anyone that does not understand:
I backed up the original file then opened the sec_key.kl file from within the app "Root Explorer"
as a text file, or an "open with text editor" option, then after making
changes I saved as sec_key.kl (.kl) just replacing the original.

thanks again guys.
 
Back
Top Bottom