yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro General] Ineedtoys:
Thanks acetuk, at least I know the Exec's working as it should. I'm not anti-Exec, I have had several situations this week where the Exec won hands down - typing up meeting minutes while I remember what's been said, doing an urgent document review with a colleague (although he did have to squint a little), and checking these forums over WiFi at home :) So it does come into its own as a business tool, which is how it is marketed after all.

And if you're using the data package in anger then the equation does swing a bit the other way - although the data 5 is a very expensive way of doing it!

I just thought it was interesting to see how well the Wizard performs in hindsight - and how marked the speed difference was on the Wizard, once I'd been using the Exec for an extended period. I knew the screen slowed it down, but I was still expecting some turn of speed given the 524MHz CPU and previous comments by people saying how it really was much faster. But I saw the spinning disc this far more this week than I ever did with the Wizard - and had to reboot more frequently as well.

It also proves how irrelevant to real life reviews and adverts based on "benchmarks" and CPU clock speeds, really are, and that anyone who treats those as gospel is going to be sorely disappointed. :lol:
[JASJAR, XDA Exec, MDA Pro General] acetuk:
I fully agree - I started skipping benchmarks about three years ago. If I see them in a review I go straight pass them.

In the real world the device is as good as you can make it work for you. If a device doesn't cover your basics then so be it but that doesn't make a device bad. My Exec is slower than my hx4705 for loading PlanMaker and for general feel. But it is so much quicker for data entry. So what I lose in load time I gain in usability. So I win overall as far as I am concerned, regardless of any benchmarks stating overwise.

But the Wizard is an amazing piece of kit. Having PocketInformant running on both, syncing via a hosted exchange server, is a major productivity step forward for me. Pick up the device most useful for the moment, run a sync over wifi or GPRS and get to work. Today I updated all of my tasks and appointments on my Exec using it's excellent keyboard, sync'd to exchange, picked my Wizard up and sync'd again. In less than a minute both devices were fully up to date.

As for the data side of the Exec you are again quite correct. That is why I signed my Exec up for the Data36 tariff with O2 - that's 1mb a day with 5-6mb spare for when I need it. So far that is working very well for me combined with my wifi network at home. I'm paying for it but not too much at £18 / month approx but with no voice calls on top.

Now, if I can only understand better how to get two Windows Moibile devices, two PCs (one private, one work) and one exchange account syncing together better I will be happy!! That might need to go in to another post!
[JASJAR, XDA Exec, MDA Pro General] knowsleyroader:
Again I have both thanks to O2 generosity but although I love my wizard for its size and the fact it can do anything the universal can do I would dispute the speed issue.

I find the universal to be the speedier of the two and the screen is amazing.

I love em both is the fact. Why compare them ? Just feel the love :D
[JASJAR, XDA Exec, MDA Pro General] Ineedtoys:
Can you quantify this? Are you saying the menus, program loading, application switching and screen refreshes are quicker on your Universal? I'd be intersted in finding out why that differs from the comparisons above. Unless your Wizard is slower than it should be, or you're not using an intelligent task manager?

By the way, my current view is that I will keep both, for maximum love :)
[JASJAR, XDA Exec, MDA Pro General] knowsleyroader:
Using a basic install on both with exactly the same apps and I do feel the universal is faster although I havent benchmarked this or even run them side by side. It just seems faster to me.

However I dont have an issue with either. Its not something im bothered about, just an observation. Im sure you will find others that thing the uni is faster.
[JASJAR, XDA Exec, MDA Pro General] stombacco:
Stability

Hi,

Before JasJar I own an IpaqHW6515. Generally JJ is much better that 6515 but using this device as unique device for communicate is not confortable as 6515 because:

1. battery life. my jj can't run for one complete day. With 280 grams devide, increasing of 20/30 grams using a much better battery would be appreciate.

2. BT: 6515 was much better in quality and range. and with a such big and havy device quality of BT would be a MUST because I don't know others but I try to use as much as possible handset because after a while with phone in my hand, I feel tired.

3. I need to soft reset few time a day. This because I start missing calls as device crash without reason while in standby.

4. I ALWAYS have problems (calling mainly) when I need something urgent. And I get crazy because I have to soft resent loosing precius minutes.

For this reasons, I confirm that JJ is best business device (i should not come back to 6515) but I've decided to buy a very light a small phone for make calls and use JJ only for Emails, web....

At least till a new rom will make stable the device.

Ciao

