Hi have the Stock Jelly Bean update on 9020a.
Rooted with Busy Box 1.20.2 via Stericson's Busy Box Installer.
I'm trying to change the Governor and IO Scheduler and using Init.d to configure the phone on launch. However init.d does not seem to be working. I have to reset my changes after every reboot. If I set the NSTools app to change it by having the app start up on boot, It seems to work that way. But I'd prefer Init.d for obvious reasons.
bump
Any fixes?
Related
I purchased my tab in China. Samsung China has deleted all Google apps from the pre-installed rom. As a result, the Chinese GT 10.1 community has compiled an Google app pack (GoogleServeice_P7510.zip) to bring back those apps.
I flashed it immediately after I rooted the tab. The Google apps were installed successfully. I entered my google account after the boot and every google app was running without a glitch. But not long after that I found I could no longer enter browser settings anymore. It would always give me a FC when I tried to do so. I then downloaded the dolphin browser. So this problem was bypassed.
Then I found there was something wrong with the superuser, I could not adb remount/push, and it couldn't be revoked by the apps that required root access.
This problem was partially resolved later by flashing the OC kernel for GT 10.1, which secured adb privileges. But the superuser was still problematic. Then I found out that after I flashed any zip other than root.zip in recovery, be it the kernel.zip, the su_busybox_tools.zip or google_servicepack.zip, the superuser icon in the app drawer would always become 4 times smaller (2 time in both height and length) than the superuser app "installed" by root.zip, as well all other apps.
There seemed to be something wrong with this version of superuser app (small icon). Whenever I opened an app that required root access, the superuser prompt window would not pop out. But if I flashed the root.zip again, the big-icon superuser app would be back. And other apps can revoke it most of time. However, it was not perfectly stable. Somethimes, it still failed to be revoked. I have flashed the root.zip among the other 3 zips for many times to get this conclusion.
I then applied the V6 SuperCharger script and flashed the su_busybox tools for GT 10.1 right before that, because SuperCharger script required busybox. However, due to the superuser problem, the SuperCharger script was not fully working. After reboot, part of the settings was changed back to default, because 99supercharger.sh couldn't be run on boot with root and there's not init.d folder in GT Tab 10.1. Then I flashed the OC kernel hoping it will fix all the problems. After that, I surprisingly found out that I was able adb remount and push. But the icon of the superuser app was again back to the small one. So the apps requiring root could not revoke it for permission.
As a result, I flashed the root.zip again. At this moment, superuser works normally, even after some reboots. SetCPU and script manager are able to automatically acquired root access on boot. But when I rechecked the supercharger script, current pages(minfree) were still showing blank.
Other problems include backspace and enter keys not working in terminal emulator/console. And the problem I just found - the notification ringtone list in the system settings and other app (e.g. Gmail) settings was blank. I could not change ringtone, although the system can play it without problem. And the ogg files are still there in /system/media/notifications.
Since all Android devices works more or less the same. I hope some of you phone experts can shed some light on these problem. The user base of Android tabs has made it less supported than Android phones. It'll be highly appreciated if all these annoying problems get fixed.
Thank you!
Having problems after switching rom to gummycharged with imo's 3.1.0 kernal and using tegrak overclock. I was previously using another rom with Imo 3.1.0 kernal and used Tegrak overclock without any issues. Yesterday I flashed Gummycharged and flashed Imo 3.1.0 kernal once again after installation I am now having issues loading module in Tegrak Overclock. I know that Tegrak overclock works based on kernal. I can't seem to figure out why with a different rom running the same kernal that Tegrak Overclock now wont load a module. I was hoping someone has had this experience and would be able to help me. Thanks
So what's the error message? Also, do you have a chance to allow it Superuser permissions?
Sent from my Droid Charge running Infinity Beta
The error I get it. Your device is not availiable. Do you want to see available models?
You know its funny when I adjust scaling was the only time that it asked for superuser permissions. I have tried to clear data in the app, uninstall app and reinstall and it never asks me for superuser permissions. I thought the same thing and thats why I tried to uninstall. I also looked in my superuser app to see if I could force the application permissions and couldn't find any options for that.
Open /system/build.prop and change the ro.product.model= line from "GummyCharge..." to "SCH-I510" and reboot the phone.
Awesome! Thanks for the help. I appreciate that and I'll save that for future reference!
Hi!
Has anyone succeeded in flashing CrossBreeder for CROMi-X 4.6.4? I'm trying to do so, but everytime something screws up... Sometimes Apex resets all of its config, sometimes I can't change time zone... I've done full wipe, then I flashed clean CROMi-X with latest Hund kernel, everything on Data2SD mod.
If anyone flashed CrossBreeder with no problems - what version of it did you use, and how exactly did you flashed it?
Used to be part of CROMI but it was dropped. So it's compatibility is probably in question
KinetiClutch said:
Used to be part of CROMI but it was dropped. So it's compatibility is probably in question
Click to expand...
Click to collapse
Yeah, I know that Lucius.zen managed to get this working on CROMI 3.4.7, and so do I. CrossBreeder really helps in adblocking, so I kinda care about having it in CROMi-X. It may be incompatible with it at all, but it's worth a try, isn't it? I just wonder which version to use and how properly flash it...
wnerw said:
Yeah, I know that Lucius.zen managed to get this working on CROMI 3.4.7, and so do I. CrossBreeder really helps in adblocking, so I kinda care about having it in CROMi-X. It may be incompatible with it at all, but it's worth a try, isn't it? I just wonder which version to use and how properly flash it...
Click to expand...
Click to collapse
When the next Cromi-x update comes out (my guess is some time next week) I plan on installing it using zens guide on now to install crossbreeder. I will report back the results if you are still interested by then.
CrossBreeder Mod/Ad Blocking:
The CrossBreeder Mod increases web page loading speed and browser responsiveness. It also removes ads from web pages instead of simply covering them with the "Web Page Not Availabe Dialogue". In order to enable ad blocking with the CrossBreeder mod you will need to apply the Ad Block Hosts mod in PMR, the Ad Away App in the CROMI installer, and the Ad Block Hosts in the CROMI installer.
NOTE - Do not enable the CrossBreeder Mod via the CROMI 3.4.7 installer. It will not work properly unless it is enabled after implementing the PMR tweaks/mods.
Step #1 - Enable CrossBreeder:
Download the CrossBreeder Mod attached to this post and move it to your external storage. Boot into TWRP and install the mount-data2sd.zip, then install the CrossBreeder Mod. Wipe Cache/Dalvick and reboot.
Step #2 - Enable Ad Blocking:
Once you have rebooted open the Ad Away app. Long press and delete the ismeh host source. Select the "Download Files and Apply Ad Blocking" button. Reboot your system. Once rebooted you should no longer have any ads in web pages or free apps
Click to expand...
Click to collapse
Latest crossbreeder can be found here: http://forum.xda-developers.com/showthread.php?t=2113150
ronniereiff said:
Latest crossbreeder can be found here: http://forum.xda-developers.com/showthread.php?t=2113150
Click to expand...
Click to collapse
I used this piece of guide by Lucius. So far it gave the worst output - total config mess. Time zone, language, everything going crazy.
I also tried latest build of CrossBreeder (5.something). Everything worked quite ok, until I launched WolfamAlpha... After wipe forced by this accident Google Account service (sth like that, an app which lets you login into google) crashes after each boot...
Thanks for help anyway. If you get any progress, drop me a line
JZ054M update to my Xoom 4G. Rerooted - at least I think. CWM6027 recovery installed. Installed an EOS3 kernel (working on stock/root wifi Xoom JB412).
It appears the kernel gets replaced on boot - or never really installs (though applying the zip completes successfully).
Is there a secret kernel overwrite on this release? How can i apply a kernel that sticks?
Root Check says everything looks good - and my root apps run fine. CWM recovery OK..
Suggestions?
Thanks
8/7
ElementalX 1.2 installs fine and lists itself in "About Phone" - and can verify most features... But no init.d support - and other init.d hacks fail too.
Something weird here..
Sent from my Xoom using XDA Premium HD app
How to set the settings like cpu frequency after installing elementalx kernel?
I installed the elementalx by using TWRP recovery in my nexus 5 (android 5.0.1), but how to set the settings like set the CPU frequency and enable double tap to wake up? Should I install some apps?
If I want to update later, should I install the origin kernel?
Thank you!!!
xcs1234 said:
How to set the settings like cpu frequency after installing elementalx kernel?
I installed the elementalx by using TWRP recovery in my nexus 5 (android 5.0.1), but how to set the settings like set the CPU frequency and enable double tap to wake up? Should I install some apps?
Click to expand...
Click to collapse
From ElementalX thread:
The config file is located at /etc/elementalx.conf. You can edit this file to change kernel settings. Whatever is set in this file will take effect when the device is booted (unless other scripts or apps interfere!)
Read OP for more details.
xcs1234 said:
If I want to update later, should I install the origin kernel?
Thank you!!!
Click to expand...
Click to collapse
Nope
xcs1234 said:
How to set the settings like cpu frequency after installing elementalx kernel?
I installed the elementalx by using TWRP recovery in my nexus 5 (android 5.0.1), but how to set the settings like set the CPU frequency and enable double tap to wake up? Should I install some apps?
If I want to update later, should I install the origin kernel?
Thank you!!!
Click to expand...
Click to collapse
I've been using ElementalX for some time. There's an app in the play store specifically for ElementalX kernel.
I always installed the kernel with default settings in AROMA installer since the app lets you tune all the values anyway
experience7 said:
I've been using ElementalX for some time. There's an app in the play store specifically for ElementalX kernel.
I always installed the kernel with default settings in AROMA installer since the app lets you tune all the values anyway
Click to expand...
Click to collapse
what's the name of that app?
ElementalX kernel
Here's the Play Store link: https://play.google.com/store/apps/details?id=flar2.elementalxkernel
Primokorn said:
From ElementalX thread:
The config file is located at /etc/elementalx.conf. You can edit this file to change kernel settings. Whatever is set in this file will take effect when the device is booted (unless other scripts or apps interfere!)
Read OP for more details.
Nope
Click to expand...
Click to collapse
If I want to install another kernel, can I just install it in the recovery(using the install button in the recovery mode)? Should I clean the present kernel, then install another kernel in the recovery?
There are recommendations that you should dirty flash the original ROM (which then overwrites your current kernel with the stock one). If you're on stock Android (Vanilla), fastboot flash the boot.img from the appropriate factory image. Then use your recovery to install zip > choose your kernel zip.
I've always used the 'easy method' by just dirty-flashing the kernel I want to try. Worked fine all the time [emoji14]