Anybody having issues loading boot settings at boot with voltage control?
I am.
It puts the script in /system/etc/init.d
Which where it has to be. But it still doesnt load at boot.
Anybody having issues too?
Ive tried My newest espresso and JT's vanilla GB and OMGB / OMFGB and CM7 with same results. So i know its not just my rom.
Sent from my SCH-I500 using XDA App
Nevermind. I fixed it by using script manager and selecting the script to run at boot and run as root.
If anyone is having this issue too,
Use script manager, navigate to /system/etc/init.d
And select what one that is your voltage script.
Sent from my SCH-I500 using XDA App
Enyo. said:
Nevermind. I fixed it by using script manager and selecting the script to run at boot and run as root.
If anyone is having this issue too,
Use script manager, navigate to /system/etc/init.d
And select what one that is your voltage script.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I fixed this by getting rid of duplicate numbers in init.d.
Sent from my Samsung Galaxy Tab 10.1
sendan said:
I fixed this by getting rid of duplicate numbers in init.d.
Sent from my Samsung Galaxy Tab 10.1
Click to expand...
Click to collapse
Do you know what you had to do?
Sent from my SCH-I500 using XDA App
Enyo. said:
Do you know what you had to do?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
All the scripts in init.d are numbered based on the order in which they execute at boot, if two scripts have the same number it can cause complications. Change the number portion of the name.
sendan said:
All the scripts in init.d are numbered based on the order in which they execute at boot, if two scripts have the same number it can cause complications. Change the number portion of the name.
Click to expand...
Click to collapse
But i have no same numbers.
It just goes 00, 01, 02, 03, 04, 05, S91 (boot settings), And the super chargers.
Sent from my SCH-I500 using XDA App
Enyo. said:
But i have no same numbers.
It just goes 00, 01, 02, 03, 04, 05, S91 (boot settings), And the super chargers.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Then it's not the same problem. Could be a number of things though; Starting with the obvious, are you running a kernel with init.d enabled? (Are your other scripts running at boot?)
sendan said:
Then it's not the same problem. Could be a number of things though; Starting with the obvious, are you running a kernel with init.d enabled? (Are your other scripts running at boot?)
Click to expand...
Click to collapse
Its my rom. Fixed it.
Sent from my SCH-I500 using XDA App
Related
Had CM7 on my phone and it was beautiful except my battery dropped like a rock. No rogue apps when testing with OS monitor. Used voltage control, cfg, conservative uv 50mv all levels between 100 - 1000. No oc. Am I missing something? Any suggestions? I need the battery to last more than 5-6 hrs. which is what I was getting. Posted this in cm7 thread but it moves along so fast that I received only one response so far.
Sent from my SCH-I500 using xda premium
thedoman said:
Had CM7 on my phone and it was beautiful except my battery dropped like a rock. No rogue apps when testing with OS monitor. Used voltage control, cfg, conservative uv 50mv all levels between 100 - 1000. No oc. Am I missing something? Any suggestions? I need the battery to last more than 5-6 hrs. which is what I was getting. Posted this in cm7 thread but it moves along so fast that I received only one response so far.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Using supercharger script. If your on the stable CM7 Build download busybox from market and install 1.7.x version
Then use supercharger. Or it won't work
If you use glitch kernel theirs a recovery where you can enable screenstate which changes the governor when the screen is off.
Sent from my SCH-I500 using XDA App
Enyo. said:
Using supercharger script. If your on the stable CM7 Build download busybox from market and install 1.7.x version
Then use supercharger. Or it won't work
If you use glitch kernel theirs a recovery where you can enable screenstate which changes the governor when the screen is off.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Two questions:
1. Where do I get info on supercharger script.
2. I was using glitch kernel. How exactly can I enable screenstate?
Thanks in advance if you can help or anyone else.
Sent from my SCH-I500 using xda premium
thedoman said:
Two questions:
1. Where do I get info on supercharger script.
2. I was using glitch kernel. How exactly can I enable screenstate?
Thanks in advance if you can help or anyone else.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
1. Do a google search for v6 supercharger script you will be directed to it's thread on xda by zeppelinrox
2. Reboot to recovery-> find menu choice that say GLITCH. Turn on
Screenstate scaling and choose your sleep governor. profit.
Forgot to add v6 supercharger is not necessary if using glitch as most of the same mods are included in the kernel.
Sent from my SCH-I500 using XDA App
Im on wicked rom and siyah 2.6.6 do i need to flash anything else on to it. I heard people talk about battery scripts and all that. And changing the voltage and im not sure if im suppose to flash on a script or something. If there is something i need to flash then someone let me know. I just want a good battery thats why i choose siyah so maybe this script stuff is good. Plus theres not one theres mutiple scripts so then which one. Its all very confusing to me :? Soneone enlighten me please
Thks
Sent from my GT-I9100 using XDA App
Ask in the Siyah thread in the development section.
No you don't need cuz in version 2.6.3 we see
removed siyah-battery, siyah-defaults and siyah-performance scripts from the blog. please remove all existing scripts before installing this version (or flash your existing rom again to remove all scripts). use init.d scripts if you know what you do, otherwise use VoltageControl app or ThunderBolt! scripts. use this CWM recovery flashable zip to remove previous 01siyah script. just flash it once and /system/etc/init.d/01siyah script will be removed.
Click to expand...
Click to collapse
and for 2.6.6 you don't need zip for battery.
The scripts people are talking about are pikcahu's thunderbolt! scripts, you dont need to flash them if you dont want to, they can help, but performance/batt are good at stock values.
(Part of thunderbolt! is built into the kernel anyway)
Thanks guys so i should leave it at wat its at when i flashed 2.6.6
Sent from my GT-I9100 using XDA App
jaher said:
Thanks guys so i should leave it at wat its at when i flashed 2.6.6
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
if it feels fine to you, then sure, if you want to tweak and mess about, then thats fine as well.
Lol kl at the moment its nothing special then again i only flashed it yesturday. Do u think there is any point using set cpu with 2.6.6
Sent from my GT-I9100 using XDA App
jaher said:
Lol kl at the moment its nothing special then again i only flashed it yesturday. Do u think there is any point using set cpu with 2.6.6
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
What do you want to change?
I would use voltage control myself, though with 2.6.6 it wont set max frequency correctly, that's supposed to be fixed next kernel version.
Well i use it to clock cpu lower at low battery and screen off
Sent from my GT-I9100 using XDA App
jaher said:
Well i use it to clock cpu lower at low battery and screen off
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yeh you can use setcpu to-do that, if you want! It wont hurt anything. Dont Undervolt to much or you may get instability.
By undervolt u mean underclocking right ?
Sent from my GT-I9100 using XDA App
jaher said:
By undervolt u mean underclocking right ?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
No.. undervolting is lowering the voltage at each frequency step
Underclocking is lowering the max frequency.
eg setting the max to 1000mhz would be underclocking
setting 1000mhz to 1100mV would be undervolting (just an example)
I havent even touched voltage settings i have no exp in tht
Sent from my GT-I9100 using XDA App
Wat would you say is better ondemand or this new lulzactive l. Whats the diff.
Sent from my GT-I9100 using XDA App
Hello guys today I am experiencing a lot of problems after the bootanimation of my rom start, this arrived (I think) in the middle of the folder part 1 stops for a while and then starts all over again always redoing this thing to infinity and the system does not boot, why? what happens? how to fix this? Thank you all for the answers
---blacksoul--- said:
Hello guys today I am experiencing a lot of problems after the bootanimation of my rom start, this arrived (I think) in the middle of the folder part 1 stops for a while and then starts all over again always redoing this thing to infinity and the system does not boot, why? what happens? how to fix this? Thank you all for the answers
Click to expand...
Click to collapse
Take a logcat and see what error it states.I doubt on android.policy.jar.have you edited it for power menu mod or for lock???
Sent from my GT-N7000 using xda app-developers app
vijai2011 said:
Take a logcat and see what error it states.I doubt on android.policy.jar.have you edited it for power menu mod or for lock???
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
But how do I get from logcat recognize the device when it is connected is in recovery?
---blacksoul--- said:
But how do I get from logcat recognize the device when it is connected is in recovery?
Click to expand...
Click to collapse
Connect your phone to PC,boot your phone and type
adb logcat > myrom.log
Now read the log and see what you have done wrong.
Sent from my GT-N7000 using xda app-developers app
I do not think the error is in the android.policy.jar file I replaced by inserting the original file, and it's always the same thing, I made a video so I can better understand the problem (sometimes the bootanimation lasts longer)
http://youtu.be/yKkLuHpU1p0
---blacksoul--- said:
I do not think the error is in the android.policy.jar file I replaced by inserting the original file, and it's always the same thing, I made a video so I can better understand the problem
http://youtu.be/yKkLuHpU1p0
Click to expand...
Click to collapse
There are many possibilities for a boot loop to occur.Only logcat can explain the exact reason.
Sent from my GT-N7000 using xda app-developers app
vijai2011 said:
There are many possibilities for a boot loop to occur.Only logcat can explain the exact reason.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
So even if I connect the phone to PC during boot the PC should recognize it?
---blacksoul--- said:
So even if I connect the phone to PC during boot the PC should recognize it?
Click to expand...
Click to collapse
Yes.
Sent from my GT-N7000 using xda app-developers app
vijai2011 said:
Yes.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
This is the report I understand I was wrong to not put the apk with system apk or is it something more serious? I have attached the file because the report was too long
Logcat Log
I see that it has multiple Java errors with frameworks.Is this a AOSP rom????If so there maybe error while compilation....
Sent from my GT-N7000 using xda app-developers app
vijai2011 said:
I see that it has multiple Java errors with frameworks.Is this a AOSP rom????If so there maybe error while compilation....
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
No it is not AOSP ROM is UOT
---blacksoul--- said:
No it is not AOSP ROM is UOT
Click to expand...
Click to collapse
You mean UOT kitchen???and I saw cyanogen mod in the log.That's why I asked.
Sent from my GT-N7000 using xda app-developers app
vijai2011 said:
You mean UOT kitchen???and I saw cyanogen mod in the log.That's why I asked.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes UOT kitchen you read cyano in the log in because my ROM is based on CyanogenMod 7 and I have yet to complete the total customization, so some apk is still original Cyanogenmod
---blacksoul--- said:
Yes UOT kitchen you read cyano in the log in because my ROM is based on CyanogenMod 7 and I have yet to complete the total customization, so some apk is still original Cyanogenmod
Click to expand...
Click to collapse
If you used uot kitchen,I can assure you that the boot loop is because of it.I too had the same issue using uot kitchen.I don't know what causes the problem and I solved the problem by theming myself....
Sent from my GT-N7000 using xda app-developers app
vijai2011 said:
If you used uot kitchen,I can assure you that the boot loop is because of it.I too had the same issue using uot kitchen.I don't know what causes the problem and I solved the problem by theming myself....
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
and then to solve the problem I put the apk SystemUI and framework-res original and then edit them manually?
---blacksoul--- said:
and then to solve the problem I put the apk SystemUI and framework-res original and then edit them manually?
Click to expand...
Click to collapse
Yeah....if you have HTC by any chance,you need HTC framework apks too for the dependency.
Sent from my GT-N7000 using xda app-developers app
vijai2011 said:
Yeah....if you have HTC by any chance,you need HTC framework apks too for the dependency.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
nothing does not want to leave, I did what you suggested, I even re-inserted the default keyboard, replace the original META-INF folder, but nothing does not start, what can I do?
Also, when I install from the recovery tells me that Framework-res, fonts and the bootanimation is still UOT why?
I'm having a doubt, it is not starting because I deleted some apk like Pacman.apk?
You need to start simple...
Get the cyanogenmod and just remove what you don't want and add what you do want first...then flash and see if it boots, if it does not boot then you deleted something you should've kept
Once youve gotten rid of unwanted apps and added wanted apps then you can start theming...uot kitchen is really only good for battery mod...but cyanogenmod already has this built into the settings... so, just use apktool to decompile the apks you want themed and start theming them with a photo editor...I use gimp, its free and has lots of features
UOT is great for personal quick themes...but if your going to be releasing the theme or ROM then you really want to do it all your self...you'll feel like you accomplished more, and it really helps you get n understanding on how things fit together in a ROM
Just by looking at your op...it is quite obvious that your new to android development...that is why I say to start simple, what I said above is exactly how I started...I would just delete and add apps at first, then I moved onto theming...and slowly progressed...now I'm building ROMs from source
Also BTW, cyanogenmod is an aosp based ROM...so your ROM is also aosp based...and I don't think uot kitchen works with cyanogenmod anyways because of all its existing mods
Sent from my SGH-I997 using Tapatalk 2
Title says it all ..
Must flash DSB's kernel to write to system...
http://forum.xda-developers.com/showpost.php?p=34904203&postcount=1
Thanks to DSB
Thanks for the Christmas present!!! In on this thread. Happy as phuck /10
Sent from my HTC6435LVW using Tapatalk 2
Yes. Very excellent.
Sent from my HTC6435LVW using xda premium
Still cant write to build.prop
Anyone managed to write to build prop?
Why does it say unfortunately app n shortcut has stop...is that a bug..
So how can i edit the build prop if it doesn't seem to save it? I'm on this kernel and i think system is still not writing. Anyone got this working?? Please do tell us how?
skinniebone said:
Why does it say unfortunately app n shortcut has stop...is that a bug..
Click to expand...
Click to collapse
I don't know what you are referring to.
Sent from my HTC6435LVW using xda app-developers app
Hendrickson said:
So how can i edit the build prop if it doesn't seem to save it? I'm on this kernel and i think system is still not writing. Anyone got this working?? Please do tell us how?
Click to expand...
Click to collapse
I just changed it to Galaxy Nexus by using Root Explorer and it worked correctly.
Be sure you are on the latest kernel, as it is the only one that allows writing to /system while booted into android.
Sent from my HTC6435LVW using xda app-developers app
iOSh8er said:
I just changed it to Galaxy Nexus by using Root Explorer and it worked correctly.
Be sure you are on the latest kernel, as it is the only one that allows writing to /system while booted into android.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I can confirm that editing build prop does work and stick on reboot. Was able to make photosphere stop working and start working again as a test.
You may have to reboot one more time. After installing it I updated superuser and it had a read/write error. After rebooting it is fine.
And once again my phone hates any kernel that's out beside stock. I wonder what's the problem that my phone hasn't been able to run without freezing and rebooting
sent from my beastly powered DNA using Tapatalk 2
This is good news ! now all we need is some cyanogenmod and aokp and well be set
It's this s-off or a workaround?
____________________________________________________________
"A foot is the ultimate stocking stuffer."
According to the developer, neither. IDK, it seems like we can pretty much do anything now.
I posted a "stock" version. For those who cannot seem to run anything else without driving me nuts, um, I mean without problems. :laugh:
D
.
Dri94 said:
It's this s-off or a workaround?
____________________________________________________________
"A foot is the ultimate stocking stuffer."
Click to expand...
Click to collapse
Neither...
Most unlock methods do not keep us from writing to /system, this fixes that for us.
Sent from my HTC6435LVW using xda premium
Would it be safe to delete all of my init.d scripts? I remember I had to delete ones related to kernel tuner when flashing a new kernel. What if I deleted all of the scripts whenever I flash a new kernel? Thanks!
Dave51495 said:
Would it be safe to delete all of my init.d scripts? I remember I had to delete ones related to kernel tuner when flashing a new kernel. What if I deleted all of the scripts whenever I flash a new kernel? Thanks!
Click to expand...
Click to collapse
Usually the Rom developer puts them in there, unless you know it is causing a problem it should stay there.
But to answer your question, it shouldn't cause a problem to remove them.
orangechoochoo said:
Usually the Rom developer puts them in there, unless you know it is causing a problem it should stay there.
But to answer your question, it shouldn't cause a problem to remove them.
Click to expand...
Click to collapse
Can you tell me which ones I'm supposed to have? Do any of these look out of the ordinary, or do they all belong? Thanks, by the way!
Edit: I'm running newts nos m7 1.6 with beastmode 5.9, if that matters
Those look normal, are you running Newts rom?
Dave51495 said:
Can you tell me which ones I'm supposed to have? Do any of these look out of the ordinary, or do they all belong? Thanks, by the way!
Edit: I'm running newts nos m7 1.6 with beastmode 5.9, if that matters
Click to expand...
Click to collapse
All those look fine. Why do you think you should delete all your scripts.
Sent from my HTC6435LVW using xda app-developers app
orangechoochoo said:
Those look normal, are you running Newts rom?
Click to expand...
Click to collapse
Yeah, I am
Bigandrewgold said:
All those look fine. Why do you think you should delete all your scripts.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I remember I had to delete ones from kernel tuner a while back, so I was wondering what would happen if I deleted all of them
Dave51495 said:
Yeah, I am
I remember I had to delete ones from kernel tuner a while back, so I was wondering what would happen if I deleted all of them
Click to expand...
Click to collapse
You would probably lose some performance and battery life... Just move them to a different folder and if you need to move them, move them back
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
You would probably lose some performance and battery life... Just move them to a different folder and if you need to move them, move them back
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
That's exactly what I do when troubleshooting for myself or other users. I just make a folder somewhere that I can easily navigate back and fourth between the folders because it makes it easier to move files.I name it "init out-it old folder" or something simple like that.
OP, The only two I would consider moving are GPU rendering and complete, just because I'm not sure what the complete script is, and usually I disable force 2D GPU rendering and I'm thinking that's what is in the other script.