Stefano
[JASJAR, XDA Exec, MDA Pro General] PDAholic:
Well, this bites. Not only is my JJ slow thanks to WM5, but also thanks to its big screen. I have gotten sick of my constant resents, and I've gone back to my WM2003 device. I feel eBay a callin' my name.
[JASJAR, XDA Exec, MDA Pro General] the magman:
Morning all....

I dont wish to be a fish out of water here, but can i ask if anyone of you have flashed the rom and upgraded...??

I'm now running with the following :-

Rom ver.........1.13.82 WWE

Rom date.......11/30/05

Radio ver.......1.04.02

Protocol ver...1.13.188 WWE

Having had both the XDA II and the IIi, it sure seemed slower than both of them....then I flashed it !!

It is both faster and smoother than my previous XDA's, I haven't once had to soft reset yet....and my battery last more than a day :lol:

For those of you who haven't done so yet.... it's a must !!

http://www.my-xda.com/xdaexec_soft.html

The magman
[JASJAR, XDA Exec, MDA Pro General] stombacco:
it's true

The Magman,

I flashed my JJ to o2 ROM and in effect looks more stable faster. I've done during this quite week end and therefore I cannot say solved until I've tried JJ during a complete work week.

Ciao
[JASJAR, XDA Exec, MDA Pro General] Anton.Valleyman:
I've had the XDA, XDA2, 2i and now the Exec - though I also had a play with a mate's Wizard whilst installing some software for him overnight a few weeks back.

I found the Wizard to be a lovely bit of kit, though I wouldn't necessarily say any faster (he had a basic install on, which is what I have on the Exec). The screen on the Exec is absolutely fantastic, the first times I noticed this was on opening the unit for the first time, and when I started whipping files to the Wizard via BT: there is absolutely no comparison between a QVGA and a VGA screen.

I think if the Exec hadn't arrived, then I would have gone for the Wizard, it's a good phone. However, I don't think I would find it easy from the 2i to Wizard, given the smaller screen and the somewhat cheapish keyboard.

Cheers

Ant
[JASJAR, XDA Exec, MDA Pro General] Ineedtoys:
The O2 Exec came with the same versions as yours out of the box, so already using the latest.
[JASJAR, XDA Exec, MDA Pro General] knowsleyroader:
Have been having too much fun with my mini s and exec so far to even think about flashing the roms :D
[Sony Xperia Miro, Tipo (Dual), J, E] Grobovschik:
Subject in title.

Keyboard Gembird KB-P3-BT-UA. The problem is not exactly a keyboard.

On other devices such as ASUS Transformer or HTC One V it's working. And it's working on PC.

Version of OS is 4.1.1

Build 11.3.A.2.23
[Sony Xperia Miro, Tipo (Dual), J, E] 123386761:
It works on the 1V? Damn I'll have to try that lol
[Off-topic] impairedworld:
Well you finally can!!

How?

We will be saving LIVES!!

How?

Lets spread the word about "Our Mission to Raise Awareness of Impaired & Distracted Driving while Operating a Motor Vehicle. To Prevent and Share the Consequences of this Crime"

Tell the person next to you....Think Before You Drink!!

Anymore suggestions? add them.

Thanks.
[Off-topic] impairedworld:
With 5+ million members...only if we can spread the word about being safe on the road, with laying out the consequences of those crimes. I think will be good contribution.

People know its wrong, but continue to commit such a crime...maybe they don't think it is a crime, maybe they don't know it carries a criminal record...they don't know they can go to JAIL for a while and ruin their career?

Kill others in the process. Well it can happen. We all can help each other.

Most people will say, "its their life to ruin"...well there is the other part. The ones that will lose their life or be injured in the process is what we really want to help!!

It can happen to someone on this Forum, well only if they can see this thread..it might help??

We are speaking about both Impaired and Distracted driving....which we all should know by now "Distracted" is more common than Impaired Driving, and have more fatalities as of lately.

"PLAN AHEAD" is another good start.
[Off-topic] impairedworld:
"DWD" - "Driving While Distracted" = is the new "DUI".
[Off-topic] impairedworld:
Hopefully as we go further into this thread, everyone can be educated...that is how people learn from their mistakes. Someone have to let them know RIGHT from WRONG!!

The first thing to learn is RESPECT!!

I grew that way, so that was not an issue for me. Give it a try!!
[Off-topic] M_T_M:
Ok...I've deleted some posts on this here thread. The OP is trying to make a valid point that fall within our rules and guidelines...please stop trolling here.

Want to participate in this thread? Do it in a respectful way...otherwise, stay out!!

