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

Root {DISCONTINUED}MegaTron 6.2.5 (Updated 7/13/13)

BLuFeNiX said:
The above solution didn't work for me. (I wasn't presented the option to "uninstall updates," so I just cleared the data, rebooted and updated.)

I have also tried clearing google services framework data, and I dowloaded an app to clear gps data. I cannot get GPS connectivity for any app.

Any advice?
Click to expand...


Yea i am having the same problem my GPS want connect if u figure please let me know
 
sorry for all the problems guys. honestly didnt think there would be this many. I am one of those who it works fine for. I tried recreating all of these issues on my tu but they all work just fine. we think we have the problem narrowed down to the symlinks in the script.

I also think the new kernel may not be jiving well with this version for some of you

what that means for you (if it you are one that is having problems) is just to flash back to 5.1 or another rom if you like and wait it out for week or so. I dont think we are gonna waste a whole lot of time on this version because of the ota release of 2.3.6.. we were already in the starting stages of getting this ported to the new android version. doing this will more than likely solve most if not all of the issues here an accomidate bob's new kernel much better anyways.

yes loota, we will both take your suggestions into concideration when we are working on this new version. and thanks for helping everyone else in the thread
loota = asset to this community :thumb:

thank you all for being so interested in our work. we were kind of broad sidded with this new update right after finishing 5.3.
 
Ty mavrik, just to be clear I did not have any issues with 5.3 until I updated the kernel.. imho I don't think anyone here is experiencing issues with just the straight 5.3 release you guys put out... I may be wrong but that's how it sounds to me...

Sent from my SPH-M930BST using Tapatalk 2 Beta-6
 
Has anyone had problems dl'ing 5.1. I'm trying to downgrade from 5.3. I have my backup on my home PC but I've got some "downtime " at work right now & trying to do it on my phone.
 
Loota said:
Paul I believe that those having issues are having issues after installing bobz new oc kernel on top of shevron 5.3. I can't speak for others but that's where things went sour for me.

Sent from my SPH-M930BST using Tapatalk 2 Beta-6
Click to expand...

Loota, I have Bobz new kernal installed. I installed it immediately after installing the new rom. Then I did the wipe, clear and fix permissions. That is when all my problems went away. I love the new rom and kernal, cause my touch screen bug has been fixed and the new rom is speedy.
 
Loota said:
Blu does it stop your system fc's?
Click to expand...
I never had any force close problems. Just the GPS issue.

Loota said:
Ty mavrik, just to be clear I did not have any issues with 5.3 until I updated the kernel.. imho I don't think anyone here is experiencing issues with just the straight 5.3 release you guys put out... I may be wrong but that's how it sounds to me...
Click to expand...
I tried flashing the 5.3 release twice (no kernel update or anything), but I stil have GPS issues.

