[Q] Faster boot times? - Galaxy S II Q&A, Help & Troubleshooting

Afternoon Forum
This possibly has been asked before however the search features of Google are insufficient at finding anything related to what I am asking.
Basically, I am looking for, whether it be a ROM or Kernel of Making my GS2 Boot Faster, I have timed my current ROM at 30 seconds, which to me as a bench marker is diabolical.
I remember having a ROM, I believe on my GS1 that made boot time around 8 seconds, I wonder if similar attempts have been tried for the GS2.
I look forward to your replies.

N.E.A.K kernel boots pretty fast. It actually gives the little vibrate, when everything is loaded, before the boot animation is finished.
Sent from my GT-I9100 using XDA

daytones said:
I wonder if similar attempts have been tried for the GS2.
Click to expand...
Click to collapse
#1 bootloader
#2 kernel
#3 init
#4 framework
Most useful thing you can do on a stock ROM is getting a slimmer kernel.
Most useful thing you can do in general is use an AOSP ROM with a slim kernel.

How often are you restarting your phone (and immediately need to use it) that 30 seconds matters?

You're ****ting me ??
You're actually concerned about a 30 second boot ? Sheesh
Only way around that is to run the most stripped back rom/kernel combination you can get your hands on, have no autoruns and basically install no apps on the phone.

MistahBungle said:
You're ****ting me ??
You're actually concerned about a 30 second boot ? Sheesh
Only way around that is to run the most stripped back rom/kernel combination you can get your hands on, have no autoruns and basically install no apps on the phone.
Click to expand...
Click to collapse
Just to quote as can't believe 30 seconds boot to be an issue... To OP you have a smartphone to which is relative to a computer how long does your computer take to boot? How many times are you really having to restart phone? Not questions as rhetorical......
And an 8 second boot on a SP it must have been turbo #ROM

Related

Unexpected reboot / long wake up : kernel, rootfs or build ?