Cheers,
[Off-topic] jRi0T68:
Let's just start with how "dwd" is impossible to avoid. There are early signs of a push to ban eating while driving. What next? No more stereos? Blood pressure monitor hooked to ignition, so you can't drive if you're upset at all?

People want to put blame on everything a person does to avoid the truth:

Some people are just too stupid to drive responsibly.

People will always make driving errors, no matter what.

You can't put enough laws on the books to prevent all distractions.

"The government that governs best is that which governs least."

Excreted from my Nexus 5

[Guide] Headphone/Earphone Buying
[Off-topic] jugg1es:
On topic, drink is just a small issue amongst a hundred other dangerous things I've seen. Women putting on makeup doing 70 down the motorway, people rolling cigs whilst driving with their knees, reaching back to swing at the kids, people taking pictures of accidents with their phones, people that can barely see over the steering wheel. The list is endless, some people shouldn't even be behind the wheel of a car and god knows how some people managed to even pass their test

"Don't be so humble - you are not that great."

- Golda Meir (1898-1978)
[Off-topic] impairedworld:
Lets not get carried away with what is really the issue here. Getting high and using a mobile device behind the wheel don't mix, period!!

DWD is not impossible to avoid....you just need to set behind the wheel RULES. Once that is set, obey it.

Do you really think eating while driving is safe?

Just drive, it is what you are supposed to do.

I don't have a say on this, only to be cautious, use lots of spacing, know your surroundings, use presets, create playlists if using an iPod and just let it play. Steering wheel operation is becoming standard. Stereo is secondary, driving is primary!!

You shouldn't drive upset. People do not know this, especially the ones getting upset while using the cellphone. Cool down first.

What do you mean by blame...truth?

You call it stupid, which might just be distraction, novice driver, impaired, upset, stressed, etc...

Everybody is not perfect, there will be errors....There is a slim chance of having errors if you are 100% focused on driving and follow the rules and regulations of the road. Basically if you are gonna cut a tree down, would you use the cellphone while cutting the tree down? Would you eat while cutting the tree down? No, because you can get injured or killed, or kill others around you.

We don't need Laws, we just gotta teach ADULTS common sense. I have no clue how to teach common sense.

Not sure what you mean...Maybe that is why i see the need to do this.
[Off-topic] jRi0T68:
My point is there will ALWAYS be distractions, and recent talk here on laws yet to be in the books is absurd.

When you're stuck in traffic for 3 hrs in the morning and 3 at night, having nothing to eat or drink, expecting no distractions or interruptions, expecting that you won't drive if you're worried about work, or pull over every time your child gets disrespectful... It's all a bit far fetched.

Focus on the road, plan ahead, but a fascist environment isn't necessary for driving. It's not hard to sip coffee in traffic, cram a quick bit in every two minutes, etc.

Maybe those real world distractions aren't things you've experienced while driving (assuming you do drive).

Excreted from my Nexus 5

[Guide] Headphone/Earphone Buying
[Off-topic] impairedworld:
There will always be distractions outside of the car. Once you train yourself to not be distracted, everything will be okay.

Remember that you have a family to take from point A to point B safely.

People are the ones to blame here, on why there is such Laws planned ahead.

Only if I started this earlier, maybe those Laws could have been prevented.

The car is DEFINITELY not a lunchroom. But I do admit doing this previously.

Once your kids seatbelt is secured, whatever it is can wait until you stop safely.... I have 5 children to deal with at times.

Disrespectful?? Maybe you mean to say "act up"...No child should be disrespectful toward their parents, from day one!!

I do not drink coffee...but I occasionally take a bottle of water with me.

Now, just to be clear...I refuse to be Distracted in close quarters while driving. If there is a fair amount of spacing and clear surroundings, also in a staggered position...then I will choose to take that sip of water, or even touch the stereo.

I am 37 yrs old now... I do drive, I am a Professional Driver...My Licence Class is ACMZ.

A - Any tractor-trailer or combination of motor vehicle

C - Any regular bus with designed seating capacity for more than 24 passengers

M - Motorcycle

Z - Air Brake

I must say this, I was younger at one point and totally opposite of what I am right now.

Only if there was someone there to put me in check, to show me RIGHT from WRONG!!
[Off-topic] impairedworld:
I am here with a Goal, and that is to spread the word that will protect and save human lives, and also prevent people's future and careers being destroyed by this senseless crime.
[Off-topic] Seraz007:
...............
[Off-topic] impairedworld:
Think Before You Drink!!
[Off-topic] impairedworld:
Driving is a Privilege, Not a Right!!...Driving is Beautiful. #distracteddriving