chevanlol360 said:
im quite sure that uninstall all updates for google maps then updating and reboot solves the gps problem.
Click to expand...
This did not work for me :(
 
BLuFeNiX said:
I never had any force close problems. Just the GPS issue.


I tried flashing the 5.3 release twice (no kernel update or anything), but I stil have GPS issues.


This did not work for me :(
Click to expand...

reinstalling the rom does not change the kernel at all.. if you did at some point install bobz new kernel then you are still running it unless you reverted back to the old one or stock kernel
 
chevanlol360 said:
im quite sure that uninstall all updates for google maps then updating and reboot solves the gps problem.

Finally got my phone back so its time to go back to dev'ing;):rock:
Click to expand...

This also did not werk for me chev, but I'm sure glad to hear you're back in the game!

Sent from my SPH-M930BST using Tapatalk 2 Beta-6
 
mavrikmeercat said:
reinstalling the rom does not change the kernel at all.. if you did at some point install bobz new kernel then you are still running it unless you reverted back to the old one or stock kernel
Click to expand...

So BobZ's new kernel causes these problems? Is there a kernel that fixes the touch screen and doesn't cause GPS issues?
 
BLuFeNiX said:
So BobZ's new kernel causes these problems? Is there a kernel that fixes the touch screen and doesn't cause GPS issues?
Click to expand...

No bobz kernel does not cause these issues by itself. I am running stock with root and bobz kernel with no force closes and no gps issue whatsoever. This issue is an incompatibility between 5.3 and bobZ's kernel. 5.1 also worked flawlessly with bobZ's kernel when I tested it.

Keep in mind users that this rom version was created before bobZ's kernel so its definitely not something chev or mavrik could have helped either..

Its just a shit happens situation.

Keep up the good work guys its an amazing project!

Sent from my SPH-M930BST using Tapatalk 2
 
Ok well I got everything fixed and have shevron 5.3.0, cwm, root, bobs kernel. I don't see a big diff from stock and 5.3.0 (I know there is I am just saying that everything works as I remember it properly but have not tried gps)

Thanks everyone!

*Had 5.1.0*
Meant to fix this sooner, 5.3.0 will not work on my sprint TU via CWM update, so it stayed with the 5.1.0 from earlier.
 
I love this rom. Any idea what the eta is on 2.3.6? I got tired of seeing the stupid update notification and went stock again. :(

edit: stock sucks too much. wifi issues, lag, and too many fc's for me. reverted back to 5.3.0 seems patience is my only option. chev, i'm counting on you and meer. I know you can do it.
 
ittbattlesship said:
I love this rom. Any idea what the eta is on 2.3.6? I got tired of seeing the stupid update notification and went stock again. :(

edit: stock sucks too much. wifi issues, lag, and too many fc's for me. reverted back to 5.3.0 seems patience is my only option. chev, i'm counting on you and meer. I know you can do it.
Click to expand...

If you look at some of the newer threads, there are a few methods to get 2.3.6 with root.
 
ittbattlesship said:
I love this rom. Any idea what the eta is on 2.3.6? I got tired of seeing the stupid update notification and went stock again. :(

edit: stock sucks too much. wifi issues, lag, and too many fc's for me. reverted back to 5.3.0 seems patience is my only option. chev, i'm counting on you and meer. I know you can do it.
Click to expand...

Mavrickmeercat and i have already begun the update process for the rom, no ETA's will be given all i can say is that its coming soon.
 
I just tested Shevrom 5.3 with BobZ's kernel and the FC29 baseband.

Everything works (wifi, data, phone calls, market, etc) except for GPS. I do not get any lock, and no GPS indicator appears on my notification bar. This is the same as when I was on the EG29 baseband.

Here is a logcat of me trying to get a gps lock in google maps:
Code: 
--------- beginning of /dev/log/system

W/PowerManagerService(  158): Timer 0x3->0x1|0x0

I/PowerManagerService(  158): Ulight 3->1|0

I/PowerManagerService(  158): Light Animator Finished curIntValue=20

--------- beginning of /dev/log/main

I/InputReader(  158): dispatchTouch::touch event's action is 0

I/InputDispatcher(  158): Delivering touch to current input target: action: 0, channel '4074c240 Keyguard (server)'

D/PowerManagerService(  158): reactivateScreenLocksLocked mProxIgnoredBecauseScreenTurnedOff=false

D/PowerManagerService(  158): acquireWakeLock flags=0x1000001a tag=keyguard uid=1000 pid=158   myUID=1000 myPID=158 myTID=196

I/PowerManagerService(  158): Ulight 1->7|0

I/PowerManagerService(  158): Light Animator Finished curIntValue=32

I/LockScreen(  158): ***** onTrigger : UnLock *****

D/PowerManagerService(  158): enableUserActivity true

D/PowerManagerService(  158): releaseWakeLockLocked flags=0x0 tag=keyguard uid=1000 pid=158 myUID=1000 myPID=158 myTID=196

I/PowerManagerService(  158): Ulight 7->3|0

D/Beautiful Widgets(  662): UserPresent from Weather14

D/Beautiful Widgets(  662): Screensaver mode: false

I/InputReader(  158): dispatchTouch::touch event's action is 1

W/InputManagerService(  158): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@408ce0b0

I/InputDispatcher(  158): Delivering touch to current input target: action: 1, channel '4074c240 Keyguard (server)'

I/InputReader(  158): dispatchTouch::touch event's action is 0

I/InputDispatcher(  158): Delivering touch to current input target: action: 0, channel '407a5218 StatusBar (server)'

I/PowerManagerService(  158): Ulight 3->7|0

I/NotificationService(  158): Notification canceled by : mLedNotification = null mScreenOn = true mInCall = false mNotificationPulseEnabled = true

W/AudioSystem(  121): get_audio_policy_service()

V/AudioPolicyManager(  121): releaseOutput() 1

I/AudioService(  158):  AudioFocus  abandonAudioFocus() from android.media.AudioManager@40774580

I/InputReader(  158): dispatchTouch::touch event's action is 1

I/InputDispatcher(  158): Delivering touch to current input target: action: 1, channel '407a5218 StatusBar (server)'

D/skia    (  228): purging 191K from font cache [26 entries]

I/InputReader(  158): dispatchTouch::touch event's action is 0

I/InputDispatcher(  158): Delivering touch to current input target: action: 0, channel '407c5d78 TrackingView (server)'

I/InputReader(  158): dispatchTouch::touch event's action is 1

I/InputDispatcher(  158): Delivering touch to current input target: action: 1, channel '407c5d78 TrackingView (server)'

I/InputReader(  158): dispatchTouch::touch event's action is 0

I/InputDispatcher(  158): Delivering touch to current input target: action: 0, channel '407c5d78 TrackingView (server)'

I/InputReader(  158): dispatchTouch::touch event's action is 1

I/InputDispatcher(  158): Delivering touch to current input target: action: 1, channel '407c5d78 TrackingView (server)'

I/NotificationService(  158): Notification canceled by : mLedNotification = null mScreenOn = true mInCall = false mNotificationPulseEnabled = true

W/InputManagerService(  158): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@40744a30

I/InputReader(  158): dispatchTouch::touch event's action is 0

I/InputDispatcher(  158): Delivering touch to current input target: action: 0, channel '408a8488 com.fede.launcher/com.fede.launcher.Launcher (server)'

I/InputReader(  158): dispatchTouch::touch event's action is 1

I/InputDispatcher(  158): Delivering touch to current input target: action: 1, channel '408a8488 com.fede.launcher/com.fede.launcher.Launcher (server)'

I/ActivityManager(  158): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.apps.maps/com.google.android.maps.MapsActivity bnds=[243,338][317,425] } from pid 245

I/GLThread( 1428): onResume tid=23

I/Main thread( 1428): onResume waiting for !mPaused.

I/GLThread( 1428): mPaused is now false tid=23

I/GLThread( 1428): noticed surfaceView surface acquired tid=23

W/EglHelper( 1428): start() tid=23

W/EglHelper( 1428): createContext com.google.android.gles_jni.EGLContextImpl@408bb390 tid=23

I/Main thread( 1428): onWindowResize waiting for render complete from tid=23

W/GLThread( 1428): egl createSurface

W/EglHelper( 1428): createSurface()  tid=23

W/GLThread( 1428): onSurfaceCreated

W/GLThread( 1428): onSurfaceChanged(320, 410)

I/Main thread( 1428): onWindowResize waiting for render complete from tid=23

I/Main thread( 1428): onWindowResize waiting for render complete from tid=23

I/GLThread( 1428): noticing that we want render notification tid=23

I/Main thread( 1428): onWindowResize waiting for render complete from tid=23

W/GLThread( 1428): onSurfaceChanged(320, 410)

I/Main thread( 1428): onWindowResize waiting for render complete from tid=23

I/Main thread( 1428): onWindowResize waiting for render complete from tid=23

I/GLThread( 1428): sending render notification tid=23

D/ViewRoot( 1428): WindowLayout in setView:WM.LayoutParams{(0,0)(320xwrap) gr=#33 ty=1000 fl=#20218 fmt=-2}

E/libsecgps(  158): connectToDaemon: fail in connect() : No such file or directory

E/libsecgps(  158): gps_state_init: failed to connect socket /data/gps/secgpsd.socket

E/GpsLocationProvider(  158): set_position_mode failed in startNavigating()

D/NlpVersionInfo( 1428): com.google.android.location not found

D/NetworkLocationClient( 1428): NONE minProtocolVersion -1 maxProtocolVersion -1 releaseVersion -1

D/NetworkLocationClient( 1428): GMM minProtocolVersion 1 maxProtocolVersion 1 releaseVersion 1105

D/NetworkLocationClient( 1428): binding to Intent { act=com.google.android.location.internal.GMM_NLP }

D/NetworkLocationClient( 1428): onServiceConnected to ComponentInfo{com.google.android.apps.maps/com.google.android.location.internal.server.NetworkLocationService}

I/InputReader(  158): dispatchTouch::touch event's action is 0

I/InputDispatcher(  158): Delivering touch to current input target: action: 0, channel '4092d6e0 com.google.android.apps.maps/com.google.android.maps.MapsActivity (server)'

I/InputReader(  158): dispatchTouch::touch event's action is 1

I/InputDispatcher(  158): Delivering touch to current input target: action: 1, channel '4092d6e0 com.google.android.apps.maps/com.google.android.maps.MapsActivity (server)'

D/ViewRoot( 1428): WindowLayout in setView:WM.LayoutParams{(0,64)(wrapxwrap) gr=#51 ty=2005 fl=#98 fmt=-3 wanim=0x1030004}

D/PowerManagerService(  158): acquireWakeLock flags=0xa tag=KEEP_SCREEN_ON_FLAG uid=1000 pid=158   myUID=1000 myPID=158 myTID=345

D/PowerManagerService(  158): releaseWakeLockLocked flags=0x0 tag=KEEP_SCREEN_ON_FLAG uid=1000 pid=158 myUID=1000 myPID=158 myTID=194

W/PowerManagerService(  158): Timer 0x7->0x3|0x0

I/PowerManagerService(  158): Ulight 7->3|0

D/ViewRoot( 1428): WindowLayout in setView:WM.LayoutParams{(0,64)(wrapxwrap) gr=#51 ty=2005 fl=#98 fmt=-3 wanim=0x1030004}

D/PowerManagerService(  158): acquireWakeLock flags=0xa tag=KEEP_SCREEN_ON_FLAG uid=1000 pid=158   myUID=1000 myPID=158 myTID=164

D/PowerManagerService(  158): releaseWakeLockLocked flags=0x0 tag=KEEP_SCREEN_ON_FLAG uid=1000 pid=158 myUID=1000 myPID=158 myTID=194

D/InputReader(  158): Input event: value=1

D/InputReader(  158): Input event: value=0

I/ActivityManager(  158): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.fede.launcher/.Launcher } from pid 158

I/GLThread( 1428): onPause tid=23

I/Main thread( 1428): onPause waiting for mPaused.

I/GLThread( 1428): mPaused is now true tid=23

I/GLThread( 1428): releasing EGL surface because paused tid=23

W/EglHelper( 1428): destroySurface()  tid=23

W/EglHelper( 1428): finish() tid=23

I/GLThread( 1428): releasing EGL context because paused tid=23

I/GLThread( 1428): noticed surfaceView surface lost tid=23

I cleared the log before my test. When the log starts, GPS is already enabled and google maps was in the background. After I started logcat, I opened google maps and tapped on the "find me" button. I waited for it to say "waiting for location" and "location temporarily unavailable", then waited a few seconds and stopped logcat.

I hope this helps. Let me know if I can do any more testing.
 
So I was following the steps outlined by meercat in his most recent, 21 step post on how to switch the phone over to 5.3.0 when, just after step 11, my phone somehow just shut off while in CWM. Now, when I try to boot, after the samsung screen it pauses for a long period of time on the transform ultra screen. It then goes into "Ram Dump Mode", with no availability for me to re-enter cwm. Is it Bricked? can anyone hep me?
 
cheronobyl said:
So I was following the steps outlined by meercat in his most recent, 21 step post on how to switch the phone over to 5.3.0 when, just after step 11, my phone somehow just shut off while in CWM. Now, when I try to boot, after the samsung screen it pauses for a long period of time on the transform ultra screen. It then goes into "Ram Dump Mode", with no availability for me to re-enter cwm. Is it Bricked? can anyone hep me?
Click to expand...

Can you get into download mode?
 
My friend got it working for me. Now the only problems I'm having are the aforementioned GPS issue (Like everyone else, so I'l just wait for the patch) and for someone reason my market will not update to play store.
 
You must log in or register to reply here.
Back
Top Bottom