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

Root [MetroPCS] [ROM] KitKat 4.4.2 NEW BETA 4

This is horrible, a week without a crash and then 4 crashes in a day. I would like to try carbon rom, as it seems to come with a different kernel. In case this is due to a remote bug in the current kernel, switching to carbon room could help, though I might still hit the same but there as well. On the other hand, if this is a hardware issue, it will surely happen there as well and I can go and get a new phone.
 
Last edited:
This is horrible, a week without a crash and then 4 crashes in a day. I would like to try karbon rom, as it seems to come with a different kernel. In case this is due to a remote bug in the current kernel, switching to karbon room could help, though I might still hit the same but there as well. On the other hand, if this is a hardware issue, it will surely happen there as well and I can go and get a new phone.
Your crashes are because CPUs frequency. You need to run min 597 max 1.2
 
Your crashes are because CPUs frequency. You need to run min 597 max 1.2
How to set the limits on CPU frequency? Didn't see anything in the settings menus.
Searching on google, I came across SetCPU on xda. Should I use that?
 
Last edited:
How to set the limits on CPU frequency? Didn't see anything in the settings menus.
Searching on google, I came across SetCPU on xda. Should I use that?
Do you have develper mode active if so you should have performance settings on device ...you canvuse that...if you can get 3cTools it would be better... SetCPU its good buy u need pay one to be able to have full control.
 
Do you have develper mode active if so you should have performance settings on device ...you canvuse that...if you can get 3cTools it would be better... SetCPU its good buy u need pay one to be able to have full control.
I have developer options enabled, but I don't see any option to control CPU. I went ahead and installed something called No-frills CPU Control and it shows the current max as 1.188GHz and min as 384MHz. I can raise the min, but the max is already below the limit that you are suggesting. Is there anything to change here?
 
I have developer options enabled, but I don't see any option to control CPU. I went ahead and installed something called No-frills CPU Control and it shows the current max as 1.188GHz and min as 384MHz. I can raise the min, but the max is already below the limit that you are suggesting. Is there anything to change here?
The max speed is actually a tad below the full 1.2ghz speed that the phone advertises. Its like that for everybody
 
The max speed is actually a tad below the full 1.2ghz speed that the phone advertises. Its like that for everybody
That means, the max is already as per your suggestion? I lowered it further and will observe it over the next few days. Should I bump up the min or 384MHz OK?
 
Ok, made the recommended change and will observe it over the next few days. Thanks a lot for answering all my questions.
If u van have MPdecison (multy processor on) its good too... Im ginna send you a present later on tonight... It will be on ur PM inbox...
 
Just FMI, is this issue only specific to some variants? If not why is it not part of the rom/kernel itself?
No... just uncompleted job... Due to lots of work of developer... If u want stock. kk u can use kk.mini Voa if u want cm 11 4.4.4 u can use Carbon rom.
 
Last edited:
No crashes so far after updating the cpu frequencies.

Anybody knows if the ring targets can be customized for the ring that shows up when you slide up from the bottom?
 
No crashes so far after updating the cpu frequencies.

Anybody knows if the ring targets can be customized for the ring that shows up when you slide up from the bottom?
you would need a costumization setting within setting like eg...home/selector from LG , TouchW-adaptation from samsung,
carbon-fiber setting from carbon or ui-face fro aokp i dont knw if you can install the apk+frameworks of any other roms based on 4.4.2 and if they work some of them are part of the settings.spk other parts of kernels, other part of the framewors
 
you would need a costumization setting within setting like eg...home/selector from LG , TouchW-adaptation from samsung,
carbon-fiber setting from carbon or ui-face fro aokp i dont knw if you can install the apk+frameworks of any other roms based on 4.4.2 and if they work some of them are part of the settings.spk other parts of kernels, other part of the framewors
I think that the navigation ring is built into the systemui.apk and the only way to remove or customize It is to modify the apk. I tried using gravity box before because it has options for this but it didn't work.
 
So is the current ring actually working as provided by the LG stock ROM? I have never seen the stock version, but judging by the fact that Memo is a ring target, I am guessing that it is a stock feature.

I uploaded all the QSlide apps, save the .apk and .odex files to system/priv-app, change the permission to rw-r--r-- and ownership to root. Then reboot