Hello,
I'm running Gingerbard GBX0A on my Rhod100FR and noticed only two minor issues :
1st one, the less annoying :
takes in average 5-7 seconds to light the screen up when i press the power button
2nd one, a bit more annoying
unexpected reboot, last one occured in the middle of a phone call.
I was wondering it this was bugs from the kernel files, the rootfs or the build itself ?
Knowing about that would allow me to test different kernel or rootfs.
Going back to FRX06 would force me to start over configuring the whole system and resintalling the apps, unless there's to change ext2 file or something to switch from GB to FR ?
Cheers
Edit : my current kernel is 1320 dated 5/14
Long wakeup -> kernel.
Reboot -> probably kernel as well, usually a kernel panic causes reboots. Not always the kernel's fault, but the kernel should be able to handle anything without panicing.
Have you tried an older kernel? Some of the newer kernels aren't as stable. I still bundle 1276 for a reason.
Also, please post in the build thread. No need for another thread...
arrrghhh said:
Long wakeup -> kernel.
Reboot -> probably kernel as well, usually a kernel panic causes reboots. Not always the kernel's fault, but the kernel should be able to handle anything without panicing.
Have you tried an older kernel? Some of the newer kernels aren't as stable. I still bundle 1276 for a reason.
Also, please post in the build thread. No need for another thread...
Click to expand...
Click to collapse
Thanks arrrghhh, i'll go back to 1276, it seemed to far away in the past compared to 131x or 1320 and my idea was to take latest.
I've never tried older than 1295 as far as i remember. I'll give a try with 1276.
I created a new thread b/c i was not sure it was related to GB and i didn't to mispost in the build topic ... Admin can close or move
diegolvobanania said:
Hello,
I'm running Gingerbard GBX0A on my Rhod100FR and noticed only two minor issues :
1st one, the less annoying :
takes in average 5-7 seconds to light the screen up when i press the power button
2nd one, a bit more annoying
unexpected reboot, last one occured in the middle of a phone call.
I was wondering it this was bugs from the kernel files, the rootfs or the build itself ?
Knowing about that would allow me to test different kernel or rootfs.
Going back to FRX06 would force me to start over configuring the whole system and resintalling the apps, unless there's to change ext2 file or something to switch from GB to FR ?
Cheers
Edit : my current kernel is 1320 dated 5/14
Click to expand...
Click to collapse
Same issue, it was running great, fast UI, data was fine, I rebooted then the same issues appeared on my next boot>
I just wanted to let it be known, he's not the only one with these issues
I also have this problem of rebooting. its very annoying. I use the FRX06 and wistilt2 kernel. Wats more annoying is when it reboots i cant even use my winmo cos it still keeps rebooting in winmo. anyone know how to fix this pls?
I decided to go back to FRX06 with stock kernel (1276) and without overclocking because i'd like to use it daily instead of WinMo.
Gingerbread is a bot nicer, ans a couple of extr&a fetures, but is alpha - not stable enough to operate daily.
prexzone said:
I also have this problem of rebooting. its very annoying. I use the FRX06 and wistilt2 kernel. Wats more annoying is when it reboots i cant even use my winmo cos it still keeps rebooting in winmo. anyone know how to fix this pls?
Click to expand...
Click to collapse
That one's weird - I've had spontaneous autoreboots to WinMo, but I've never had WinMo itself bootloop.
You might have failing hardware?
Sounds like that battery issue people were experiencing.
Remove battery for a few hours put it in and charge it, then turn it on only AFTER charging.
There's a chip in the battery that needs resetting, this should do so.
Thanks. ur solution has been working so far but i cant be removing my battery for hours every now n then. is there a way to reset the chip on the battery of i just get a new one?
prexzone said:
Thanks. ur solution has been working so far but i cant be removing my battery for hours every now n then. is there a way to reset the chip on the battery of i just get a new one?
Click to expand...
Click to collapse
Well, hopefully this bug doesn't hit you that often. You can avoid it by shutting down before battery hits 0 (though most of the time battery hitting 0 doesn't trigger this).
You can also avoid this by:
*Getting a second battery. When this bug hits your first battery, just boot Android with the second, and then while plugged in, swap in your first battery. I believe it should start charging normally.
*Getting an external battery charger.
Last time I checked, you could pick up 3 third-party spare batteries with an external charger for like 10 bucks of eBay.
i changed my kernel n it fixed it. well not really but it doesnt bother me as much n im happy wit it now but the problem is this new kernel im using drains my battery. idk if its cos of the constant red led light. anyone know a kernel that fixes this? pls post link
prexzone said:
i changed my kernel n it fixed it. well not really but it doesnt bother me as much n im happy wit it now but the problem is this new kernel im using drains my battery. idk if its cos of the constant red led light. anyone know a kernel that fixes this? pls post link
Click to expand...
Click to collapse
Uhm, the kernel I bundle with my packages (1276) is pretty solid. You can grab a newer kernel, but some of 'em are not as stable.
arrrghhh said:
Uhm, the kernel I bundle with my packages (1276) is pretty solid. You can grab a newer kernel, but some of 'em are not as stable.
Click to expand...
Click to collapse
The only black spot i faced with 1276 is hte screen not lighting up when unlocking the device.
That happened randomly, and of course, this is alayhs when yhou need it the most.
I steped up to wilstilt2's 1300 to get rid of this.
Thanks dvs for your work and support.
It's arela pleasure to use the portage everyday.
guys can anyone pls give me the link to the kernel. whether its 1276 or wistilt 1300
If you go to ryannathans' "Intro to Android - SD card" sticky, the link to the kernels is up near the top of the first post - along with many other useful links.
prexzone said:
guys can anyone pls give me the link to the kernel. whether its 1276 or wistilt 1300
Click to expand...
Click to collapse
Here you can find tons of kernels :
http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Wilstilt2 ones available from there maybe
http://forum.xda-developers.com/showthread.php?t=885550&highlight=Wistilt
but link in 1st post leads ot v1321.
i don't remeber where i founf v1300... sorry

Possible fix for random reboots

