Related
As ICS has been released, all our devices have a developer that works hard on making ICS for your phone...
But, if you have a low-end phone, with low memory, RAM, CPU, small screen, you doubt it is good for you...
YOU ARE WRONG
ICS is made for high-end devices and tablets, but, if you see, all the bars and everything have been optimized:
-Pressing menu will bring a more minimal menu.
-Apps like "Maps" have transparent bars!
-The "thumb slider" is much, MUCH more slim.
-Apps like Superuser don't have the need to press settings to get to the settings, it now appears in the top bar!
-The title bar is a tiny bit smaller, the status bar makes you thing you have a very high-end device!
You thing the RAM is not enough... wrong! It actually takes less RAM for me than on GB, with lot more crappy apps ICS has...
CPU not good??? YOU ARE 100% wrong!! An OS will never take more than 100 MHz just to work, A win7 PC with a dual-core CPU(2,8GHz) takes just 2% if not doing anything, and this is a Computer OS, very complex one!
One little problem is the size... it takes a lot from internal memory, but data2sd etc... they will solve it!
Yes, it is not a fully working ROM, except for some of the high-end devices, but the devs are working together, a developer from gt540 fixes something, another one from p500 takes it and works faster, a HD2 dev comes with a fix, all devices use it, p500 devs come with a very innovative thing, it gets implemented on ALL devices with the compatible hardware...
So, just take ICS, but make sure it is done!! It is highly unstable for most of us right now, but everyone is working very, very hard
.
Thread moved. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
Bump
I know this is old. but look where we are now. almost every active device and some inactive devices have ICS ports, even low end phones, and most of the phones that have ics already have jelly bean
I still use a HTC Desire,, i believe i am rediculously limited by the apps space ... literally 70mb in total
I'm not necessarily a noob to android. I've flashed a few phones, dabbled with rooting and custom roms, but nothing too serious.
My first question about these Tegra 2 processors is fairly simple. I want to know if overclocking them makes them more media capable? I have a Droid Charge and had a Galaxy S before it, and both phones were perfectly capable of playing a 720p mkv with nary a stutter. It boggles my mind that I have to convert every video file before I drop it onto the Xoom. It's not a huge hassle but it's rather interesting a single core hummingbird can handle it with ease and a dual core clocked at the same speed has so much trouble.
Second question is this. Is there any development going on for the Xoom Family Edition? I haven't noticed much other than news posted regarding this version on this forum, so I'm not sure. It's obviously not the hit they were hoping it would be, there's a whole 3-4 cases made to fit it, and virtually no accessories for it like there is for the Xoom (docks and whatnot). If overclocking helps without nuking battery life, I'd be interested. I wouldn't know where to start developing, I'm definitely not a skilled programmer, but I would be happy to help any way I could (minus a potential brick, I can't afford a new tab)!
Bump. Any opinions?
Regarding the overclocking the tegra 2 , yes it will be more powerful therefore increasing media playback performance. Although battery usually drops faster you can install set CPU to set profiles for when the screen is off etc...
As for the Xoom I myself am not very knowledgeable about that device so I cannot effectivily answer your question.
Hope this helps!
Sent from my PG86100 using XDA App
Remember that the Xoom screen is so much bigger, so takes a lot more juice to playback at same resolution, but overclocked cpu does make a difference for sure. Also, if on ICS, go into developers settings menu and turn off animation or set to .5. Makes a big difference.
The Xoom FE (like the Xoom2 and the Xyboard) don't have unlockable bootloaders and noone yet has found the exploit to gain root access. Hence no development...so far. If you find the way, you will be popular among the owners of those devices.
If you overclock the Xoom it will of course consume the battery faster, as with anything that requires voltage tweaking. The main thing to remember is research the governors that will adjust what clock you're running at and when you're running it. Interactive usually gives the best performance speedwise while Ondemand gives you a mix of performance and battery life.
Your media playback issue could possibly be due to several factors. Processor, RAM, SD read rate, and the media player are the main culprits that come to mind.
If it is the processor then overclocking will most likely help. There is a minor off chance that the Tegra2 does not contain certain instruction sets included on the other devices processor that allow it to decode the Matroskiva, mkv, format as readily.
If it is the RAM, your best bet is to get a task killer and use it to kill everything before you try to play the video. You can also go into settings and go to individual apps to force kill them which tends to work better than most task killers.
If it is the SD card rate, research fairly deeply into the subject because I personally have heard many mixed reviews in regards to the Xoom and higher "class" or access rate SD cards. Eventually I plan on getting a collection of them to run some testing myself for a unified chart, but until then your best bet would be to ask experienced Xoom users, and browse these forums.
If it is the app then try looking around to see what other players are out there. Some people use different decoding codecs than others, and some tend to work better on mobile devices with limited instruction sets.
Mind you, if i remember correctly, the other two devices also display at a lower resolution, which would take less power, and the app used to play the file might not support the larger resolutions as well.
And if you have not already toyed around with your Xoom and hacking it, just as a warning, like all other devices it can be easy to brick. Make sure you have read at least 2 different tutorials on how to do it beforehand as some are much more clearly stated than others.
Hope this helps you some
I hadn't thought about the memory card being the issue. I'm not sure how fast the internal memory card is, but my external is only a class 2, so that could have an effect on load times and everything. I know the RAM isn't really a problem, I don't do much on my tablet, and I've tried killing apps and fresh boots and nothing seems to work. It only seems to use about 450mb out of 1024mb for apps, and out of that only 124 was in use last time I checked.
I have tried many other media players though, including Dice Player which seems to be unanimously the best, and nothing I've tried is able to play an mkv on the Xoom. I typically try downloaded tv shows before movies, which include 500mb Big Bang Theory mkv files and 1gb Top Gear mkv files at 720p. Neither play at all in the stock player and play very badly in Dice or other players.
I can't wait until ICS on the Xoom FE, I'm betting it fixes a lot of my issues. Such as the browser constantly force closing and my wifi slowing down the longer the tablet is on.
I heard this was possible, could someone elaborate on how this is done? Thank you
Do *not* attempt to flash ROMs across devices. Each ROM contains a customized set of drivers and configuration settings specific to your phone. Even if what you suggest is possible (it shouldn't be, but sometimes the safeguards aren't as strict as they should be) and you'll wind up with a phone where the hardware buttons don't work, or the touchscreen is off, or the battery doesn't charge correctly, or... yeah, just don't. Unless the hardware really is the next best thing to identical (and I mean the actual, internal chips and such, not the look of the device's chassis) it is pretty much guaranteed to cause more problems than it will solve.
Despite all apps/menus being fast, the Sensation 4G still feels sluggish due to a significant touchscreen input lag, also known as "touch lag" or "touchscreen latency". I see the same amount of lag with clean installs of stock GB 2.3.4 and ICS ARHD 6.6.1 /w overclock to 1.6Ghz.
This video/article (of a Galaxy SII) illustrates the problem.
Here is another video showing the effect that I'm talking about.
I've tried increasing/decreasing the "windowsmgr.max_events_per_sec" in build.props but that only affect smoothness, not overall lag or latency in following my finger. I've been using the free "Touch Test" app to compare different phones. The iPhone 4 and Galaxy S Blaze have MUCH less lag, and hence feel more responsive overall. The Blaze is an Android phone, so all of Android is not to blame (as the first video suggests).
Is there a hidden setting somewhere to help fix this or is the touch sensor in the Sensation just too slow? A fix for ARHD ICS would be ideal since I plan on running that.
UPDATE
I am a programmer but new to Android and mobile platforms. Assuming the touch screen is implemented as a polling input device, is a kernel hack that increases the polling rate possible? I am looking at the Sensation ICS kernel driver code, but I have no idea what I'm doing... Not even sure which driver's are applicable to the touchscreen yet...
Nvm, we need to decrease the touchscreen latency, polling rate won't affect that...
UPDATE
The following seem to have no effect on the touch lag:
Upgrading to ICS with ARHD 6.6.1 or Virtuos 4.0.1
Using Sebastian or faux123 kernels for ARHD
Overclocking up to 1.7Ghz
Using SuperCharger /w or w/o Nitro Lag Nullifier
Increasing/decreasing windowsmgr.max_events_per_sec in build.props
I have never experienced any lag at all with my phone running ARHD...
I cant recall seeing any threads regarding this either ??? Maybe its a hardware fault ?? If it is a really noticeable severe lag
azzledazzle said:
I cant recall seeing any threads regarding this either ???
Click to expand...
Click to collapse
This (old) thread mentions the Sensation. There are a couple threads around in other phone forums (SGS2 and DROIDX)
azzledazzle said:
Maybe its a hardware fault ?? If it is a really noticeable severe lag
Click to expand...
Click to collapse
It is not "severe". I have 2 Sensations and both behave similarly. I'm new to Android so maybe its just something I'm not used to, but seeing as how the Galaxy Blaze 4G hardly has any, the Sensation seems slow by comparison.
Really it seems like there should be a (hidden) setting somewhere because the CPU isn't struggling in the slightest. If the touch digitizer is just slow though, then there is no hope...
Well certain kernels and tweak apps have lots of hidden features. GPU rendering and such.... I dont really understand what they all are because i dont have any issues, so i dont bother to learn about things that dont affect me lol
maybe you could try a custom kernel and install leedroid tweaks. ??
azzledazzle said:
maybe you could try a custom kernel and install leedroid tweaks. ??
Click to expand...
Click to collapse
Yeah, I'm in the process of just trying everything. I was hoping maybe someone knew something about it so that I could avoid the shotgun approach
Ideally the fix would be a setting at the firmware level. The lag is even apparent in 4EXT and CWM Touch for example. But I would gladly settle for a kernel level hack so I have fast touch when actually using my phone...
demonsavatar said:
Despite all apps/menus being fast, the Sensation 4G still feels sluggish due to a significant touchscreen input lag, also known as "touch lag" or "touchscreen latency". I see the same amount of lag with clean installs of stock GB 2.3.4 and ICS ARHD 6.6.1 /w overclock to 1.6Ghz.
This video/article (of a Galaxy SII) illustrates the problem.
I've tried increasing/decreasing the "windowsmgr.max_events_per_sec" in build.props but that only affect smoothness, not overall lag or latency in following my finger. I've been using the free "Touch Test" app to compare different phones. The iPhone 4 and Galaxy S Blaze have MUCH less lag, and hence feel more responsive overall.
Is there a hidden setting somewhere to help fix this or is the touch sensor in the Sensation just too slow? A fix for ARHD ICS would be ideal since I plan on running that.
Click to expand...
Click to collapse
i have the same lag i had the lag from gb rom and now on ics arhd i really hate it when you touch somewhere and it shows the touch later rather than picking it up straight away
Recommend v6 supercharger and nitro lag nullifier. Makes my 1.5GHz sensation feel like 1.8GHz!
http://forum.xda-developers.com/showthread.php?t=991276
sent from HTC Pyramid using Tapatalk
The easiest way to see the lag if you have an ICS rom installed is enable Settings->Developer Options->Show touches. Move your finger around on the screen and see how far back the dot trails your finger.
Shery4life said:
i have the same lag
Click to expand...
Click to collapse
Good to know I'm not the only one. I think more people may have it, but they are used to it?!? If this could be fixed it would make the phone feel much faster. I actually played with a single-core lumia 710 windows phone and the touchscreen responds quite fast. Same thing with Iphone 4. This is part of how Microsoft/Nokia/Apple make their slow hardware feel fast.
stringer7 said:
Recommend v6 supercharger and nitro lag nullifier.
Click to expand...
Click to collapse
Tried these. Supercharger is also an option when installing ARHD, which I did choose. Nitro Lag Nullifier is a bunch of build.prop settings which didn't make a difference in the touch lag.
here watch this video
http://research.microsoft.com/apps/video/default.aspx?id=160670
and tell me in which latency htrc senastion falls
and also with you experience can you also tell which one iphhone 4 falls under
here what i think about all the andriod that they have latenc of 100 millisecond
and for iphone, ipad, and ipod have latency of 50 millisecond
and since i have used alot of andriod devices i think that some andriod devices have latency of 200 millisecond or more
but for iphone i think that there latency are 50millisecond
Shery4life said:
here watch this video
http://research.microsoft.com/apps/video/default.aspx?id=160670
and tell me in which latency htrc senastion falls
and also with you experience can you also tell which one iphhone 4 falls under
here what i think about all the andriod that they have latenc of 100 millisecond
and for iphone, ipad, and ipod have latency of 50 millisecond
Click to expand...
Click to collapse
Yeah I saw that video. Not sure how fast they are moving their finger, but if we are talking in relative terms, the Sensation is definitely in the 100ms range, the Windows phone is somewhere between 100ms and 50ms. The iPhone and the Galaxy Blaze are around 50ms. Again, these are relative comparisons, the numbers dont mean much unless we know how fast he is moving his finger in the video.
The limit is clearly not the entire Android platform as the Galaxy S Blaze responds quickly.
I am looking through the kernel driver code to see if anything makes sense. I am a programmer but I've never touched Android or mobile platforms before, so I have no idea what I'm doing...
Any DEVs with kernel and driver experience care to join the discussion? I'm guessing the touch screen is implemented as a polling input device. If we can increase the polling rate, it may go faster. Of course, the hardware may impose some limit on that...
UPDATE: I just realized polling rate has nothing to do with it. It is just input latency. Harder problem to fix...might just be hardware limitation.
demonsavatar said:
Yeah I saw that video. Not sure how fast they are moving their finger, but if we are talking in relative terms, the Sensation is definitely in the 100ms range, the Windows phone is somewhere between 100ms and 50ms. The iPhone and the Galaxy Blaze are around 50ms. Again, these are relative comparisons, the numbers dont mean much unless we know how fast he is moving his finger in the video.
The limit is clearly not the entire Android platform as the Galaxy S Blaze responds quickly.
I am looking through the kernel driver code to see if anything makes sense. I am a programmer but I've never touched Android or mobile platforms before, so I have no idea what I'm doing...
Any DEVs with kernel and driver experience care to join the discussion? I'm guessing the touch screen is implemented as a polling input device. If we can increase the polling rate, it may go faster. Of course, the hardware may impose some limit on that...
UPDATE: I just realized polling rate has nothing to do with it. It is just input latency. Harder problem to fix...might just be hardware limitation.
Click to expand...
Click to collapse
I live in UK and I don't think we have galaxy blaze in UK but then again I can be wrong
But like I said I have used iPhones iPod and iPad and the experience I had from these devices made me think that the latency is around 50 and my phone like sensation have 100 and I'm not sure if galaxy s2 have 100 or 50 latency but one thing I can say is that s2 is much more responsive than any other android I have used. But compare to iPhone I would say it is a bit laggy and I would put it around 75 and even 75 latency touch experience is still better than 100 I would love it manufacturer stay making new devices with 1 latency. But even if they bring out 10 latency I wouldn't mind but to keep the devices with 100 latency I think is bull**** and as a customer I will love a device with good touch experience.
Sent from my HTC Sensation using xda premium
demonsavatar said:
Yeah I saw that video. Not sure how fast they are moving their finger, but if we are talking in relative terms, the Sensation is definitely in the 100ms range, the Windows phone is somewhere between 100ms and 50ms. The iPhone and the Galaxy Blaze are around 50ms. Again, these are relative comparisons, the numbers dont mean much unless we know how fast he is moving his finger in the video.
The limit is clearly not the entire Android platform as the Galaxy S Blaze responds quickly.
I am looking through the kernel driver code to see if anything makes sense. I am a programmer but I've never touched Android or mobile platforms before, so I have no idea what I'm doing...
Any DEVs with kernel and driver experience care to join the discussion? I'm guessing the touch screen is implemented as a polling input device. If we can increase the polling rate, it may go faster. Of course, the hardware may impose some limit on that...
UPDATE: I just realized polling rate has nothing to do with it. It is just input latency. Harder problem to fix...might just be hardware limitation.
Click to expand...
Click to collapse
Sorry to resurrect an old thread, but there isn't much discussion on the internet going on regarding this issue. I used to own a HTC Desire (Oxygen Rom 2.3) and recently upgraded to a Galaxy S3 (LTE) and the input latency is no different. I have also tested using hardware controllers via bluetooth such as Wiimotes and PS3 gamepads, same results on 2 very different devices.
I was planning on using my device for some emulation (SNES, etc) but the input latency makes platforming games unplayable. I've read that AMOLED screens are supposed to be as responsive (in both pixel reponse and input delay) as plasma screens, so I'm pretty sure that the screen hardware isn't at fault here. From the little information I have scrounged together from the internet, it is the Android OS and the way it is written. All devices, all applications.
When my HDMI adapter for my S3 arrives, I'm going to test using both the touch screen and a hardware gamepad on a screen I know to have negligible input lag.
Some people aren't sensitive to noticing input latency, but its very frustrating for people like me that do. I have a quad core in my pocket with 2GB ram and I'm dealing with 100ms+ input latency in everything I do, despite getting awesome buttery smooth frame rates.
iOS has Android beat in this area, and I'm yet to use one yet, but the Microsoft Surface is said to boast a 1-2ms delay on their touch input.
Knowing that my hardware is more than capable of great response makes me sad. But I have a feeling that rom nor kernel alone can fix this issue.
Hello,
I would like to ask you, the experienced modders and users of xda, what CFW would you recommend me to install in case I'm looking for a long lasting battery and a smooth experience (rather a minimalistic system than a sleek, but laggy one)? I basically only use my PhQ for reading and writing SMS messages and e-mails, for web browsing, for chatting and internet (video)telephony. Occasionally I watch a YT video or use the GPS navigator.
Given the fact, that the phone has only 1 GB RAM and a 1.5 GHz dual-core processor, would you recommend me flashing it with the up-to-date LineageOS 14.1, or shall I stay with the older, but (supposedly more) stable build of CM 11? Or is there a different (slim) CFW, that would provide me high stability, fast response and good battery life?
Thanks.
I'd use newer than CM11 for sure. Lollipop (CM12) uses ART which makes stuff faster, and improved battery usage, so that's the minimum I'd consider.
I dunno exactly which version off the top of my head, but somewhere later than CM11 ZRAM was added, which keeps stuff from swapping to disk as often, so faster. F2FS support was also added, so if you reformat data/cache as f2fs before you install, that'll speed up disk access too.
I personally see no reason not to use the latest since it has all that, and is officially supported, so if you find something wrong there's people to talk to...
Well, maybe it was just my wrong assumption, but I thought I might want to keep using CM11, because I had read and heard, that Android 5.0 and above had higher HW requirements compared to Android 4.4.4, possibly making the phone with such specifications slower. On the other hand, I've read, that the RAM management and power management are both better with newer versions of Android, therefore I decided to post this question here and ask you xda guys (and girls) for your opinions.
You might be right, I'm no expert, and it's been quite a while since I ran kitkat. But lollipop (on our device) seemed faster to me, and battery definitely better. ZRAM also helps our low memory situation run modern apps, my understanding is it basically compresses what's in memory. Kinda like stacker did for hard drives back in the day if you remember the early 90s. So yeah, it slows down memory access all the time. However, the OS has to swap apps you're not actively using to disk when it needs memory for your current app, and in worst case scenario even will swap background apps out of memory that you expect to remain active. So by using zram, you get effectively more ram even tho its slower to access it, but overall makes things faster. And people who've done actual tests can confirm f2fs speeds things up on any device. I only just started using nougat myself so dunno how it affects performance, probably not any better than CM12/CM13 with zram implemented and f2fs format...
I belive KitKat even supports zram, but as far as I know wasn't implemented in CM11 for our device.
Also, dunno if it was in L or M, but you can now utilize external_sd cards easier. Don't have to keep setting paths for camera/etc to use external_sd, it blends it with your internal storage somehow, haven't paid attention to how it works, but haven't had a need to mess with paths ever since, and since we have only 8GB internal, that's also another nice feature; one completely easily fill that up without any photos or even going crazy with apps. Apparently our device will even work with 128G SDcards, although I only have the same 32G I've used forever. So for me on this device, it's CM12 or newer.
Alright, thanks for your advice. I will appreciate any other input and experience, though.
I'm interested what others might say too actually, I wanna know if other people agree or disagree with me! But being this is an older device, not very active community anymore. Only reason I'm on here every day lately is cuz I just updated myself, which had me checking into things, and am now looking for help getting the keyboard working right (in another thread).
I was running CM11 cm-11-20150626-SNAPSHOT-XNG3CAO1L8-moto_msm8960_jbbl.zip
finally decided to try CM12.1 cm-12.1-20151007-SNAPSHOT-YOG4PAO339-xt897.zip
Its smooth so far, but I'd love to try the lastnightyly/snapshot you have from March 2016 @enigma9o7