https://www.youtube.com/watch?v=ERLwgT5cAa8
[Off-topic] impairedworld:
Who is with me?
[Off-topic] impairedworld:
Please Follow, Like and Share....thanks.
[Samsung Galaxy Nexus] metalspring:
not sure if this helps but

W/ManagedEGLContext(31385): doTerminate failed: EGL count is 2 but managed count is 1

seems to come from the code in https://github.com/android/platform...gl/java/android/opengl/ManagedEGLContext.java

lines 111- 126

// Need to check how many EGL contexts are actually running,
// to compare with how many we are managing.
EGL10 egl = (EGL10) EGLContext.getEGL();
EGLDisplay display = egl.eglGetDisplay(EGL_DEFAULT_DISPLAY);

if (display == EGL_NO_DISPLAY) {
Log.w(TAG, "doTerminate failed: no display");
return false;
}

if (EGLImpl.getInitCount(display) != sActive.size()) {
Log.w(TAG, "doTerminate failed: EGL count is " + EGLImpl.getInitCount(display)
+ " but managed count is " + sActive.size());
return false;
}

so what exactly might happen if that was removed? I'm not a coding expert but it might at least get us past that particular error and show other ones that might need fixed
[Samsung Galaxy Nexus] gh0stslayer:
looks like the managed EGL count does not exceed 1 at any case, so we need to find the code for setting sActive.size() .

i think removing this part of the code well lead to even further errors and freezes, but lets wait for some experienced developers for their comments.
[Samsung Galaxy Nexus] ilgimmy:
sActive is an array.

sActive.size() depends on how may times sActive.add(this); is called.

sActive.size() increase any time a new ManagedEGLContext is created.

I think the error is not in sActive,size() being 1, but in EGLImpl.getInitCount(display) returning 2, while only 1 ManagedEGLContext has been created.

I'm trying to see where EGLImpl.getInitCount() is defined...

UPDATE: can't understand where those "native" functions can be found for GNex...Which is the correct repo for C stuff for GNex?
[Samsung Galaxy Nexus] MWisBest:
http://review.cyanogenmod.org/#/c/54291/

Looks like it was tracked down, Google basically had us just beta testing this stuff for them, lol.
[Samsung Galaxy Nexus] sd3993:
I know this is an old thread.

But all other ROMs except for CM still experience rare freezes/reboots(even on 4.4.2 which has the Refactor gpuMemoryBuffer patch included already).

Can anyone please list out all the commits that eventually let to complete eradication of the freeze/reboot issue on CM?

Thanks Guys! :)
[Samsung Galaxy Nexus] baldwinguy77:
I am also still wondering about this. This is the only thread I've found with accurate, concise information concerning the lockup->reboot behavior that almost all of the Galaxy Nexus KitKat ROMs are experiencing, except for CM. I don't want to just rip off CM's code, but I'd like to actually see if we could figure out what's going on and how it could be fixed. I've also isolated these few lines consistently from logs right before reboots occur:

E/IMGSRV ( 5116): :0: gralloc_register_buffer: Cannot register a buffer twice (ID=6)
W/GraphicBufferMapper( 5116): registerBuffer(0x46168508) failed -22 (Invalid argument)
E/GraphicBuffer( 5116): unflatten: registerBuffer failed: Invalid argument (-22)
I/ActivityManager( 454): Process com.android.musicfx (pid 5313) has died.
I/Choreographer( 5116): Skipped 35 frames! The application may be doing too much work on its main thread.
W/SurfaceFlinger( 128): setTransactionState timed out waiting for previous animation frame
I/Choreographer( 454): Skipped 294 frames! The application may be doing too much work on its main thread.
W/SurfaceFlinger( 128): setTransactionState timed out waiting for previous animation frame
[Samsung Galaxy Nexus] sd3993:
I've been hunting around the a little and i narrowed down the error to these two files

/frameworks/native/libs/ui/GraphicBuffer.cpp & /frameworks/native/libs/ui/GraphicBufferMapper.cpp

I've tried a few things to fix the errors but I wasn't successful.

Also I have no idea where IMGSRV or 'gralloc_register_buffer' are located? Do you know where they are?
[Samsung Galaxy Nexus] metalspring:
I'm starting to wonder if the fix for the reboots is hidden somewhere completely unexpected, I know I've personally tried pulling in just about everything related to graphics in cm's frameworks_native repo and still getting the reboots on omnirom