Okay so I'm not 100% sure if this is a sure fix, but it seems to have worked for myself and my wife. We both were getting random reboots like crazy and it was getting very annoying. I remembered back in my windows mobile TP2 days that a lot of stuff gets stored on the SD card after constant flashing and tweaks. So in order to get a proper flash u normally would have to reformat ur SD card, wipe, wipe, wipe, and then flash ur ROM. That is exactly what I did with my phone as well as my wife's phone. I formatted our SD cards after backing everything up of course. I backed it up on an external harddrive, formatted, put everything back, formatted the phone with a super wipe zip I found somewhere in the development forum, installed a custom stock Rom I have been tweaking and then booted up my phone and have not had a single random reboot since. So as the title says, it is a possible fix. If u try it then please post so that other users can know if it is actually stopping the reboots or if It's just a placebo effect. Thanks and I hope I've helped someone who is extremely frustrated as I was with their 500 dollar phone randomly rebooting.
Sent from my Beastly EVO.. And did I mention it has 3D?
I fixed mine with a buisness card as a shim for the battery lol
atistang said:
I fixed mine with a buisness card as a shim for the battery lol
Click to expand...
Click to collapse
Yeah my battery wasn't loose at all. My phone would also sometimes freeze up and when I rebooted it would just be a black screen. I had to pull the battery to get it working again. I tried the auto brightness fix bit my screen would go black sometimes and rebooting did not fix. I actually had to pull the battery out.
Sent from my Beastly EVO.. And did I mention it has 3D?
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
Truth. I've never had random reboots and the only reboots I've done were solely manual because of these hardlocks from custom kernels.
If only my phone played nicely with kernels...
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
Since we never had this issue with the 4G you think it could just be a borked kernel source from HTC and we are missing some valuable info in it? Or the dual core aspect of it being ours r diff than others being asynchronous, is very touchy to code and adjustments we woulda made on single cores?
Any other of the MSM8660 handsets experiencing this with their custom kernels or is it just ours? If just ours be worth looking at their stable kernel modes source to see difference n what they might be doing differently??
Sent from my PG86100 using XDA App
sgt. slaughter said:
Since we never had this issue with the 4G you think it could just be a borked kernel source from HTC and we are missing some valuable info in it? Or the dual core aspect of it being ours r diff than others being asynchronous, is very touchy to code and adjustments we woulda made on single cores?
Any other of the MSM8660 handsets experiencing this with their custom kernels or is it just ours? If just ours be worth looking at their stable kernel modes source to see difference n what they might be doing differently??
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I'm leaning more towards HTC's screwed up source. As this problem wasn't present in their 2.3.3 source, at least with netarchy's kernel. There weren't nearly as many kernels to choose from but still.
I've heard a few people say the source was either incomplete or messed up somehow. We can only hope that HTC releases an updated software version with a new kernel so that they're obligated to release the source as well, and this time hopefully it will be complete.
atistang said:
I fixed mine with a buisness card as a shim for the battery lol
Click to expand...
Click to collapse
I used a gum wrapper for mine
Sent from my PG86100 using xda premium
I'm having strange issues as well. My phone will sometimes lockup while using it and then it displays the bootanimation and gets stuck on it and I have to battery pull. And it's actually done it once so far while I was sleeping. ROM is stock but I just decided to finally update it to 2.3.4 so I flashed dastin1015's "[ROM][Sense 3.0][2.3.4][Nov. 3, 2011] Stock 2.08.651.3 Deodexed w/ Hotspot and Beats" over it and rolled. Before I flashed, I nandroid'd, Titanium'd, and My Backup Pro'd. I then booted into TWRP and flashed and rolled. I didn't clean reset before or after because I was worried about losing texts and whatnot. That seemed to go well so I flashed chad.goodman's mildAnthraX and also updated my PRI. And keep in mind I haven't touched the clock settings or voltage. Any ideas? I was considering flashing stock kernel and seeing if that fixes it. If not, then I imagine I will have to do what I least want to and clean reset my phone. Will the logcat help identity the problem here?
Lucentio said:
I'm having strange issues as well. My phone will sometimes lockup while using it and then it displays the bootanimation and gets stuck on it and I have to battery pull. And it's actually done it once so far while I was sleeping. ROM is stock but I just decided to finally update it to 2.3.4 so I flashed dastin1015's "[ROM][Sense 3.0][2.3.4][Nov. 3, 2011] Stock 2.08.651.3 Deodexed w/ Hotspot and Beats" over it and rolled. Before I flashed, I nandroid'd, Titanium'd, and My Backup Pro'd. I then booted into TWRP and flashed and rolled. I didn't clean reset before or after because I was worried about losing texts and whatnot. That seemed to go well so I flashed chad.goodman's mildAnthraX and also updated my PRI. And keep in mind I haven't touched the clock settings or voltage. Any ideas? I was considering flashing stock kernel and seeing if that fixes it. If not, then I imagine I will have to do what I least want to and clean reset my phone. Will the logcat help identity the problem here?
Click to expand...
Click to collapse
Ur on the exact setup as I am. Kernel and ROM. Stock kernel still did exactly what u mentioned above as well. After formatting my SD card I have yet to have it happen. It's been about 8 days since I formatted. After reading the posts I don't think formatting my SD card is a fix, but I too am leaning towards HTC kernel being messed up. I think sooner or later my phone is going to do it. My phone was doing exactly as u stated. Booting into the splash screen and not going past it. On some occasions my phone would either freeze up or just go black. The hard buttons would light up but not my screen. Hope this gets figured out soon.
Sent from my Beastly EVO.. And did I mention it has 3D?
Mine resets between the hours of 71-80 of being on
I'm having the same problem and I do not know how to solve it! I am so close to selling my Evo 3D and going to the SG II.
I have ran CleanRom and currently running Fresh. I have tried Mwalts kernel, Bcblends kernel, and stock kernel from Fresh stock. No matter what I tried, my phone ALWAYS resets between the hours of 71-80 of being on.
The reset happens only when I try to turn on the phone. It turns on, off really quick, then I hit the power button again, the lock screen comes on, then the phone resets. It is getting really annoying as I love having stability and this phone isn't stable at all.
Any ideas? I have exhausted everything I know. I'm running the exact same programs as I have on the Evo 4G and since it is resetting at the same hours always at the same time on different ROMS/Kernels, I'm pretty sure its not app issue. I also tried changing between the 3 radios and no change there. The only other option now is to do a fresh install of Fresh and use it stock and see what happens.
Rytt
Try setting min cpu freq to something other than 192000, I use 384000 sleep and 482000 wake. I used to have a reboots and freezes but saw that advice somewhere and gave it a shot. Presto no more issues. Battery life is no worse for wear either. Not saying this will work but worth a try.
3VO Sent
ifly4vamerica said:
Try setting min cpu freq to something other than 192000, I use 384000 sleep and 482000 wake. I used to have a reboots and freezes but saw that advice somewhere and gave it a shot. Presto no more issues. Battery life is no worse for wear either. Not saying this will work but worth a try.
3VO Sent
Click to expand...
Click to collapse
already try that
no luck it still keep rebooting while screen off
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
my cdma-sense kernels having issues????
RLS9 and RLS14 should be 100% stable - and not based off of htc source
(on pre 2.17 based roms)
i think freeza gave rls9 his seal of approval for stability.. if memory serves correctly
...on my phone i use (not my test phone) im @ 242 hours uptime on rls14 and warm 3.5 r116
...no im not trolling, just looking for feedback
chad.goodman said:
my cdma-sense kernels having issues????
RLS9 and RLS14 should be 100% stable - and not based off of htc source
(on pre 2.17 based roms)
i think freeza gave rls9 his seal of approval for stability.. if memory serves correctly
...on my phone i use (not my test phone) im @ 242 hours uptime on rls14 and warm 3.5 r116
...no im not trolling, just looking for feedback
Click to expand...
Click to collapse
He said that before you found the magic fix I'm pretty sure. Notice that was back from November. Lol
Sent from my PG86100 using xda premium
Huge Thanks
thank you so much for sharing your information my evo 3d was rebooting about every 30 min and i have just been dealing with it because i had took my evo4g into the sprint store because it was rebooting aboutevery 5-10min so they looked at it and couldnt figure it out so the gave me the evo3d for free and i put the sdcard that was in my evo 4g into my evo3d without having any idea that it was the sdcard causing all of my problems so the same thing started to happen to my new evo 3d started off about every day and eventually started to reboot every 30min and i just decided that all htc devices were like this so i have been dealing with it but today i said enough is enough and looked online and saw this thread and wiped my sdcard and sure enough no reboots yet its been about 3 hours so i think its fixed
i cant thank you enough i think it got corrupt from all of the flashing i was doing
son of a ***** right as i was about to hit post the mother ****er rebooted so its not my sdcard after all should i take it in to sprint what do you think ahhh i should have never posted anything it was going so well FML!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ps hboot 1.4 is the **** no more going to the computer to flash a rom stupid hboot 1.5
I've sometimes had trouble running custom kernels (reboots and strange behaviors) that were fixed when running the stock kernel. But, the stock kernel leaves a lot to be desired in overall performance, so I continue to kernel hop. But, from my lurking on the different ROM forums, it seems that stock is the way to go for stability at the sacrifice of performance.
I had problems with evo rebooting and that in a loop. Very annoying. For that i've changed several roms just to find out that it could probably be because of widgetsoid.
At first the rebooting after some time of use, 1-2 days. And if flashing a different kernel than the one with rom. I was going mad, the last reboot or series of constant reboot after the evo has turned itself on, has occured after i set the brightness to lowest value, it was late so i wanted a darker screen. Interesting it when i set lowest value in system or via leedroid tweaks in widgetsoid widget popup - value im at 12 %. Maybe i got the restarts because i went below 12? Since my brightness im above 12 in widgetsoid and minimal in system, my evo didn't reboot a single time.
Currently i'm at shawn3d rom. Later i'll try some other kernel and rom again and see if the reboots occured.
U get random reboots while using any brightness widget with custom roms. I've narrowed my 3d threshold for the reboots to be anything less than 5%.
No reboots if kept at or above 5% for me...
Sent from my PG86100 using Tapatalk 2
i have had success after formatting system/data/cache to ext4 in the ext4 recovery, i had random reboots and lockups while using twrp and not formatting to ext4, (in all honesty i doubt the twrp was too blame)

