PrinceCorwin
Android Expert
Actually, no, I wasn't using the power method. I was using rom toolbox. My bad. I'll do it again using power method
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Enhanced init.d/simulated run levels
- Thread starter Yoinx
- Start date
-
- Tags
- lg spectrum
Actually, no, I wasn't using the power method. I was using rom toolbox. My bad. I'll do it again using power method
PrinceCorwin
Android Expert
double post
Yeah. Unfortunately, third party apps don't have to necessarily use the same methods to shutdown the phone... and there's no real way to hook a shutdown in android conveniently... Luckily when you use the reboot to recovery method through the power menu button it sets a backup property in case things don't go right. (sys.shutdown.request = 1recovery in the case of recovery if you're interested) Luckily, I can hook this in init.rc, which is where the line to trigger the onshutdown event in sysinit went. However, the catch is that the only thing that's triggering this property being set is the reboot recovery in power options.
It was doing it like this.... or having a simple process running forever after your phone starts writing the time to the cache every X seconds. I didn't care much for that option, because it's unnecessary wear and tear on the internal memory and if the process hangs you have to deal with lag.
Now that I've gotten to the bottom of what's going on... I'll update the links in the OP once I hear back that it did in fact work.
now... BACK TO TWRP!
PrinceCorwin
Android Expert
SUCCESS!!!!!!!!!!!!!!!!!!!!! Thanx for sticking with me through all this, yoinx.
Now I can have some free time to go research what adb and twrp are.
Now I can have some free time to go research what adb and twrp are.
SUCCESS!!!!!!!!!!!!!!!!!!!!! Thanx for sticking with me through all this, yoinx.
Now I can have some free time to go research what adb and twrp are.
TWRP is a recovery that you use instead of CWM. TeamWin Projects - TWRP 2.5 - | TeamWin
it looks nicer. Lets you name backups within the recovery itself, you can que multiple zips to flash at once (rom,gapps,tweaks for instance) and it will install them all for you in one shot. More importantly, it lets the screen turn off (on a timeout) and back on when you touch it during recoveries... Which really helps the ol' battery if you do backups on battery.
More importantly, it's all opensource. Right now, the one I've been build/posting is still experimental. IF you're still learning and don't quite know how to use ADB, I'd recommending steering clear of it for a bit until some more experienced users post back with their experiences.
As for ADB... Its a debugging bridge, it gives you a shell prompt (think command or dos prompt) to execute commands on your device. With 4.2.2 you need to use an updated 4.2.2 adb as there's a security handshake now. It should prompt you on your phone to allow the connection from your computer.
http://d-h.st/WXX
Extract this zip to a directory, say C:/ADB to keep it simple. Since you rooted... You have your drivers installed. So go to Start > run > "cmd" then "cd C:/adb" then you should be able to "adb devices" and it should list a device... probably named "device" you can then use a TON of commands on your phone as the busybox binary gives it a nearly full set of linux commands. The most important are
adb shell - for a shell prompt that executes commands on the phone
adb push - pushes a file to the phone, ex: adb push file_in_adbs_directory /sdcard/filename
adb pull - pulls a file from the phone adb pull remote_path local_path
adb logcat - this provides debugging logs. adb logcat > logcat.txt this txt file can then be given to someone for troubleshooting.
adb reboot - reboots the phone
adb reboot recovery - reboots the phone to recovery. (this wont trigger my time mod)
Hopefully this helps you some.
PrinceCorwin
Android Expert
I take it that phone need to be connected via usb to pc when I'm doing this.... with debugging on?
And, yes, it does help... thanx
Usb is the easiest and most reliable way, and yes you need debugging on.
if you're feeling lazy or dont want to connect usb you can enable usb over network in developer options then do 'adb connect ip
ort' ip and port are listed when you turn the box on. This gives you all the same adb commands as usb. But its unreliable and I always get freezes when the screen turns off like this.
IMUcarmen
Android Expert
nice post. I must say you have become a pillar of this community yoinx and it's nice to see you grow in knowledge and to share it with others. It seems you have a passion for this stuff and I wouldn't be surprised to one day see some amazing work coming from you. Thanks for your contributions.
I had the problem with my notifications bar disappearing again and played around a bit more (while on vacation and needed my phone to work for Google Navigation, btw). The root cause appears to be the Enhanced init.d scripts. Once I flashed the rom (pacman RC1) without it, everything worked fine (albeit, without the better performance and battery life).
I didn't have enough time to see if it was the init.d scripts themselves or the V6 Supercharger settings (more likely culprit, I would imagine). Perhaps it's because I haven't had the time to try patching my services.jar with ZeppelinRox' tool.
Will discuss further if and when I have more info.
For now, this is just an FYI for others have trouble.
I didn't have enough time to see if it was the init.d scripts themselves or the V6 Supercharger settings (more likely culprit, I would imagine). Perhaps it's because I haven't had the time to try patching my services.jar with ZeppelinRox' tool.
Will discuss further if and when I have more info.
For now, this is just an FYI for others have trouble.
I'm interested in what you find. I always flash this with Pac and my kernel each time. Haven't had any weirdness yet.
Status bar disappearing...to me... sounds more like a launcher thing. Personally I use apex launcher. Mines disappeared once or twice when I first started using Pac but that was before any mods.
Really curious what's going on with it though.
Sent from my VS920 4G using Tapatalk 2
I'm pretty much running the same as you are, so there's something I'm doing different that's causing it.
It could be the launcher. I may try the stock Trebuchet to see if that's the culprit.
What makes me think it's something else is that it was running great for about 3 weeks before this started and I've been running Holo Launcher forever (hey, I paid for it and the settings backup & restore easily - may as well use it).
I may try a full wipe/clean install, too - but that's painful.
It could be the launcher. I may try the stock Trebuchet to see if that's the culprit.
What makes me think it's something else is that it was running great for about 3 weeks before this started and I've been running Holo Launcher forever (hey, I paid for it and the settings backup & restore easily - may as well use it).
I may try a full wipe/clean install, too - but that's painful.
actually. The more I think about it. My car only ever disappeared regularly when I run anything over phablet mode in the pa settings.
Are you using tablet mode?
Sent from my VS920 4G using Tapatalk 2
Nope. But now it just disappeared without the init.d scripts loaded.