Let's just hope the fix isn't hidden in frameworks/base (since that's one of the repos that gets the most commits)
[Samsung Galaxy Nexus] pattyboi:):
ill look around in there tonight..never know what cm has up their sleeve.
[Samsung Galaxy Nexus] sd3993:
I scanned through the commits in /harware/libhardware too and pulled almost all commits related to graphics since 1st Nov but none really helped :/

I guess it's time to take a deep breath and dive into /frameworks/base then! :P

---------- Post added at 11:17 AM ---------- Previous post was at 10:29 AM ----------

I took a quick look through the commits in external/chromium_org/

Here the commits I found interesting.

https://github.com/CyanogenMod/andr...mmit/18760af88a405ded53cf524d9a273b217e759807

https://github.com/CyanogenMod/andr...mmit/294545aa54ddff00ccb2f1188f231ff0ebbd9386

https://github.com/CyanogenMod/andr...mmit/e1049c797e39f4f9f9753731b3c7054473db1b45

https://github.com/CyanogenMod/andr...mmit/e31b3128a419654fd14003d6117caa8da32697e7

Plus can anyone verify that this commit https://github.com/CyanogenMod/andr...mmit/dd37648c2dfb0405e11028c264ef37200ef75001 is already included in AOSP 4.4.2? Because i THING that all reboot/freeze issues were fixed right after CM merged in this commit into 4.4 (4.4.1 and 4.4.2 weren't released back then.
[Samsung Galaxy Nexus] Loureiro:
Allright guys, [MENTION=2548902]akash3656[/MENTION] built an Omnirom using metalspring's device trees and a commit found by [MENTION=4353291]steven676[/MENTION] (http://xdaforums.com/showpost.php?p=49009667&postcount=574) that really worked against graphic glitches & reboots.

I've been messing around and those gralloc buffers still got messed up but It will not make the device reboot or display weird graphical glitches. However, the affected app become choppy. just kill that thread for now
[Samsung Galaxy Nexus] sd3993:
No. I managed to trigger freezes even with the fix. Glitch is still there :/
[Samsung Galaxy Nexus] Loureiro:
Dammit. Guess I didn't stressed the rom that much. I was able too see throught adb logcat the buffers not being registered properly and all those IMGSRV errors, and none of those glitches appear.

I'll continue trying to trigger a freeze.
[Samsung Galaxy Nexus] sd3993:
Open G+. Click on a link that will open in a browser. One the page loads fully navigate a little. Then click on recents button and choose G+. You'll see the GraphicBufferMapper errors in logcat and the black boxes in G+.
[Samsung Galaxy Nexus] Loureiro:
I'm trying to trigger, but without success so far.

got

E/IMGSRV gralloc_register_buffer: Cannot register a buffer twice (ID=6)

E/GraphicBuffer unflatten : registerBuffer failed: Invalid argument (-22)

and a warning related to GraphicBufferMapper

registerBuffer(...) failed -22 (Invalid argument)

But didn't saw any black boxes. I'm still jumping between aosp browser / dialer / G+ / tapatalk / settings using recents button. Those 2 erros keep showing on logcat but there's no graphical glitches nor reboots.

As far as I understood, it's normal that GraphicBuffer unflatten() still throws that error. But now with that commit, it clears the buffer when the error occurs, not poiting to anywhere else, that was causing graphic corruption.
[Samsung Galaxy Nexus] sd3993:
The reboots are rare. But i don't think that error should occur at all. If i had a Nexus 4 or 5 i could test it on those. Do you know anyone with those devices? Maybe you could ask them to see id these occurs on their devices?
[Samsung Galaxy Nexus] steven676:
No, it is not part of AOSP at the moment -- that comes from Chromium sometime around the Chrome 31 development cycle, and AOSP is still on Chrome 30.

To be clear, black boxes in WebView is a different bug than the one causing device crashes and screen corruption in random apps, and the workaround for one will not fix the other -- you'll need both patches applied.
[Samsung Galaxy Nexus] sd3993:
Yes i figured it out with a little bit of research :P

BTW the patch(the one that modifies GraphicBuffer.cpp & IGraphicBufferProducer.cpp) which you linked in the Nexus S didn't work. Reboots are still an issue.

I'm still hunting around.
[Samsung Galaxy Nexus] baldwinguy77:
So I merged in this commit that other people have been talking about quite a lot and my users haven't reported any reboots yet.
[Samsung Galaxy Nexus] sd3993:
That alone is not enough to fix the reboots. They are greatly reduced but still happen.

Merge in all the commits from the link below.

http://xdaforums.com/showpost.php?p=49138376&postcount=894
[Samsung Galaxy Nexus] metalspring:
I think he already has most, if not all of those