Hi all,
I wanted to post this question in the Endymion 3.4 thread but I don't have enough 10 posts.
My phone has been rooted (via htcdev unlock) and installed Endymion 3.4. But since then, it reboots very frequently. I noted that the most of times it reboots at the moments the screen times out. I had to set the screen to not times out and now it seems not to reboot randomly.
When it reboots, it returns directly to the "HTC quietly brilliant". So I think this is a soft reboot and this is a software problem.
I need help from you all. Thanks.
d_t_kien said:
Hi all,
I wanted to post this question in the Endymion 3.4 thread but I don't have enough 10 posts.
My phone has been rooted (via htcdev unlock) and installed Endymion 3.4. But since then, it reboots very frequently. I noted that the most of times it reboots at the moments the screen times out. I had to set the screen to not times out and now it seems not to reboot randomly.
When it reboots, it returns directly to the "HTC quietly brilliant". So I think this is a soft reboot and this is a software problem.
I need help from you all. Thanks.
Click to expand...
Click to collapse
What are your CPU settings?
I mean the awake and sleep CPU settings, clockspeeds, governors, and undervolting settings...?
All settings related to CPU are default:
Deamon controller: not checked
Awake:
max speed: 998400
min speed: 245000
governor: ondemand
Asleep: same as above
UV control: 0
(I had once tried to changed to -25 but not help)
IO scheduler: deadline
Apply on boot: not checked
d_t_kien said:
All settings related to CPU are default:
Deamon controller: not checked
Awake:
max speed: 998400
min speed: 245000
governor: ondemand
Asleep: same as above
UV control: 0
(I had once tried to changed to -25 but not help)
IO scheduler: deadline
Apply on boot: not checked
Click to expand...
Click to collapse
Enable the Daemon Controller,
Set the Governor to Reaper (both sleep and awake)
Keep the speed settings as 245 and 1075 for both sleep and awake,
Set UV control to +25 (yes, the one above the zero),
Enable apply on boot,
then Reboot.
See if that solves the problem.
Provide more info. What is your Hboot version and radio?
Hi there. After many test (with default CPU settings or with those enigmaamit mentioned above) I found that the priblem is related to the screen when it times out.
In Endymion 3.4 (I've never tried other versions), when the screen times out, it dims out darker and darker then turns off.
I usually set the screen brightness to 10% when being indoor, and AUTO when being outside. And I found that when setting brightness to >10%, everything is fine, but when I set to 10% (not tried lower), the phone will reboot when timing out instead of turn off the screen.
I feel that there is some assumption in Endymion that the screen brightness is > 10% when dimming out.
Please help me to check if your phone is also like this if you are running Endymion 3.4.
Sent from my HTC Desire S using XDA App
Nope. Set the brightness to minimum and no problem here.
In RCtweaks under display/autobrightness are you set to default?
What is your Hboot?
Did you made a full wipe?
Are your all partitions ext4?
- RCtweaks autobrightness: yes, default
- HBOOT: 2.00.0002
- Full wipe: yes, all wiped before installing ROM
data/factory reset, cache, dalvik cache, battery stats
- Only sdcard is fat32, all others are ext4
I have tried to reinstall Endymion several times but still the same thing.
Does anyone have the same problem with Endymion like me here: phone reboots on screen time out when setting brightness to <10% ?
Sent from my HTC Desire S using XDA App
d_t_kien said:
Does anyone have the same problem with Endymion like me here: phone reboots on screen time out when setting brightness to <10% ?
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Nope... can't say i do. Why don't you PM lowveld and ask the great one himself?
I did not have enough post count to send PM. Now it's ok, I have sent lowveld a message.
same here
I can confirm the exact same behaviour. It's while reading ebooks with Moon+ Reader when I manually slide down the backlight to below 10%. In this cases the phone reproducable reboots at screen timeout. If the brightness is higher than 10%, everything is fine.
I think normally the screen brightness never goes beyond 10% as this is the darkest possible level anyway (values below 10% are not going darker). Even the normal manual brightness slider stops at 10% at its lowest position. But programs like ebook readers with their own brightness settings alow to drop lower (even if it doesn't have any effect).
This problem was not there at Hyperion. I switched to Endymion 3 days ago. And this was when the issue first appeared.
I set Moon+Reader to never screen time out now.
Thanks for your confirmation. I did not get reply from lowveld. But since last time, I didnot set brightness too low and everything is working fine.
same here. But i only have this problem with the CRT on/off animations... No animations = no reboot
Related
What scaling setting do you use, maybe you have custom profile?
I personally use 'ondemand', but I was thinking.... It would be nice to have a smart scaling setting, based on the amount the phone is used, screen brightness and the battery temperature, etc.
Sent from my X10a using XDA App
Hi.
I've set mine at 576 max and left minimum at 245, scaling is on demand, and have set a profile for screen off at 245 for both. I've left the advanced screen as I don't have a clue what any of it means lol.
Non
Used it at first when got rooted. still on root BA23 firmware and im very happy with the current setup. I left the processor to operate the way it want to do.
Dont take me wrong, its a great software, everything is depends on overall apps you are running. and its unique to your phone, check its really necessary.
After-all we are talking about android, not windows.
I want to know the best setting also I had some custome profiles (after reading in a post on XDA) but phone got slow, laggy & sometimes call drop. Then i deleted all custome profiles
Mano1982 said:
I want to know the best setting also I had some custome profiles (after reading in a post on XDA) but phone got slow, laggy & sometimes call drop. Then i deleted all custome profiles
Click to expand...
Click to collapse
I had that problem once. But i think it is a OS bug than the SetCPU bug itself. You should re-root your fone and set profiles one more time. It will help you save a lot of battery
My setting (following someone on the net)
- Fully chage (AC/USB): 998/245
- Screenoff: Max: 348 Min: 245
- Battery <25%: Max: 348 Min: 245
Ok Dundun, I've set profiles again same as yours let's see how it workd
Just came across this thread for decent SetCPU setting: http://forum.xda-developers.com/showthread.php?t=734886
I am having a problem with my screen staying on long enough to unlock it. It also happens when in a call and I need to push a number. When I push power to unlock the screen, it only stays on for a fraction of a second then goes out. The bottom row of buttons stays light and will vibrate if i push them but nothing happens. It will do this over and over until finally it lets me unlock the phone. Also when I am on a call and remove the phone from my ear the screen does the same exact thing. Stays on only for a fraction of a second and so on........... This is my third G2X and my first one did this as well. I don't use any kind of lock screen app such as widget locker and when I do try it, it still does the same thing. Anyone have any Ideas???
Are you using SetCPU? I had a similar issue when I set my "screen off profile" in SetCPU to 216 max and 216 min with a priority of 100. I changed it to 312 max 216 min. Now no issues.
Battery seems about the same.
jcbofkc said:
Are you using SetCPU? I had a similar issue when I set my "screen off profile" in SetCPU to 216 max and 216 min with a priority of 100. I changed it to 312 max 216 min. Now no issues.
Battery seems about the same.
Click to expand...
Click to collapse
I do, and I use the same profile you mentioned. I am going to switch it now and try that. Thanks for your quick help!!
(Edit) Yes, that seems to be the culprit. I froze SetCPU for now and problem solved. Now I will change the settings to 312-216. Thanks Again
Happy to help. I am new to this android stuff, but I am beginning to figure things out through trial and error.
Hey guys,
I noticed another issue but don't know if it's rom-related.
When I push the power or volume-button to wake up the device, it sometimes takes 3-5 seconds until it wakes up and display powers on.
It seems that this issue is showing up more often than a few days before. I would say it happens every 5th to 8th time I wake up the device. :-/
Can anyone confirm this?
Check your minimum Clock speed i.e. in SetCPU or NoFrills what is the minimum speed the processor can run at?
If it's very low then increase it a little.
Minimum CPU-speed is 384Mhz set through SebastianFMs kernel I think. Will NoFrills overwrite kernel settings for testing?
Hello. I have been a "lurker" on these boards for roughly 2 years. I have rooted, flashed and installed custom ROMs, bootloaders, recoveries and radios on the following devices:
Samsung Vibrant (original samsung galaxy S)
HTC Amaze (a.k.a Ruby.... wire trick and all)
ASUS Transformer 1 WiFi Only model ( a.k.a TF101)
Anyway, I am posting for the first time. Because of this, I cannot post directly to the development thread involved with my issue. Never the less, here it is:
I am running RaymanFX's JellyBean Cyanogen 10 V6 (STABLE) with Rayman's custom kernel on my TF101. I was running a Revolver ICS ROM prior to installing this JB ROM.... or Revolution HD, I can't remember... anyway
I am having an issue with the TF101 either 1) involuntary reboot or 2) freeze/lockup/crashing after wakeup from sleep mode and complete loss of WiFi radio.
Yes, I have extensively searched the development threads and I found posts related to this one, but none of them solve the issue and I also noticed a few people have this same problem but have no known solution.
I have wiped and done clean install of this ROM several times always with the same result. I also flashed LiquidSmooth (Rayman worked on this ROM and his kernel is cross compatible) to see if it was ROM-related and discovered it is not.... this is a kernel issue. My wipe procedure is:
Factory Reset (cache/data wipe)
Run Superwipe script for TF101 from Android Revolution HD thread (format cache, data, etc...)
Wipe Dalvik Cache
Flash ROM
Reboot
Flash GAPPS (latest version linked on Cyanogen thread from goo.im)
Reboot
Everything runs buttery smooth and flawlessly, HOWEVER.... "Wake on WiFi fix" solution on RaymanFX's post does not work for me.
The "fix" is to designate WiFi Always On during Sleep. Changing this setting doesn't stick... WiFi still sleeps even with this setting corrected. With one caveat... Changing the setting to "Never" and then modifying WiFi Idle Timeout to "3 hours" and then changing the Keep WiFi on During Sleep to "Always" will delay the WiFi from idling out temporarily unless the tablet is in Sleep longer than 3 hours.... at which it idles anyway and causes a crash or reboot.
Secondly, I have discovered that the CPU Frequency setting under Performance could be part of the reason it crashes. I have "Set on Boot" enabled. Setting a CPU Frequency, regardless of governor, above 1408 Mhz WILL cause tablet to lockup/crash upon wakeup from Sleep as the processor jumps to maximum set frequency. If maximum frequency is set to 1408, it will stutter and lag out the system forcing it to become unresponsive to touch commands but "stable" and useable.... albeit very laggy. If the Max Frequency is set to 1200, it will NOT reduce the maximum frequency set for the CPU unless tablet is put into Sleep mode and then woken again.... it will constantly cycle between the "old" maximum frequency setting and the "new" maximum frequency setting (observed by monitoring the frequency in the Performance setting screen after changing from a higher max frequency to a lower max frequency and staying on the menu screen and allowing the CPU to "settle" without any user input).
I really like this ROM and I hate to give up on it, so I'm hoping someone out there will have an idea about what I can do to make this work... or at least recommend a different kernel that will work with this ROM and also has a way to change CPU frequencies and governers.
Any ideas?
Hi,
I have tried different rom + kernel:
cleanrom
ultra fast rom: http://forum.xda-developers.com/showthread.php?t=1901784
untermensch kernel: http://forum.xda-developers.com/showthread.php?t=1892326
and still can't oc the cpu to something higher than 1.3ghz
I used the No-frills CPU as well as the antutu cpu master (free version)
for the No-frills cpu, whenever I set the CPU speed to something high (ie. 1.6ghz max and 102mhz min), checked apply on root then apply, it worked fine for a while, but later on when I open no-frills cpu, th e current max and min will reset back to 1.3ghz and 102mhz.
Governor and I/O scheduler is fine though.
Sounds to me like u need to check start on boot..i havent oveclocked mine yet but option should be there where u select governors and such...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Of course i have checked that it just didnt work
Give Voltage Control a try. It gives you the options to apply on boot or init.d. I use the init.d setting because the phone boots quicker. I had that problem with CPU Master in the past while running it on my phone.
Sent from my LG-LG855 using Xparent Green Tapatalk 2
Will do, however i dont think it's the reboot problem. The problem was, when i set the cpu speed to 1.5 or 1.6 its works fine for an hour or so ( i closed the cpu app, reopen it and the curent seed got set) but then an hour or so, it got resetted back to 1.3 without rebooting the device
redjersey said:
Will do, however i dont think it's the reboot problem. The problem was, when i set the cpu speed to 1.5 or 1.6 its works fine for an hour or so ( i closed the cpu app, reopen it and the curent seed got set) but then an hour or so, it got resetted back to 1.3 without rebooting the device
Click to expand...
Click to collapse
Hi !
Overclock automatically deactivates when the device enters in standby !
surdu_petru said:
Hi !
Overclock automatically deactivates when the device enters in standby !
Click to expand...
Click to collapse
Ahh, that's what I thought was going on, this is happening to me as well.
treo4life said:
Ahh, that's what I thought was going on, this is happening to me as well.
Click to expand...
Click to collapse
Hi!
No, this happens to everyone
However, it seems a pretty good thing - why we need OC - if the device sleep ? :laugh:
- it is also good for battery - !
So i will have to reoverclock it everytime ??
Mine doesn't do this at all. I use CleanROM 3.1, unters kernel and setcpu. No issues.
I guess I know why it's because setcpu has the profile settings allows u to set the CPU speed when screen is on / when screen is unlocked
Othe CPU apps I have tried have no such feature which means oc works when u set it, but when u turn off the screen then turn it on , it will reset back to 1.3ghz
Using setcpu, what I did was set a "screen off" profile to max out at 1700ghz when the screen is off or in sleep mode and it worked for me!!! That way will not default back to stock 1300ghz everytime I hit screen off or sleep mode.