QSlide Apps

I followed your instructions to add calculator and it works, thank you! A quick question on launching the memo.. I can launch from the ring target, but it doesn't show up under the QSlide apps. Is this expected?
 
So is the current ring actually working as provided by the LG stock ROM? I have never seen the stock version, but judging by the fact that Memo is a ring target, I am guessing that it is a stock feature.



I followed your instructions to add calculator and it works, thank you! A quick question on launching the memo.. I can launch from the ring target, but it doesn't show up under the QSlide apps. Is this expected?
YES CUS YOU ARE USING A STOCK. APK FROM 4.4.2 ON A CM ROM. PLUS IT SHOULD BE TARGET FROM THE LEFT TOP BOTTON TOO
 
To integrate Google play services and play store updates into the rom you just need a file manager like root explorer or root browser. Whatever file manager you use must have root access.
What you have to do is go to /data/app and rename Google play services to GmsCore.apk and rename play store to Phonesky.apk (This is caps sensitive). Both apps will probably force close when you rename them but this is normal.
The next step is to move both apps (cut & paste) into /system/priv-app. There should be a pop-up telling you that GmsCore.apk and Phonesky apk already exist and asking if you want to replace (overwrite) them. Choose the option to replace (overwrite) these two apps and after it is done check and make sure the permissions are set to rw-r--r--. Finally reboot to recovery and wipe dalvik cache then reboot the phone and you're done.
I have a followup question on this. After cleaning up multiple versions of GmsCore.apk and com.google.android.gms-*.apk in /data/app and /system/priv-app, I moved the latest com.google.android.gms-1.apk to /system/priv-app and after a cleanup of dalvik cache, it has been working great. I had to repeat the cleanup process at least once in between, when I got the play services crashing and I figured that an update left multiple versions of com.google.android.gms-*.apk again. All is good until yesterday when play services started crashing again and this time, I found no update of com.google.android.gms or multiple versions, so I can't figure out what is causing the crashes. I noticed that /system/priv-app also has something called PreBuildGmsCore.apk with a slightly older timestamp. Can this be safely deleted in favor of com.google.android.gms-1.apk or is it also required?
 
I have a followup question on this. After cleaning up multiple versions of GmsCore.apk and com.google.android.gms-*.apk in /data/app and /system/priv-app, I moved the latest com.google.android.gms-1.apk to /system/priv-app and after a cleanup of dalvik cache, it has been working great. I had to repeat the cleanup process at least once in between, when I got the play services crashing and I figured that an update left multiple versions of com.google.android.gms-*.apk again. All is good until yesterday when play services started crashing again and this time, I found no update of com.google.android.gms or multiple versions, so I can't figure out what is causing the crashes. I noticed that /system/priv-app also has something called PreBuildGmsCore.apk with a slightly older timestamp. Can this be safely deleted in favor of com.google.android.gms-1.apk or is it also required?
Instead of deleting it rename it to PrebuiltGMSCore.apk.bak and see if it causes any problems. If you need to later, just remove .bak from the end of the filename. Also, whenever I replace a system app with a newer version I always change the name of the apk. For example, to integrate an update of the google play store, first I'll rename /data/app/com.android.vending.apk to Phonesky.apk then move it to /system/priv-app so that it overwrites the original apk. I think its best to do it this way.
 
Instead of deleting it rename it to PrebuiltGMSCore.apk.bak and see if it causes any problems. If you need to later, just remove .bak from the end of the filename. Also, whenever I replace a system app with a newer version I always change the name of the apk. For example, to integrate an update of the google play store, first I'll rename /data/app/com.android.vending.apk to Phonesky.apk then move it to /system/priv-app so that it overwrites the original apk. I think its best to do it this way.
After I renamed it and removed the dalvik-cache, I don't see the play services crashing, but I am seeing the message "Unknown issue with Google Play services." in a few apps that need play services, like Hangouts, YouTube and Play Music (though it is slightly different message). I found this thread with many reporting the same message:

https://productforums.google.com/forum/m/#!topic/hangouts/vsQnRtWdemU

However, the solution is not applicable to me, since I have already moved the update into priv-app. Perhaps I should remove the update also and start over?
 
So. When I call screen is dead but goes back to normal when caller ends. I Also get 4G but not lte. Any fixes for these two problems?
 
