I have a GALAXY S
I saw a friend who has LockScreen just as there are for Nexus
When he presses the button lock it looks like a TV screen off ...
http://www.youtube.com/watch?v=y-1yRPV3twk see from 0:56 sec
That's neat !
That's the standard standby animation for any 2.3 Android rom. It doesn't seem to be portable to other firmware as of now. Galaxy s is android 2.1.
Rockin' DJ05, Minimal Icognito, Clocked at 1.3Ghz
Related
Coming from an 8520 Blackberry Curve to the G2x I have made great leaps and bounds when it comes to OSes. For my review on my Rooted Leaked GB build on G2x I would just like to say the pros and cons that I have had since the moment I installed it 30 minutes after the leak.
Pros:
Very smooth thanks to LPP & ADW making the home screens amazing
Space to install games
Still shots on the 8mp camera is a beauty
Swype is a must on any phone for me now
Speed, speed, speed and more speed! Duel Core is a power house
Wireless tether is smooth as butter! (Main source of internet for my home)
Screen size is very different then the HD2, but it’s still unique and nice
Soft keys are very bright and glow very well when receiving notifications
Weight with a body glove case without clip backing is perfect!
Rooting was SUPER easy and installing Leaked GB was so simple
Bluetooth is A+ for the range on it! BT Stereo headphones work great!
4G phone, can be a pro and con due to T-mobiles "Largest SO CALLED 4G Network"
Cons:
Number 1 issue would be battery but solved with upcoming updates or switching to 2g only in settings
Speakers are not as loud as I would want them to be. Voice/Music
Speakers are also very low quality, distorting music/call if too loud
No notification light, but solved by Optimus 2X Touch app
Vibrate is not as strong as I would like (Can be solved by app?)
Touch screen can be a little buggy, also due to leaked GB maybe?
Slight jitter when swiping between home screens
Random app lock ups at least once every 3 days, VERY bearable
LCD bleed top left, bottom left and slightly in the right
No dedicated camera button
Lag when coming from standby, WidgetLocker maybe?
Video recording is sub-par but improves with settings in low light conditions
Keyboard lags. For example, typing a very long e-mail, text or post
Hangs on lock screen sometimes
Lag on trying to end a call when removing the phone from your ear
Some apps will lock the phone up forcing you to hold power to reboot.
4G seems to be the issue for my battery drains - Can go 15 hours on heavy use with 2G while switching to 4G for downloading apps and music
Overall:
One the best phones I have had a chance to have and even with the MINOR issues I have with the phone can be fixed with updates/patches/ROMs.
Once I find a way to increase the volume via an app and T-Mobile starts to build better 4G towers in my area then this phone will be perfect!
Vibrate can be altered with different roms. CM7 has a stronger vibrate. The initial builds was out of control. I think they toned it done some. Most phones don't have a dedicated camera button anymore, which is a shame. You can, however, map apps to Long-Presses. With CM7, long-press back = force close. Long-press home = default task manger or assign to an app. Long-Press menu = keyboard. Long-press search = whatever.
ADW has been known to be laggy on the Tegras, but Launcher Pro has always been buttery smooth, even with the 3D effects. I think ADW has something to do with a driver issue or something.
CM7 also boosts the audio profiles. Coming from a Blackberry, the speakers are weak. Blackberry's have always had great speaker phones. The G2x is much better then some other devices I've had. Call quality on both ends still sounds pretty good.
Just a few tid-bits of information. Most of the stuff in the CON list, like you said, can be fixed with "updates/patches/ROMs".
Yeah I am holding off on making the switch to a CM7 nightly build..at least till its finished. I hate having to reinstall all my apps with titanium backup, takes forever.
But its bugging me so badly that I can't find the app or setting to change haptic strength!
Sent from my LG-P999 using XDA Premium App
player911 said:
ADW has been known to be laggy on the Tegras, but Launcher Pro has always been buttery smooth, even with the 3D effects. I think ADW has something to do with a driver issue or something..
Click to expand...
Click to collapse
Just a note...ADW EX is hands down smother than Launcher Pro since Hardware Acceleration was added (last update I believe). I just want to make sure that gets out there since I left ADW myself for awhile due to the lag...back now and loving it.
bdkinney said:
Just a note...ADW EX is hands down smother than Launcher Pro since Hardware Acceleration was added (last update I believe). I just want to make sure that gets out there since I left ADW myself for awhile due to the lag...back now and loving it.
Click to expand...
Click to collapse
Yeah I was going to say that as well since I'm using it after it was optimized for Tegra2 processors.
Also, found that it was Perfect Keyboard that has the haptic feed back strength setting. DANG IT!
Sent from my LG-P999 using XDA Premium App
@Zspy1985
So, how does GB compare to stock stability wise? I ran GB (CM7) exclusively on my HD2. I have been holding off on the g2x waiting for a CM7 RC...but I'm itching to flash.
bdkinney said:
@Zspy1985
So, how does GB compare to stock stability wise? I ran GB (CM7) exclusively on my HD2. I have been holding off on the g2x waiting for a CM7 RC...but I'm itching to flash.
Click to expand...
Click to collapse
To be honest Gingerbread only gives a few extra perks besides the black notification bar, the glow when you hit the top and bottom of web pages and option screens. The main reason why I LOVE GB is the copy and paste function! Makes me wonder how they never had the arrow in the first place to move your selector around either!
Sent from my LG-P999 using XDA Premium App
P.S. / edit
To really answer your question about GB vs stock Froyo: I would have to say that the leaked GB is perfectly fine for daily use besides the few hangs on lock screen sometimes, lag on trying to end a call when removing the phone from your ear and some apps will lock the phone up forcing you to hold power to reboot.
Once again some of my issues seem like they are caused by apps I'm using to replace stock apps.
Nexus s is my second droid, my first droid was humble zte blade, running custom rom modaco 2.2 ,3,5 inches OLED screen and 512 ram .
i could browsing over 3g all day long, meanwhile playing call of duty modern sandstorm ( yes mine blade could run that game very smoothly), and my screen never been even worm, only battery sometimes, but not noticeable.
But not the same with mine nexus, when my phone is set up at full brightness, 10-15 minutes on 3g and half top of screen is getting hot and i don't mean worm,i mean hot as same as the back cover, just above google logo.
I googled that issue and I've found lots of threads regarding hot like pan fry screen in nexus s on various forums, but not so many on xda.
So i'm asking; when my screen is at full brightness (looking then beautiful) and I'm using 3g for browsing and downloading and after 10- 15 minutes my screen and google logo is getting hot, IS THAT NORMAL or do i have faulty phone ?
Btw I'm running nscollab 1.6.0
I've found that setting my brightness at 50% kind of eliminate that problem, or at least making it usable, but what's the point in having such a screen if i can't use it fully ...
So if u have or u had such a
Issue , please share your experience in that matter.
Hello
I recently purchased a Ramos X10F on an impulse buy on a trip to the PP last month. I had been waiting longer than a year for an 8" 4:3 device that was not Apple with expandable memory and this one just made me succumb. Also I fell for the false data in marketing it as a cortex A9 and I thought a quad core A9 should be faster than my dual core A9 in the n7000. Actually it is a A5 or A7 (device details in cpuz mention some A7 blah).
The device has great potential to be an ipad mini killer (at $165) as the hardware fit and finish is very good, the screen is IPS and it weighs only 360 grams. I can hold it in one had lying in bed without tiring myself. However performance is marred by the stock android 4.1.1. Intially I thought it was slow nand flash as when I enabled cpu stats, the nand-rw-flash process appeared to be the top process for a longish time, each time it stalled. However I later discovered, the device is very laggy when Wifi is on while actual WiFi throughput is very good - I get almost full speed 16mbs in the speedtest.net results. Unfortunately even with entropy seeder and a deadline or noop scheduler, the lagginess is only partially improved. Also the old linux/android decision of using input to randomize and seed the entropy is only good for desktops not servers or touchpads. I have to tap a few times to get a app screen to respond inexplicably and suddenly and it shows that the OS was waiting on input. The device is best for streaming as typically once the app is opened I never have a problem with lag a it is typically 15 to 30 mins of viewing before switching apps. Otherwise the poor performance means a task that should take normal time (like reading news in the morning for 15 mins) takes more than twice the time as I have to struggle with the slow app launches and screen loading mostly. But if Wifi is switched off and content is cached, everything is smooth and much better. Battery life is decent with display brightness set around or below 10% typically.
So my recommendation for a new buyer is - dont buy until a custom ROM is made available. Dont fall for the x10pro video on the utube yet. Real world performance is not the same. Once the smoothness of the 4.4.x is acheived it will be a killer product. (It is not a weak cpu either, it is responsive and smooth with wifi off. Although the chip does not support out-of-order execution)
I would like to upgrade the android from its 4.1.1 to a 4.4.x version. Also this version is vulnerable to heartbleed and the openssl bug that came after that in June 2014. The omnirom 4.4.3 on my n7000 is really smooth and I am hoping somebody will develop a custom rom for this device.
But I dont see a custom ROM or CWM for this anywhere. I installed a CWM recovery for another ATM7029 device (yarvik) and it boots, but I forgot about the display driver compatibility and I can no longer view the menu in recovery mode. Otherwise rooted it and running ok.
The specifications of the device are as follows:
OS: Android 4.1.1
CPU: Quad Core ATM7029
GPU: Vivante GC1000
RAM 1GB，DDR3 --> False. Real RAM is 686MB.
Storage 8GB
Screen: Capacitive Touchscreen, 1024*768 Full resolution Screen
Size: 7.85 inch
Resolution: 1024*768 Pixels
Flash: Support Flash 11.0 and HTML 5
Extend Card Support TF card up to 32GB extended
Camera Dual Camera Front 2.0M,Back 5.0M
Gravity Sensor Yes
Multi-Touch Yes, 5 points touch
Android Market Yes
Skype Yes
Email and Browser: Yes, built in
WIFI: Yes, 802.11 b/g/n
3G : support external 3G dongle
OTG Function: Support USB Mouse,Keyboard (2.4GHz)
Support:FAT,FAT32,NTFS
Earphone Interface 3.5mm
Battery: 4000mAh
Link to the device blurb: http://www.ramos-tablet.com/ramos-x...et-mini-7-85-inch-screen-dual-camera-16g.html
What do I need to submit for a developer to build a custom rom for this device? Some kind of dump? Also need a recovery manager with the right display driver. Either TWRP or CWM.
I hope a developer will volunteer.
Thanks
G0bble
Anyone have this problem? I've enabled it in the voice settings to allow Google Now detection to always be on no matter what screen it's on, even at the lock screen.
The feature works on the Nexus 7 but doesn't work on my Nexus 5. Is there a way to force it to work or some kind of settings I can toggle to get it to work?
It would be brilliant is someone could port the OK Google with the screen off, adaptive display and double tap to wake !
jingletard said:
Anyone have this problem? I've enabled it in the voice settings to allow Google Now detection to always be on no matter what screen it's on, even at the lock screen.
The feature works on the Nexus 7 but doesn't work on my Nexus 5. Is there a way to force it to work or some kind of settings I can toggle to get it to work?
Click to expand...
Click to collapse
Firstly... didn't think the Nexus 5 hardware supported it as it doesn't have the low power processor. Secondly, on my nexus 9 it didn't work until I rebooted the tablet?
For me it works well...! I can say "Ok google" in the homescreen, when i'm on the browser and so on...even on the lockscreen, but obviously not when the screen is completely off.
mingoid said:
Firstly... didn't think the Nexus 5 hardware supported it as it doesn't have the low power processor. Secondly, on my nexus 9 it didn't work until I rebooted the tablet?
Click to expand...
Click to collapse
Al snapdragon 800 processors have that low power always listening chip
mingoid said:
Firstly... didn't think the Nexus 5 hardware supported it as it doesn't have the low power processor. Secondly, on my nexus 9 it didn't work until I rebooted the tablet?
Click to expand...
Click to collapse
Technically it does have the low power core, however it's being utilized as a pedometer.
sorcio91 said:
For me it works well...! I can say "Ok google" in the homescreen, when i'm on the browser and so on...even on the lockscreen, but obviously not when the screen is completely off.
Click to expand...
Click to collapse
It'll work with the screen completely off in you enable all 3 options. However the phone needs to be plugged in for it to work with the screen off.
jingletard said:
Anyone have this problem? I've enabled it in the voice settings to allow Google Now detection to always be on no matter what screen it's on, even at the lock screen.
The feature works on the Nexus 7 but doesn't work on my Nexus 5. Is there a way to force it to work or some kind of settings I can toggle to get it to work?
Click to expand...
Click to collapse
^
RoyJ said:
Technically it does have the low power core, however it's being utilized as a pedometer.
It'll work with the screen completely off in you enable all 3 options. However the phone needs to be plugged in for it to work with the screen off.
^
Click to expand...
Click to collapse
That's what it is! Thanks. it doesn't work if the device isn't being charged.
Anyone know if this is going to change?
The Moto X 2014 has a 801 and works with the screen off unplugged. It has to be achievable. That phone doesn't have any special chip besides the 801.
801 is just an overclocked version of 800... some dev should be able to port it from Nexus 6 or Moto X 2014
TigerCourage said:
The Moto X 2014 has a 801 and works with the screen off unplugged. It has to be achievable. That phone doesn't have any special chip besides the 801.
801 is just an overclocked version of 800... some dev should be able to port it from Nexus 6 or Moto X 2014
Click to expand...
Click to collapse
Wrong, the motox 2014 does have a special chip for that.
Motorola Mobile Computing System including 2.5GHz Qualcomm® SnapdragonTM 801 with quad-core CPU (MSM 8974-AC), Adreno 330 @ 578 MHz GPU, Natural Language Processor, Contextual Computing Processor
https://www.motorola.com/us/motomak...6M78H3z8ECFYataQodl4gASw#moto-x+1-story-specs
Before I upgraded my galaxy S6 to 6.0.1, the screen refresh rate/flickering was fine. That, and it was less laggy in general. I compared my S6 to my brother's Note 4 and his screen looks to be running smoother when swiping through the home screen although his phone is older. Has anyone else ran into this issue and is there maybe a fix in the developer options I can apply?