Boot time?

Everytime i boot my photon it stays on the word "now" for 30 seconds? Is this ok?
Sent from my MB855 using xda premium
Sadly I believe it is normal. My photon (which is rooted) takes 45s-1min to boot up which is quite pathetic I believe. I can't even show off my phone because most people start making fun of my phone when they see the word now for 30 seconds :/
cm 7.2 boots up for me pretty quickly defenitaly faster then the other roms i have played with
I guess i have to ask... 1) why would you turn your phone off before showing it to someone?
2) how often do you reboot where boot time is an issue? i reboot once a month tops. (unless i find myself having to switch batteries, which is also rare)
now i am just guessing here but i bet he wants to show off a custom boot animatiion.
Change your initial boot image, that way they aren't staring at the word now. its a cheap solution, but I did it and it beats the default.
On a side note, I don't like how long it sits on that screen, either.
Sent from my 1.3 OC'd CM7.2 Electrify.
I found out why it takes so long to boot... this is because it loads security platforms, features, applications, firewalls, etc. + it's just slow in plain english.
Sent from my Epic Touch running Blazer Rom via xda premium
Blur has a lot of services that start on boot. Significantly more than android source and as such takes a little longer to boot. As someone else said CM boots fast and that's due the less work to do on boot. I made myself a blur rom that was stripped of services and apps I don't use then deodexed, zipaligned for better ram usage, PNG optimized the system and framework to reduce the overhead and the end result was my phone wouldn't make it through the stock boot animation before it started painting the screen.
My goal was to just see how certain blur services played with others but it didn't take long for me to notice I had inadvertently increased boot time significantly over stock.
Cm7 and cm9 are rockets, fly and boot quickly!
Sent from my MB855 using xda premium

