Every now and then my HTC Hero just freezes up.
Especially when starting the phone.
Logcat says this:
W/SharedBufferStack( 264): waitForCondition(LockCondition) timed out (identity=
4, status=0). CPU may be pegged. trying again.
W/SharedBufferStack( 264): waitForCondition(LockCondition) timed out (identity=
4, status=0). CPU may be pegged. trying again.
W/SharedBufferStack( 264): waitForCondition(LockCondition) timed out (identity=
4, status=0). CPU may be pegged. trying again.
W/SharedBufferStack( 264): waitForCondition(LockCondition) timed out (identity=
4, status=0). CPU may be pegged. trying again.
W/SharedBufferStack( 264): waitForCondition(LockCondition) timed out (identity=
4, status=0). CPU may be pegged. trying again.
W/SharedBufferStack( 264): waitForCondition(LockCondition) timed out (identity=
4, status=0). CPU may be pegged. trying again.
W/SharedBufferStack( 264): waitForCondition(LockCondition) timed out (identity=
4, status=0). CPU may be pegged. trying again.
W/SharedBufferStack( 264): waitForCondition(LockCondition) timed out (identity=
4, status=0). CPU may be pegged. trying again.
W/SharedBufferStack( 264): waitForCondition(LockCondition) timed out (identity=
4, status=0). CPU may be pegged. trying again.
W/SharedBufferStack( 264): waitForCondition(LockCondition) timed out (identity=
4, status=0). CPU may be pegged. trying again.
W/SharedBufferStack( 264): waitForCondition(LockCondition) timed out (identity=
4, status=0). CPU may be pegged. trying again.
W/SharedBufferStack( 264): waitForCondition(LockCondition) timed out (identity=
4, status=0). CPU may be pegged. trying again.
W/SharedBufferStack( 264): waitForCondition(LockCondition) timed out (identity=
4, status=0). CPU may be pegged. trying again.
It's similar to the problem which this guy had: http://forum.xda-developers.com/showthread.php?p=14651457&posted=1#post14651457
It happens on all kind of ROMs like HTC Stock Android 2.1 ; Froydvillain 1.7.2 ; Cronos Gingerbread and Elelinux
So... worth it? Better than the iPad? Surface? What do y'all think?
Different. For some better, for some worse. It all comes down to your own preferences.
C-Lang said:
So... worth it? Better than the iPad? Surface? What do y'all think?
Click to expand...
Click to collapse
Cant say, haven't used the Surface and only little iPad 2 so hard to tell.
Sent from my Nexus 10 using xda app-developers app
how about those that have/had the note 10.1? worth switchin to nexus 10? or is screen the only factor..over all the features note 10.1 has especially with its upcoming jb update
tuffballa said:
how about those that have/had the note 10.1? worth switchin to nexus 10? or is screen the only factor..over all the features note 10.1 has especially with its upcoming jb update
Click to expand...
Click to collapse
Nexus 10 will receive future updates first (before any 3rd-party vendor/non-nexus device), has a clean Android experience (no Touchwiz, may or may not be a plus), and can easily be unlocked and modded (not sure what the Note 10.1's stance is on such matters)
What will yo be using it for mostly ? And gave you owned a tablet be for and what tablet? Once we know this we can give you a better answer.
I came from an I pad and it took me two weeks to settle into the nexus 10, first week will be poor battery life and frustrating with the back button but after that its great.
Don't use chrome use dolphin browser and the YouTube app is good but getting to subs is a little annoying at times.
Ill also say I've found lagg on some games like osmosis HD but others work great.
The feel of the tablet is great the soft warm rubberized finish is really comfy.
Also the tablet gets warm near the camera when being used nothing to be conserned about.
You should also keep in mind that you will get great support from Google with updates but even more support from us with custom rooms, however Samsung is a consern with giving out source for the exynos processors but I'm sure since it is a Google tablet this will not be an issue.
Also if you side load flash I personly found it to be useless and laggy.
Another thing is with such a high Res screen some site images will look pixalated but text and vector images are clear as a magazine.
We are also finding that support for some video codecs is not great but Mx player seems to do well to help this but it uses software to decode if I'm correct.
Sound quality is amazing with true around sound coming from left and right speakers.
And you will find some screen have light bleed but you will not notice this unless looking at a blank black image so not worth worrying over.
The screen is bright and crisp and hope full more apps will be updated to the Res in the future.
This still is more a Dev device rather then a consumer device so we do get some random reboots but it generally takes 30seconds to reboot so take that into consideration.
Also no mirracast support from what I hear so you cannot mirror movies onto your TV without a HDMI cable.
Also charging takes a long time 8 hours from empty to full. Their will be a pogo charger but who knows when that will be available and how long it will take to come out. Same with the smart covers and magnetic keyboards.
Hope this helps .
I live my nexus 10 and am happy i sold my I pad 2 I like the customization and freedom to do what I want with it also the comfort of use.
Sent from my GT-I9300 using xda premium
its amazing hands down if you love google you will cum
Its an awesome tablet; beautiful screen, front speakers, good battery life, really fast processor speed(boots up in 15 seconds), crazy multitasking with 2 GB ram and android 4.2 for only $400. Can't get a better deal than this in the market.
Sent from my Nexus 4 using XDA Premium HD app
I LOVE this thing, however, I must say that compared to my nexus 4, this thing is quite laggy. I of course rooted it and overclocked it and kept the minimum processor speeds to about 1 GHz to prevent lag as much as possible, but if you do any sort of "stressful" multitasking or game playing, then this thing will overheat and reboot fairly annoying, but it will surely be fixed in the future However, I LOVE the beautiful screen, stock experiecne, and the light form factor :highfive:
Just go to a Best Buy or equivalent and check them all out. People will have different opinions which may or may differ from your own.
ImARaptor said:
I LOVE this thing, however, I must say that compared to my nexus 4, this thing is quite laggy. I of course rooted it and overclocked it and kept the minimum processor speeds to about 1 GHz to prevent lag as much as possible, but if you do any sort of "stressful" multitasking or game playing, then this thing will overheat and reboot fairly annoying, but it will surely be fixed in the future However, I LOVE the beautiful screen, stock experiecne, and the light form factor :highfive:
Click to expand...
Click to collapse
This is one anecdotal experience and involved a complete wipe but I found that my N10 was much more responsive after flashing the stock image than it was out of the box.
ImARaptor said:
I LOVE this thing, however, I must say that compared to my nexus 4, this thing is quite laggy. I of course rooted it and overclocked it and kept the minimum processor speeds to about 1 GHz to prevent lag as much as possible, but if you do any sort of "stressful" multitasking or game playing, then this thing will overheat and reboot fairly annoying, but it will surely be fixed in the future However, I LOVE the beautiful screen, stock experiecne, and the light form factor :highfive:
Click to expand...
Click to collapse
Hmm... I've never, not once, had mine overheat and reboot. Mines also been as smooth as butter in every definition of the phrase. That's just me! Running on all stock.
Returned my ASUS Infinity TF700T for the Nexus 10, and I absolutely love it.
beamed from a Nexus 10 far, far away
jonstrong said:
Returned my ASUS Infinity TF700T for the Nexus 10, and I absolutely love it.
beamed from a Nexus 10 far, far away
Click to expand...
Click to collapse
I also returned my Infinity for the N10....not that the Infinity was awful. Gaming is better, the screen is awesome, 2GB is nice. The only down side is the charger IMHO.
ImARaptor said:
I LOVE this thing, however, I must say that compared to my nexus 4, this thing is quite laggy. I of course rooted it and overclocked it and kept the minimum processor speeds to about 1 GHz to prevent lag as much as possible, but if you do any sort of "stressful" multitasking or game playing, then this thing will overheat and reboot fairly annoying, but it will surely be fixed in the future However, I LOVE the beautiful screen, stock experiecne, and the light form factor :highfive:
Click to expand...
Click to collapse
I had only one reboot since I bout it, and too when I was not rooted, the only problem I have is that this thing does ridiculous amount of thermal throttling and can start lagging after playing high end games for a long time. Just a matter of time before the developers fix that
Sent from my Nexus 4 using XDA Premium HD app
johno86 said:
Just go to a Best Buy or equivalent and check them all out. People will have different opinions which may or may differ from your own.
Click to expand...
Click to collapse
Best Buy doesn't sell the Nexus 7 or 10, much to my chagrin!
Surface although it has that desktop mode you can't do much except office and browser. The app catalog is not as big as android or iOS and its a new platform hasn't been tested much in everyday use.
IPad is good at hardware not so good software wise (tired of the same old UI). I hear there are more apps for tablet on iOS.
Nexus 10 is android and has none of the bloatware of other android tablets faster upgrade cycle. Apps for tablet are limted . hardware is really good very good response times. Only problem is the light bleed which for my tablet is not noticeable in regular conditions unless you want to look for it. Contrast could have been better but its $100 cheaper than the competition. Not many Accessories yet.
Sent from my Nexus 10 using xda premium
If you consider yourself a power user and are used to Android, you'll sometimes find it incredibly difficult to do what you would consider even basic tasks with an iPad (tweaking settings is extremely limited as is personalisation for example). You'll find yourself regularly going to forums and searching for ways round the many limitations of the apple ecosystem, only to find if you want to do it you can't-unless you jailbreak it.
I do however tend to recommend ipads to my friends who are either not great with technology or who want it for a specific purpose that it performs particularly well at (as long as they have deep pockets obviously)!
It most certainly does have more optimised apps, you find many apps tend to appear first on ios and in the past have been higher quality.
You'll also find however that you'll almost certainly have to spend more money on apps with an ipad.
The android tablet apps will catch up soon enough though I'm sure as this christmas, tablets are selling in huge amounts and developers are all going to want a slice of the cake.
Sent from my XT910 using xda premium
So far, IMHO, the best droid tab on the market!!!
So you don't think that my opinion is frivolous, I have been a big part of the PDA/XDA revolution. My career is in mobile tech and my first smartphone was the "Amigo". Any of you remember that one?
Okay, so I did quite a bit of research on my next tablet. My first was the Galaxy 8.9 (by far my favorite form factor), then the Galaxy 10.1 V2, and finally the Prime TF700. Well, I didn' own the Asus for very long due to the ridiculously under developed I/O.
Unfortunately, my experience with Samsung's Cust SVC was like pulling teeth. My 8.9 developed horrible screen issues and had to be sent back to Samsung three separate times. After three months of playing ping pong with the under trained Samsung staff, finally, my money was refunded. So, needless to say, when I heard that Samsung was chosen to make the n10...I was displeased.
With that said, I can't begin to tell you how much of an improvement the n10 is to the Android sector. This tablet is by far the finest yet and should be given the top ranking spot...and not just because of the specs. Overall, 4.2.1 is extremely fluent and intuitive. Switching between programs and the home screen has absolutely no lag. The chrome browser is fast and seems to handle the lack of flash fairly well.
I, for one, really like the rubberized backing. Although I think that Asus' design is flashier and has a more "high-end" look, I always felt like the bare tablet was slippery and risked a drop. The n10 does not feel this way at all! Holding the tablet in one hand or two seems to make no difference on the grip. I believe this to be an extremely important factor in making the decision on which tablet to buy. A tablet has to be comfortable to use in all conditions.
One gripe...I know, I know....the lack of the SD card is a bummer. I did get the 32GB model, however, my movie collection alone is approaching 100GB. When I bought the TF, I sat down and spent hours transferring all of the videos to SD cards...now...anyone want three 32GB SD cards? I guess I'll be floating with the clouds.
Anyways, overall I give the n10 a 9.8 rating on my scale and truly believe that this is the tablet that has that potential to overtake the aging iPad and its iOS. Really shows what Google and its droid OS are capable of....can't wait to see what's next!
C-Lang said:
So... worth it?
Click to expand...
Click to collapse
For a few days i thought 100% yes - positive. Now im not so sure.
Screen was the main selling point for me. But now im disappointed.
After comparing with macbook retina screen (same image,on the same brightness) the difference is obvious: light bleed not only makes black glowing, but also makes colors much less saturated.
Both panels made by samsung, but they look completely different. PLS technology is supposed to be superrior than S-IPS, and it is, in retina display. But in nexus 10, it actually looks worse than S-IPS desktop monitor.
Nexus display still better than TFT.
DX11 class GPU ARM® Mali™-T604 GPU: APIs supported include OpenVG™ 1.1, OpenGL® ES 1.1, OpenGL ES 2.0, OpenGL ES 3.0*, DirectX® 11 and OpenCL™ 1.1.
GPU is great, but there could be a problem with tablet design. Playing modern games results in thermal Throttling in a few minutes.
I got to #2 in NFS: Most Wanted, but it was a torture, not fun. Usually, if you start with cold device, you can finish 2 races before slideshow starts.
You would not believe how bad it is.
Here is an example:
I slowed down and undervolted CPU to 600MHz/825mV to this test. Visually this reduced FPS (and supposedly GPU load) to about a half. But look at dmesg:
Code:
<3>[ 6121.923434] wm8994-codec wm8994-codec: FIFO error
<3>[ 6136.684382] wm8994-codec wm8994-codec: FIFO error
<6>[ 6162.047312] battery: l=77 v=3977 c=-873 temp=33.5 h=1 st=1 ct=2139 type=usb
<6>[ 6222.078644] battery: l=77 v=3991 c=-1122 temp=33.5 h=1 st=1 ct=2199 type=usb
<6>[ 6282.105733] battery: l=77 v=3982 c=-1177 temp=33.3 h=1 st=1 ct=2259 type=usb
<6>[ 6342.134913] battery: l=76 v=3986 c=-931 temp=33.3 h=1 st=1 ct=2319 type=usb
<6>[ 6402.164581] battery: l=76 v=3977 c=-1044 temp=33.3 h=1 st=1 ct=2379 type=usb
<6>[ 6462.191748] battery: l=76 v=3977 c=-1572 temp=33.5 h=1 st=1 ct=2439 type=usb
<6>[ 6522.217670] battery: l=76 v=3982 c=-1077 temp=33.5 h=1 st=1 ct=2499 type=usb
<6>[ 6582.243999] battery: l=75 v=3957 c=-1740 temp=33.5 h=1 st=1 ct=2559 type=usb
<6>[ 6642.273164] battery: l=75 v=3957 c=-1556 temp=33.6 h=1 st=1 ct=2619 type=usb
<6>[ 6702.300569] battery: l=75 v=3967 c=-1009 temp=33.6 h=1 st=1 ct=2679 type=usb
<6>[ 6740.053235] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 6744.060087] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 6745.065074] exynos_thermal_unthrottle: not throttling
<6>[ 6762.326856] battery: l=75 v=3952 c=-1452 temp=33.6 h=1 st=1 ct=2739 type=usb
<6>[ 6799.431233] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 6809.440076] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 6810.445067] exynos_thermal_unthrottle: not throttling
<6>[ 6822.353315] battery: l=75 v=3952 c=-1246 temp=33.8 h=1 st=1 ct=2799 type=usb
<6>[ 6882.380353] battery: l=74 v=3957 c=-1253 temp=33.8 h=1 st=1 ct=2859 type=usb
<6>[ 6898.923374] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 6906.925088] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 6907.930062] exynos_thermal_unthrottle: not throttling
<6>[ 6942.406760] battery: l=74 v=3962 c=-1170 temp=33.8 h=1 st=1 ct=2919 type=usb
<6>[ 6961.641239] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 6965.645090] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 6966.650084] exynos_thermal_unthrottle: not throttling
<6>[ 7002.435304] battery: l=74 v=3952 c=-1121 temp=34.0 h=1 st=1 ct=2979 type=usb
<6>[ 7056.386004] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 7061.390081] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 7062.395063] exynos_thermal_unthrottle: not throttling
<6>[ 7062.460871] battery: l=73 v=3947 c=-1320 temp=34.1 h=1 st=1 ct=3039 type=usb
<6>[ 7116.360405] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 7122.487602] battery: l=73 v=3928 c=-1728 temp=34.1 h=1 st=1 ct=3099 type=usb
<6>[ 7135.366751] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 7136.380068] exynos_thermal_unthrottle: not throttling
<6>[ 7137.473113] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 7157.487309] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 7158.495067] exynos_thermal_unthrottle: not throttling
<6>[ 7161.072825] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 7180.086782] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 7181.090064] exynos_thermal_unthrottle: not throttling
<6>[ 7181.762092] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 7182.515823] battery: l=73 v=3928 c=-1058 temp=34.1 h=1 st=1 ct=3159 type=usb
<6>[ 7201.783180] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 7202.785083] exynos_thermal_unthrottle: not throttling
<6>[ 7204.425444] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 7224.436955] exynos_tmu exynos_tmu: Throttling interrupt
<4>[ 7225.445074] exynos_thermal_unthrottle: not throttling
<6>[ 7226.939704] exynos_tmu exynos_tmu: Throttling interrupt
<6>[ 7242.544022] battery: l=73 v=3923 c=-1736 temp=34.3 h=1 st=1 ct=3219 type=usb
Game started at ~6162s, ~500sec later it started to throttle. Throttling, among other things, change memory speed and increases memory refresh rate 2x ( which slows down memory even further). Memory bandwidth is crucial to 3D graphics in 2560x1600.
This could be totally software issue, increasing temperature threshold, undervolt/underclock GPU and memory controller could solve the problem.
But if you want to enjoy this toy right now, you are out of luck.
P.S second issue seems to be solved, undervolting GPU -100mV and increasing throttling point to 85 C did the trick
I'm working on a research project about Android smartphones power consumption. Using "adb shell dumpsys batterystats" interesting stats can be obtained. For example:
Statistics since last charge: System starts: 0, currently on battery: false
Time on battery: 1h 0m 38s 51ms (99.7%) realtime, 1h 0m 38s 50ms (99.7%) uptime
Time on battery screen off: 30m 21s 169ms (49.9%) realtime, 30m 21s 169ms (49.9%) uptime
Total run time: 1h 0m 47s 207ms realtime, 1h 0m 47s 207ms uptime
Start clock time: 2016-06-18-22-57-54
Screen on: 30m 16s 882ms (49.9%) 1x, Interactive: 30m 16s 367ms (49.9%)
Screen brightnesses:
dark 10s 89ms (0.6%)
light 30m 6s 793ms (99.4%)
....
Estimated power use (mAh):
Capacity: 6700, Computed drain: 298, actual drain: 335-402
Screen: 244
Unaccounted: 36.9 ( )
Uid u0a90: 15.8 ( cpu=15.8 )
Uid 1000: 9.58 ( cpu=9.49 sensor=0.0868 )
.....
As far as I know, the power_profile.xml is used to estimate the power consumption of each hardware component, and differs from device model to another.
Now I have couple of questions:
Q1: How does Android compute the actual drain ? I looked everywhere and I can't seem to find an answer. I also checked Android code, but unfortunately I couldn't identify the implementation of the method theat is responsible for "actual drain".
Q2: How Android estimates the screen power consumption ? the screen's value when it is on "light = 75%" state is:
ligh: 120.96 ( and it's in mA according to the power_profile.xml), I found this value on Nexus 9.
However, the report says the consumption is 244 mAh for about 30 mins, it doesn't make sense to me ! Can you guys explain it ? I tried to check the source code but again I couldn't find it.
Q3: How accurate these values in the power_profile.xml ? I found here some posts reporting some issues for Samsung devices. But I don't know about Nexus 9.
For those of you using the modified thermal-engine-8996.conf files in this forum, I would recommend using these three specifications under the [KYRO_SS] area: (keep everything else the same)
set_point 49500
set_point_clr 45500
device_perf_floor 1324800
set_point determines a threshold for thermal throttling
set_point_clr determines when to stop thermal throttling
They don't equate exactly to the degrees in celsius for the CPU or battery, so I'm not sure exactly what the translation is. However, I found that this was a pretty good threshold to use to reduce the thermal throttling on the CPU.
By setting the device_perf_floor metric to a lower number, I could also make sure that thermal throttling DID happen when it was needed. This helped a lot to reduce the chances of my phone from overheating and shutting down during a hot summer day.
Hope this helps somebody! This really saved my phone.
this is the two i modified
p.s. do not go higher than 1824000... it went so hot my first Lgv20 screen got unglued from the case lol. now is working fine with my second lg v20 with below config
KRYO_SS]
algo_type ss
sensor skin_ap
sampling 5000
device cpu_voltage
set_point 40000
set_point_clr 38500
device_perf_floor 1824000
[GPU_MONITOR]
algo_type monitor
sensor vts
sampling 5000
thresholds 38000 39500 41000 42500
thresholds_clr 37000 38500 40000 41500
actions gpu gpu gpu gpu
action_info 642000000 560000000 510000000 401000000
paul999 said:
this is the two i modified
p.s. do not go higher than 1824000... it went so hot my first Lgv20 screen got unglued from the case lol. now is working fine with my second lg v20 with below config
KRYO_SS]
algo_type ss
sensor skin_ap
sampling 5000
device cpu_voltage
set_point 40000
set_point_clr 38500
device_perf_floor 1824000
[GPU_MONITOR]
algo_type monitor
sensor vts
sampling 5000
thresholds 38000 39500 41000 42500
thresholds_clr 37000 38500 40000 41500
actions gpu gpu gpu gpu
action_info 642000000 560000000 510000000 401000000
Click to expand...
Click to collapse
The difference betwen the two methods is that 1824000 is actually kind of a high frequency to be thermal throttling at. (especially during the hot summer days we've been having lately in my state, my phone would just continue heating up and shutting down) I find that modifying set_point and set_point_clr are actually better since it increases the temperature setting BEFORE it starts throttling, but still throttles when it really needs to. This is especially helpful when using extended life batteries like the 6700 mAh batteries or 8500 mAh batteries which tend to run hotter than the average 3200 mAh batteries.
What I've observed is that if the extended batteries go above 51 degrees celsius, it starts kind of a chain reaction of heat between the CPU and battery that eventually causes the phone to overheat. I targeted the set_point and set_point_clr settings to cause it to throttle around this time to still make the phone usable, just slower for a short time.
I found that 1324800 was a good frequency to actually bring the temperature back down. When I set it at higher frequencies, the temperature for the battery would still stay around 51 degrees celsius or higher which was too hot for my taste.
i think my phone can handle it since i replaced the cheap paste with a premium paste......anyway i will test your method out to see if theres improvement