So. When I call screen is dead but goes back to normal when caller ends. I Also get 4G but not lte. Any fixes for these two problems?
Since this is not a metropcs ROM and LTE is the only true 4g technology, it will say 4g when you are connected to LTE.

4G LTE=4G, "4G"=H+

I no longer have an f6 so I can't shed any light on your other issue.
 
After I renamed it and removed the dalvik-cache, I don't see the play services crashing, but I am seeing the message "Unknown issue with Google Play services." in a few apps that need play services, like Hangouts, YouTube and Play Music (though it is slightly different message). I found this thread with many reporting the same message:

https://productforums.google.com/forum/m/#!topic/hangouts/vsQnRtWdemU

However, the solution is not applicable to me, since I have already moved the update into priv-app. Perhaps I should remove the update also and start over?
So, I got tired of seeing this message and on top of that I wanted to make Hangouts as the messaging app (since it supports filtering SMS spam), so I captured the logcat and found these messages:

Code:
D/dalvikvm( 8505): Trying to load lib /data/app-lib/com.google.android.gms-1/libgmscore.so 0x4253b630
D/dalvikvm( 8505): Shared lib '/data/app-lib/com.google.android.gms-1/libgmscore.so' already loaded in same CL 0x4253b630
E/ProviderInstaller( 8505): libgmscore version mismatch (7571 vs. 7329)
E/ProviderInstaller( 8505): Failed to install provider: null
E/Babel_RequestWriter( 8505): GPS not available when trying to installIfNeeded
E/Babel_RequestWriter( 8505): dda
E/Babel_RequestWriter( 8505):     at dux.a(Unknown Source)
E/Babel_RequestWriter( 8505):     at com.google.android.apps.hangouts.realtimechat.RequestWriter.onCreate(SourceFile:400)
E/Babel_RequestWriter( 8505):     at android.app.ActivityThread.handleCreateService(ActivityThread.java:2581)
E/Babel_RequestWriter( 8505):     at android.app.ActivityThread.access$1800(ActivityThread.java:139)
E/Babel_RequestWriter( 8505):     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1282)
E/Babel_RequestWriter( 8505):     at android.os.Handler.dispatchMessage(Handler.java:102)
E/Babel_RequestWriter( 8505):     at android.os.Looper.loop(Looper.java:136)
E/Babel_RequestWriter( 8505):     at android.app.ActivityThread.main(ActivityThread.java:5103)
E/Babel_RequestWriter( 8505):     at java.lang.reflect.Method.invokeNative(Native Method)
E/Babel_RequestWriter( 8505):     at java.lang.reflect.Method.invoke(Method.java:515)
E/Babel_RequestWriter( 8505):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:788)
E/Babel_RequestWriter( 8505):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:604)
E/Babel_RequestWriter( 8505):     at dalvik.system.NativeStart.main(Native Method)

I don't know what the exception is and if it is related, but looks like an older version of this native shared library is leftover. Any idea how to fix this issue? If I remove it, will it get restored from the newer apk, or do I need to manually extract it from the apk and overwrite it?

Update: Interestingly, the path "/data/app-lib/com.google.android.gms-1/libgmscore.so" is not even valid. When I searched for libgmscore.so, I found one under /system/lib, but nowhere else.

Update 2: It appears that Android expects the .so files that correspond to the apk's under the /system/priv-app to be under /system/lib. In case of apk's under /data/app, it automatically expands them to /data/app-lib (which is not the case with the apks under /system/priv-app). In case of an update for gms, the apk gets installed under /data/app and the .so under /data/app-lib. To move this update into the system, it is not enough to just move the apk to /system/priv-app (and overwrite the existing apk), but you also need to move the existing .so files from /data/app-lib to /system/lib (this step may leave any outdated .so files that are no longer used, but I am guessing it should be OK). I actually didn't try this myself to confirm that they are the right steps, mainly because I don't plan to do it due to the overhead and reliability issues associated with them. Instead, I cleared all the existing references to gms and installed it freshly as a user app and then used link2sd to move it to 2nd partition, after ensuring that the play services errors are gone. I will have to watch out how this works after the next update for gms gets pushed.
 
Last edited:
Back
Top Bottom