Samsung galaxy player 5.0 (Few random questions)

Hi all,
I was looking into overclocking and underclocking the hummingbird processor withing my galaxy player 5.0
The overclocking is obviously for fun (I know the risks to the CPU and battery), the uderclocking is more so for power management.
I so far have not been able to go past the 1 GHz on the stock kernel.
Has anyone else tried this on stock/custom kernel and gotten any descent results?
I'm intrested in your expierences.
---------------------------------------------------------------
I'd upload the 5.0 compatible kernel and ROM into my device to use it and try it out; I found it on this sight, but I have been stuck on attempting to backup my current Kernel and ROM, as I do not want to loose it.
(I'm trying to do it "manually" with a program that was meant for something totally different, its interesting on the parts of data I could dump, but nothing is usable).
But aside from that, I have been trying different things with just the root on stock kernel and ROM, and I have found a few things that were fun to play with like the droid wall and an SD speed up...
-----------------------------------------------------------------
honestly I do not see anything else I need/can use the root for right now...
An I missing something? Is the android that open...?!
(This is coming from someone who worked and worked to unlock an iPod touch and turned it into an iPhone and partially into a pocket PC)
I remember the kernels name: Entrophies Kernel (idk how to spell it)
(Its on this forms sight in a different category somewhere)
-I'd use it, but first I'm putting back the stock charging and battery management, I personally do not like the settings he has, Li-Ion Polymer batteries like a complete charge, and a steady charge with a taper at the end...
-----------------------------------------------------------------
Any thoughts and experiences on anything I had not asked about is also welcome.
Everywhere I look for information about this device, I keep finding random one posts with questions and never any answers.
Also, people seem to not know about this device, and also not know how to modify and back its data up, including me with my failed atempts... o_o
Ultimately, if I can figure enough out about this device, because everything I have found so far is scattered about online, I'd like to make a post and dedicate it to the galaxy 5 player eventually, with up-to-date (or as close as possible) info on many things. Because thats the biggest problem I see, nothings ever centralized.
If you have root then This should work on your 5.0 player. I just installed it (stock) to try after seeing your post and i already have my 5.0 overclocked to 1.1ghz
Tegrak Overclock is a great utility to over and under clock your CPU.
[root]How to back up your current kernel U.S 5.0 YP-G70
Download MDump Partition dumper v0.02: link in signature!
Open MDump on your device and select "mmcblk0p11"
Rename the file: mmcblk0p11.mdump -> zImage
Touch "Start Dump"
Move the file to a linux machine and put it in a tar ball. (example command: tar -H ustar -c zImage > kernel.tar)
You now have a backup of your stock kernel which you can reflash using odin! (kernel.tar)
Update: I just noticed that you wanted the ROM too, it's mmcblk0p13. You can just dump that as well; rename it "factoryfs.rfs" and include it in the tar ball.
I plan on eventually adding support for clocking at 1.2 GHz and voltage control - I've just been busy with some issues with my I777 kernel (SoDs... ) and busy with real life in general.
I won't be just grabbing rumirand's patches as his use a slightly different approach than the netarchy-style code I prefer.
wow thanks everyone for the fast replies, I'm replying to each post in order, I added quotes to show which ones I am replying to.
murph5525 said:
If you have root then This should work on your 5.0 player. I just installed it (stock) to try after seeing your post and i already have my 5.0 overclocked to 1.1ghz
Click to expand...
Click to collapse
Thanks for the link, I added the app to my device, and overjoyed, I clicked on the 1.3 GHz setting and applied it!
I do not see much of a difference as my device never lagged, if that, before.
I tried a few benchmark utilities, and it seems to surpass almost all the single core CPU phones I looked at...
dunca123 said:
Tegrak Overclock is a great utility to over and under clock your CPU.
Click to expand...
Click to collapse
I was playing with the underclocking features, and my already 2-2.5 day battery looks like it will last another day...lol
Meticulus said:
Download MDump Partition dumper v0.02: link in signature!
Open MDump on your device and select "mmcblk0p11"
Rename the file: mmcblk0p11.mdump -> zImage
Touch "Start Dump"
Move the file to a linux machine and put it in a tar ball. (example command: tar -H ustar -c zImage > kernel.tar)
You now have a backup of your stock kernel which you can reflash using odin! (kernel.tar)
Click to expand...
Click to collapse
I was not expecting this... Thank you very much, you just saved me a lot of trouble!
I'm trying this in a few days, I've got a couple tests to study for this week...
Entropy512 said:
I plan on eventually adding support for clocking at 1.2 GHz and voltage control - I've just been busy with some issues with my I777 kernel (SoDs... ) and busy with real life in general.
I won't be just grabbing rumirand's patches as his use a slightly different approach than the netarchy-style code I prefer.
Click to expand...
Click to collapse
I really like your kernel, you have done a nice job with it!
I was just wondering if you are keeping a single serries of the kernel or one with the modified power management, and one without?
Reason asking, is that I'm an EE, and I know a few people who work with battery management, and they all tell me the Li-Ion Polymer batteries like to be fully charged. I'm just curious as to your approach/reason behind stopping the charge just short of the top?
I like your selections for the custom charging with the kernel for quicker charge times... when I eventually get your kernel onto my device, I'm going to see if I can change settings while its installed, kinda like a power charge for when needed, and a regular charge for over night for less stress...
-------------------------------------------------------------
idk, I'm new to android, I've been stuck in i-Devices lingo for a long time and I'm slowly figuring this android stuff out...
So far, the only real thing I actually needed root for is overclocking and underclocking, droidwall, and tor... I like how open the system is (aside from the kernel/boxroom seeming to be locked when my friend tried a program called adb on it the other day).
Just curious, anything fun I can do with a custom kernel/rom? the only thing I see it can do so far from searching a few links is themes? idk, i need to look into it more...lol
I came across running ubuntu linux on the device through a vnc, even though its installed on the device... I was thinking of trying that if it looks like its ok...lol
I'm just a bit excited, I have this thing that can do so much, but idk what to do with it other than using it as a free wifi phone so far...lol
zBusterCB87 said:
I really like your kernel, you have done a nice job with it!
I was just wondering if you are keeping a single serries of the kernel or one with the modified power management, and one without?
Reason asking, is that I'm an EE, and I know a few people who work with battery management, and they all tell me the Li-Ion Polymer batteries like to be fully charged. I'm just curious as to your approach/reason behind stopping the charge just short of the top?
I like your selections for the custom charging with the kernel for quicker charge times... when I eventually get your kernel onto my device, I'm going to see if I can change settings while its installed, kinda like a power charge for when needed, and a regular charge for over night for less stress...
Click to expand...
Click to collapse
I'm an EE myself. That's odd - all information I've ever seen says that Li-Ion and Li-Po batteries do NOT like to be fully "topped off" or "trickle charged".
I'll try to dig up my sources later, but, from memory:
Overcharging them can result in metallic lithium plating out, which leads to permanent capacity loss. This is why all Li-Ion chargers stop charging once current drops below a certain rate in the constant-voltage phase. In the case of almost every Samsung I've ever used, CPU/power usage counts against the charge current limit - so I'm REALLY paranoid about the charger terminating properly, which is why I make it cut off earlier, as a way of offsetting some of the stress on the battery that the charging rate bump creates.
Also, Li-Ion batteries stored at maximum charge will lose capacity far faster than ones stored at around 50% charge. (This is why almost all new devices have batteries only 50% charged or so.)
I may eventually add a feature to disable the increased charging rate at runtime, however, in the case of the Galaxy Player:
It has a 2500 mAh battery, so 800 mA is actually still less than C/3 charge rate for the battery, whereas on most Galaxy S phones, they charge at 600 mA for an (approximately) 1650 mAh battery, making charge rate slightly more than C/3.
I also reduce charge rate below stock near the top - the technique is inspired by this: http://www.engadget.com/2011/02/20/apple-patent-application-points-to-denser-batteries-improved-ch/
idk, I'm new to android, I've been stuck in i-Devices lingo for a long time and I'm slowly figuring this android stuff out...
So far, the only real thing I actually needed root for is overclocking and underclocking, droidwall, and tor... I like how open the system is (aside from the kernel/boxroom seeming to be locked when my friend tried a program called adb on it the other day).
Just curious, anything fun I can do with a custom kernel/rom? the only thing I see it can do so far from searching a few links is themes? idk, i need to look into it more...lol
I came across running ubuntu linux on the device through a vnc, even though its installed on the device... I was thinking of trying that if it looks like its ok...lol
I'm just a bit excited, I have this thing that can do so much, but idk what to do with it other than using it as a free wifi phone so far...lol
Click to expand...
Click to collapse
Well, on many Android devices, root is needed to kill carrier bloatware. It happens that wifi-only non-carrier-branded devices tend to be less mangled and require less debloating. (Often none...) I've frequently run stock system firmware with custom kernels on wifi-only devices for long periods of time - but carrier-mangled devices almost always need an immediate debloat.

[Q] How often is too often to have SGS2 crash?

I wanted to see if I can post something without getting ridiculed. Seriously doubt that now cause I accidentally posted this in the general Q&A first and did not know how to move it or delete it so i am posing again here. Hopefully a moderator can just take care of that stray posting I made in the general area.
I am on my second ATT SGS2. First one had a GPS issue. Tried everything and finally convinced ATT warranty services that the problem was hardware. They said they would advance replace the handset. So I got it back to stock in every way except the flash counter,this was in December so long before I was aware of mobile odin. Flash counter was at about 12 when I was done trying different ROMs,mostly just try to get the GPS to work. It was in perfect shape, bone stock except for the counter. I cannot imagine I will have an issue, but has anyone ever heard of someone getting charged on a return to stock phone that had a flash counter above stock? Ill update once I know for sure the outcome.
My real question, does everyones SGH-I777 crash on occasion? If so how often? I so happy with the current code that is running on the phone with the exception that it sometimes sleeps and wont wake up, and sometimes it just plain crashes hard, locks up and has to be hard rebooted. Usually this happens about twice a day one or the other. I wiped before installing current kernel. The only reason I am not stock is cause I wanted the CKK6, 2.3.6 update to work and to keep root privaledges, but also needed my wifi cause ATT is throttling me down to dial up speeds when I reach 2GB. So wrong!!! Anyway thats another thread.
I loaded shostock with siyah kernel 2.6.35.14. after wiping everything including both caches. The GPS is solid now, phone is fast, battery is egh, I keep a charger with me... but it crashes hard from one to three times a day. Locks up playing tunes, or wont wake up with out being plugged in or hard booted. Do I have another defective handset or should I just go back to 2.3.4 and UKH7 or should I just deal with it and consider the crashes, "excellent opportunities to reboot."?
Thanks for the all the hours of fun, u know who you are.
I honestly don't remember my phone crashing at all. If it's crashing, it aint stable. Did it crash when it was stock?
yeah I mean duh right? The new handset was updated, rooted, downreved and flashed with the custom rom before it was put under any load, so I do not know if it would have crashed before. I have wiped, re downloaded, checked with hashtab and re flashed my current kernel, so it seems like it has to be hardware, again... ugh. Especially since no one else is having issues with shostock and siyah. I wonder how hard it is going to be to get warranty services to replace the second phone in 3weeks!? Lol.
Try going back to stock and run it for a couple hours to see if it still crashes. If it still crashes then more than likely hardware issues.
Sent from my SAMSUNG-SGH-I777 using xda premium
If it's crashing on stock without SetCPU to set a screen-off profile, you have a hardware problem.
I haven't had a crash, freeze, or spontaneous reboot in ages - despite running kernels that a few others have reported stability problems with (and I have effectively halted my kernel until I can get to the bottom of those reports...)
Too often is when it happens regularly, period.
I'm running CyanogenMod 9 and have almost no crashes, despite it being experimental.
Sent from my GT-I9100 using XDA App
I reverted to stock last night shortly after posting this. Ran fine until re loaded SHOstock v1.9.2-UCKK6. It is not "crashing" but it will go to sleep and not want to wake up again. I can sometimes plug in the charger and that will wake it up but other times I have to hard reboot. So no more crashing, but will not wake from sleep about 10% of the time. Not a huge deal, but its a bit weird because I know that the code I am running is ok, and it seems the hw is ok, so... not sure why this is happening. Anyway thanks all for your suggestions etc.
silashj said:
I reverted to stock last night shortly after posting this. Ran fine until re loaded SHOstock v1.9.2-UCKK6. It is not "crashing" but it will go to sleep and not want to wake up again. I can sometimes plug in the charger and that will wake it up but other times I have to hard reboot. So no more crashing, but will not wake from sleep about 10% of the time. Not a huge deal, but its a bit weird because I know that the code I am running is ok, and it seems the hw is ok, so... not sure why this is happening. Anyway thanks all for your suggestions etc.
Click to expand...
Click to collapse
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
I had the same problem using the latest siyah kernel, but never with entropy's. I would suggest flashing a new kernel.
Sent from my GT-I9100 using Tapatalk
1. To answer the OP question, I have experienced ONCE that was when I tried to run the Andy's TI-83 emulator on my virgin stock ROM. The result is either my fault or the application isn't compatible with the running OS.
2. With bone stock, it shouldn't crash at all. If it does, RMA.
3. If the owner(s) have "some fun" around it such rip it off, hack it up, install different kernels, different ROMs, ...... then please DO NOT complain the device is suck.
I've seen a lot of knuckleheads who tried to mod their devices, screw them up then claim "they're suck".
dandrumheller said:
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
Click to expand...
Click to collapse
Thanks this sounds like a plan. I have to do something things have gotten worse. About 3 out of ten times I go to put the phone to sleep now, instead of blinking out the phone takes a screen shot. My fingers are no where near any of the other buttons and it takes a screen shot over and over when I press the power button. I have to move around from screen to screen, hit the home button and then hit the power button to put it to sleep. Weird stuff, could be worse though. Did I say that I thought the phone sucks? I thought I read in one of the replies up there something like that. Aside from the GPS issue that was hardware related, and problems I have brought on myself because stock wasnt good enough, this is hands down the most awesome piece of electronics I have ever owned. iPhone smyphone. I just need to find the perfect turbo charged, rooted but as stock as possible configuration that is stable and I will be set. I really like where I am, hopefully the kernel you suggested does not change much but fixes the problems. Thanks again all.
Grab one of Entropy's DD Kernels and flash it with CWM. I'd suggest getting one from Jan or earlier. His latest ones are trying to track down a issue.
dandrumheller said:
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
Click to expand...
Click to collapse
axis01 said:
Grab one of Entropy's DD Kernels and flash it with CWM. I'd suggest getting one from Jan or earlier. His latest ones are trying to track down a issue.
Click to expand...
Click to collapse
Ok the noob is going to shine through here... but you say to flash with CWM. With my current config, when I enter recovery mode I am taken to the siyah kernel recovery console. Are we talking the same difference here, and when I go to flash as you mentioned can I do so with Siyah recovery or shall I flash with something that will give me back cwm first and then flash the config that you mentioned in your reply?
silashj said:
Ok the noob is going to shine through here... but you say to flash with CWM. With my current config, when I enter recovery mode I am taken to the siyah kernel recovery console. Are we talking the same difference here, and when I go to flash as you mentioned can I do so with Siyah recovery or shall I flash with something that will give me back cwm first and then flash the config that you mentioned in your reply?
Click to expand...
Click to collapse
That recovery will work. After installing the DD kernel, CWM will change.
Sent from my Galaxy SII
I get a crash here and there everyday...
Sent from my SGH-I777 using xda premium
Have only ever crashed while messing with voltages or clock speeds. if it's crashing something is wrong.
A few people's phones just do not play well with Siya kernal. Most of those people flash Entropy's DD and the sleep deaths go away... give it a try, I bet it will help!
Mine crashes a few times a day if I'm cycling through a lot of apps or installing things. (Stock+root) the other day my phone would crash anytime I tried, to watch a video in web browser. (Either mxplayer or phone)
Sent from my SAMSUNG-SGH-I777 using XDA App
T90 said:
A few people's phones just do not play well with Siya kernal. Most of those people flash Entropy's DD and the sleep deaths go away... give it a try, I bet it will help!
Click to expand...
Click to collapse
With Siyah I crashed more often than I do know with DD...
Sent from my SGH-I777 using xda premium
Ok flashed the DD from 01-30-2012
Thanks for all the help. I will post again when I know if things are better.

Categories

Resources