Related
Device Info:
Nook Color running B&N 1.2 (Android 2.2.1)
ManualNooter 4-6-16
OC at up to 1.2GHz using Froyo 1.2 dalingrin OC emmc 090111
Problem: Text in some apps cannot be seen (ie Titanium Backup "Filters" screen).
Observations: This problem seems to happen with B&N Software Versions ABOVE 1.2 (I am currently running 1.2 because of this issue).
Search Results: I've only found mention of this problem (or something close to it) in two places: HERE and HERE.
Recommended Fix or Workaround: NONE
I just inherited a Nook Color about three weeks ago, it was reset to factory defaults (B&N 1.1). The person I got it from was running B&N Software version 1.2 with the latest recommended ManualNootered version (manualnooter-4-6-16) at that time. He could not get B&N Version 1.3 to work right. When I got the Nook, the first thing I did was to update it to B&N 1.3 and root it with the latest ManualNooter procedures, which worked great (the procedures had been updated since the person I got it from had tried to root B&N 1.3). Thanks GabrialDestruir!
One of the first apps I purchased was Titanium Backup. I noticed in Titanium's Filters screen there were Radio Buttons that had no text next to them. I was brand new to Android and had a lot to learn, so I made note of this issue to return to later. When I finally got around to addressing this issue, I discovered others had the same problem, but so far it was not addressed within the development community.
In my experimenting I have crashed and re-rooted the device many times, so I know the problem is consistent. I was becoming frustrated and asked the previous owner if he had the same issue with B&N 1.2. He did not. As of this morning, I have returned to B&N Software Version 1.2 and I can now see all the text that was invisible before - in every app I've tested and remembered had the issue.
The specifications above are the only changes needed to reproduce the problem. As soon as I was up and running, I downloaded Titanium Backup from Market. When I rooted the Nook using B&N Software version 1.2, all text was visible. Following the procedures to get the system up to the same place with B&N 1.3, the text problem reappears (text disappears).
Any help with this problem would be greatly appreciated. If you have any questions for me or if I have forgotten a critical piece of information, please do not hesitate to post what you need here, I will be checking it daily.
Thank you for your time, effort, and help XDA! You've made a complicated procedure very simple.
I am experiencing the same problems with dialog boxes in many apps and widgets. I too have tried to find a solution.
Sent from my BNRV200 using Tapatalk
milliman said:
I am experiencing the same problems with dialog boxes in many apps and widgets. I too have tried to find a solution.
Sent from my BNRV200 using Tapatalk
Click to expand...
Click to collapse
Changing the dpi in build.prop to 160 helps, but does not cure the problem.
framitz said:
Changing the dpi in build.prop to 160 helps, but does not cure the problem.
Click to expand...
Click to collapse
Can I do that with LCD resolution?
This has always been a problem with the stock ROM, IIRC it's because typical Android text is Black and it's White on the stock ROM, therefore by default it's White on White in some apps.
If you don't need the Read to Me kids books or Magazines, use CM7 and the Nook market app, it doesn't have this problem and does much more.
khaytsus said:
This has always been a problem with the stock ROM, IIRC it's because typical Android text is Black and it's White on the stock ROM, therefore by default it's White on White in some apps.
If you don't need the Read to Me kids books or Magazines, use CM7 and the Nook market app, it doesn't have this problem and does much more.
Click to expand...
Click to collapse
Yea, so far, that's what I figured - the Nook is using a white background and if a program does not explicitly define the background and foreground text colors, but assumes the background is black, this is when the problem occurs.
I guess what I was wondering is if there is a way to change the default background color for the Nooks to black, and the default foreground text color to white. I read somewhere about "theme-ing," though, like I said, I am new to Android, could theme-ing be a solution?
I don't get your second statement. I already use CM7 (but only so far as for booting to use ManualNooter), and I have no idea what "Nook market app" you are referring to, or the Kid Reading stuff - do you meant the stock B&N stuff?. Am I missing a key concept here?
Or, possibly, are you suggesting I use CM7 to install a different ROM and skip the Nooter method altogether? I was actually beginning to research this - I can do without all the B&N stuff, it doesn't work right anyway and I have disabled much of the B&N apps. If flashing a different ROM fixes this and "does much more," I'm all for it. It will just take me doing a little more research and someone confirming this is what you are referring to.
khaytsus said:
This has always been a problem with the stock ROM, IIRC it's because typical Android text is Black and it's White on the stock ROM, therefore by default it's White on White in some apps.
If you don't need the Read to Me kids books or Magazines, use CM7 and the Nook market app, it doesn't have this problem and does much more.
Click to expand...
Click to collapse
I see! I will have to see if I can dig into the nook a little deeper and see if I can do anything about that. It is annoying but I'm not annoyed enough to change to CM7 yet! Plus I have a People subscription that I am enjoying ATM.
Trasd..You are using CWM to boot to manual nooter. CM7 is something else.
Anemailname said:
Trasd..You are using CWM to boot to manual nooter. CM7 is something else.
Click to expand...
Click to collapse
Ah, thank you, I was wondering how some people were runnig higher versions of Android - now I know.
Is it weird I love this stuff?
Well, as they say, back to the drawing board....
EDITED
The theory below is NOT the problem, but I left it up because I cannot delete it and is serves as reminder. Sorry.
ORIGINAL
I have made a discovery; the problem seems to happen, not because of background color assumptions, but when styles are used (an app developer, who was kind enough to debug and redesign his app for me, discovered this).
I am almost to the point in my self-education with Android and Java programming that I can verify this myself, but I am not quite there yet. If someone does verify this, could you please post your findings here?
As you can tell, I haven't flashed the ROM yet, and may not for awhile. It's running OK and I really want to concentrate on programming for the time being.
As more and more developers use styles though, I may not have a choice.
Hi, after installing a new kernel with multitouch and norefresh through CWM, and considering installing the overclocked one by guevor (update: installed oc kernel), but I had some newbie questions about restoring the Kernel in case I wanted to go back to stock or update to 1.2.1.
I have taken full factory backups at 1.0.1 with noogie by copying the physical disk with diskimage, and another backup with the 1.2 rooter gui. I have since updated to 1.1 (no backup on 1.1) and rooted before I installed the new kernel. Is there any way to revert to the default kernel on 1.1.0?
Also, Is there any way to adjust the contrast in fastmode? The text is barely readable and an unusual amount of gosting (maybe something is wrong), but it's super fast.
Thanks so much, and this community has been a lifesaver since last night when I got my nook. Go easy on me since I've only had my nook for a few hours, I've been reading a lot and searching these forums for hours.
Also, bonus questions:
1. Is it possible to set a custom wallpaper (behind the icons)
2. Is it possible to actually decode/play videos? no video apps seem to work, even p2p ones.. also youtube videos / flash doesn't work which is strange because android 2.1 should support video right?
3. What's the consensus about screen damage/use using fast mode? Brand new nook.... lol. I'm not sure if I'm shortening the 10 year life of the e-ink display to 1 week.
jun127 said:
Hi, after installing a new kernel with multitouch and norefresh through CWM, and considering installing the overclocked one by guevor (update: installed oc kernel), but I had some newbie questions about restoring the Kernel in case I wanted to go back to stock or update to 1.2.1.
I have taken full factory backups at 1.0.1 with noogie by copying the physical disk with diskimage, and another backup with the 1.2 rooter gui. I have since updated to 1.1 (no backup on 1.1) and rooted before I installed the new kernel. Is there any way to revert to the default kernel on 1.1.0?
Also, Is there any way to adjust the contrast in fastmode? The text is barely readable and an unusual amount of gosting (maybe something is wrong), but it's super fast.
Thanks so much, and this community has been a lifesaver since last night when I got my nook. Go easy on me since I've only had my nook for a few hours, I've been reading a lot and searching these forums for hours.
Also, bonus questions:
1. Is it possible to set a custom wallpaper (behind the icons)
2. Is it possible to actually decode/play videos? no video apps seem to work, even p2p ones.. also youtube videos / flash doesn't work which is strange because android 2.1 should support video right?
3. What's the consensus about screen damage/use using fast mode? Brand new nook.... lol. I'm not sure if I'm shortening the 10 year life of the e-ink display to 1 week.
Click to expand...
Click to collapse
I. http://nookdevs.com/Nook_Simple_Touch_restore_to_stock
II. No. Try to change font in your reader. http://forum.xda-developers.com/showpost.php?p=20069292&postcount=10
or use NoRefresh to read text.
or try different reader for eg. https://code.google.com/p/apv/downloads/list
1. if you change your launcher from 'ReLaunch' to for eg. 'LegacyLauncher' then yes.
2. RockPlayer + software decoding = playing videos
https://play.google.com/store/apps/details?id=com.redirectin.rockplayer.android.unified.lite&hl=en
3. Your battery will probably die faster than the screen. I used NoRefresh and FastMode from the start and the screen still works fine. On the other hand my battery died (2 weeks before the end of warranty).
osowiecki said:
I. http://nookdevs.com/Nook_Simple_Touch_restore_to_stock
II. No. Try to change font in your reader. http://forum.xda-developers.com/showpost.php?p=20069292&postcount=10
or use NoRefresh to read text.
or try different reader for eg. https://code.google.com/p/apv/downloads/list
1. if you change your launcher from 'ReLaunch' to for eg. 'LegacyLauncher' then yes.
2. RockPlayer + software decoding = playing videos
https://play.google.com/store/apps/details?id=com.redirectin.rockplayer.android.unified.lite&hl=en
3. Your battery will probably die faster than the screen. I used NoRefresh and FastMode from the start and the screen still works fine. On the other hand my battery died (2 weeks before the end of warranty).
Click to expand...
Click to collapse
Thanks for your help! I've seen you around the forums quite a bit and learned a lot from reading your past posts.
I was able to play rmvb with rockplayer (still in beta?), but couldn't figure out how to make the streaming p2p tv applications work (also rmvb) such as PPTV, and PPS which usually work on everything (although they installed properly and also tried downloading and installing codecs. I had to download the rmvb file from pptv and play it manually on rockplayer.
Thanks for the Legacy Launcher tip, looks great! Edit: Unfortunately I can't get wallpapers to work there either. When I select wallpaper, it gives me 2 options, from pictures, or from wallpapers. pictures shows "no media", and wallpapers are just a few standard wallpapers. I can't find anywhere to select a picture from the SD card, and I can't find any "media" or wallpaper folder in file browser. UPDATE: I was able to get wallpapers by downloading the app "wallpaper changer" and "ES file explorer".
Interesting to know about the battery, I was also worried about that. I managed to suck through 35% of the battery in 5 hours. I didn't buy the official wall charger, but I used a chinese 5 volt adapter I had laying around after I kept getting the following problem:
Another problem I've been having is that when I plug the NST into my computer via USB everything goes ballistic on my nook, it rapidly connects and drops USB mode, and then if I go into settings both internal storage and SD card are greyed out "unavailable". What could cause that?
Finally, is there anyway to get ADB on windows without downloading the entire android SDK? I want to apply the IMEI fix to install whatsapp, but I can't get ADB to work at all. UPDATE: I solved it, adb.exe baby and I guess you can use that with commander. My problem was the default wireless adb app wasn't working, I installed wifi adb and it worked. Very odd, since usb connection didn't work, but at least I got my IMEI and whatsapp. Any methods for getting working contacts on NST? I'm going to try the contacts.db workaround if there is no other options, but I'm hoping for something less risky and automated.
I also wanted to note that I solved the 24 hour wait time on google market, go to gmail and add a second contact and sync that contact. The first google account will automagically work.
jun127 said:
...
Click to expand...
Click to collapse
1. I think that 'nook' launches 'hardware video decoding' by default when you try to open up a stream from the apk so the only option is to download videos and play them locally. 'TubeMate' is able to do this.
http://m.tubemate.net/
On the other hand if the apk contains a video player with 'software decoding' this could work like it should.
I know that 'BeyondPod' was able to play audio podcasts from within application. Haven't tested it on videos.
https://play.google.com/store/apps/details?id=mobi.beyondpod&hl=en
2. Don't forget to turn all useless animations in the Launcher off and get "Minimalist Black - ADW Theme'. You can find it in 'TouchNooter' package.
3. Try to use a different micro usb cable. Sounds like yours is broken.
4. In the current version of NookManager, ADB through USB is not supported.
5. Can't help you with that right now.
Hello, i installed http://forum.xda-developers.com/showthread.php?t=1906507 kernel, adn i wanted to test FastMode.
And i noticed than is useless, because i have horrible ghosting effects - it's hard to read anything in browser.
It's normal?
Shissu said:
Hello, i installed http://forum.xda-developers.com/showthread.php?t=1906507 kernel, adn i wanted to test FastMode.
And i noticed than is useless, because i have horrible ghosting effects - it's hard to read anything in browser.
It's normal?
Click to expand...
Click to collapse
The initial ghosting occurs (at least in fastmode2.apk) because the apk does not perform 1 full screen refresh after the start (yet).
Try to lock and than unlock the device after starting fastmode2.apk.
The other reason may be that you have 'NoRefresh' installed and it autostarts on boot.
Never use both NoRefresh and FastMode at the same time.Kill one or another using TaskXP (or similar apk).
Edit:
Yeah. I have checked it. Applying 1 full refresh helps a lot. (you can also try do display a white full screen image to get the same result).
If you have time you can edit the source of fastmode2.apk. I won't do this during this week for sure.
osowiecki said:
Applying 1 full refresh DOES NOT helped me.
Click to expand...
Click to collapse
I do not mean any offence but FastMode2 does the trick but with terrible ghosting. Nevertheless thanx to osowiecki
Mnurlan said:
I do not mean any offence but FastMode2 does the trick but with terrible ghosting. Nevertheless thanx to osowiecki
Click to expand...
Click to collapse
What I meant by performing a 1 full refresh :
1. you can see extensive ghosting
2. I push the lock button, the screen blinks (full refresh)
3. After unlocking there is no (a little) ghosting effect.
It would be nice to force fullscreen refresh after fast mode gets activated.
Alas, That is not an acceptable solution for me (still poorly readable), I think the only way to get the NST working with normal resolution is to rollback to factory settings and install the FW with which this mode is working.
Now I realize that there is no way of getting any FW earlier than 1.2.1. I am stuck.
Mnurlan said:
Alas, That is not an acceptable solution for me (still poorly readable), I think the only way to get the NST working with normal resolution is to rollback to factory settings and install the FW with which this mode is working.
Now I realize that there is no way of getting any FW earlier than 1.2.1. I am stuck.
Click to expand...
Click to collapse
"lurk moar"
stock image 1.1 for CWM
https://code.google.com/p/nst-recovery/downloads/detail?name=nook_1_1_update_cwm.zip&can=2&q=
Also..why not use NoRefresh then?
Both modes work on kernel v166.
Mnurlan said:
Now I realize that there is no way of getting any FW earlier than 1.2.1. I am stuck.
Click to expand...
Click to collapse
1.1.2 FW straight from B&N
Also..why not use NoRefresh then?
Click to expand...
Click to collapse
Yes, agree, I am a "lurk more" and thank you for the link - I would never be able to find it myself. We, Russian speaking people, used to say "to make someone's nose pointed in the right direction" . The only thing is I am not sure now that downgrading the FW is the right thing to do as they say that the performance was improved in 1.2.1.
I've tried every NoRefresh I could find, even some NoRefreshToggle-debug2.apk, they seem to be having no effect whatsoever so far.
2 straygecko - link seems to be incorrect. Thank you nevertheless.
Mnurlan said:
Yes, agree, I am a "lurk more" and thank you for the link - I would never be able to find it myself. We, Russian speaking people, used to say "to make someone's nose pointed in the right direction" . The only thing is I am not sure now that downgrading the FW is the right thing to do as they say that the performance was improved in 1.2.1.
I've tried every NoRefresh I could find, even some NoRefreshToggle-debug2.apk, they seem to be having no effect whatsoever so far.
2 straygecko - link seems to be incorrect. Thank you nevertheless.
Click to expand...
Click to collapse
What do you mean by "no effect"?
You should run NoRefresh once (it starts it's deamon), then you run in the second time to get results.
By default the contrast options are set to "auto". Go to "NoRefresh Settings"->"Contrast Settings" and select "appear always".
Add shortcut to NoRefresh to 'quicknav' bar or any other place that you can always reach on the screen.
NoRefresh works only within the application that it was started with. When you change the focus to another apk, it stops.
If you are on stock kernel and 'NoRefreshToggle-debug2.apk' does not work, that means you don't have FW 1.2.1 installed.
Seems like I've now got a bricked device, neither Noogie, nor CWM can help - my PC doesn't "see" my NST anymore and I can't replace the uImage, the NST itself is working now, but this means I will not be able even to restore it to a saved image:crying:
A day later I've found out that for some reason my desktop PC ("floortop") refuses to "recognize" my NST (although "sees" it alright without Noogie or CWM), then I have managed to replace uImage on my NST using my son's laptop, yet FastMode is not working, same as NoRefresh, FW 1.2.1 (I'm positive), FastMode2 works fine but resulting view renders it useless.
Update: 26.04.2013 - NoRefresh is working, but the resulting resolution renders it also almost unusable. Just delivering my SitRep, not whining. Installed kernel 166 with CWM.
dots
I have same problem in addition dots. I tried different software versions(1.1.0-1.2.1), different root methods(nook manager, touchnooter, minimal touch) and also different kernels with all variations. But no change. Screen resolution is awful because of dots and ghosting. What the wrong?
View attachment 2413476
View attachment 2413477
View attachment 2413478
eraycr said:
I have same problem in addition dots. I tried different software versions(1.1.0-1.2.1), different root methods(nook manager, touchnooter, minimal touch) and also different kernels with all variations. But no change. Screen resolution is awful because of dots and ghosting. What the wrong?
View attachment 2413476
View attachment 2413477
View attachment 2413478
Click to expand...
Click to collapse
Same here, try many kernels.
I thought it was normal operation of this modification. Oo
Well, I'm late to the party, having generated an apparently useless post here. But I agree with you all who are underwhelmed with the screen appearance using either of these two mods. I like the sprightly Android performance of the NST in FastMode, but there really is a lot of visual "noise" on the screen. NoRefresh is even worse on my Nook. I can hardly get an image at the beginning, the screen is almost an all white overlay so the contrast buttons don't do me any good because I can't see much through the white film (sort of like a bad cataract!). Scrolling a bit gradually brings in a fractured image and by the time the app has closed.
I've tried disabling the NoRefresh app entirely to see if FastMode would work better. No deal. Same poor image quality. Nothing like some of the YouTube videos I've seen.
FW 1.21, kernal 166.
But who knows? At least multi-touch is nice.
I have downloaded the XDA omni rom for A500:
Freshly built Android 4.4.2 ROM based on Omnirom KitKat !
"The Team 'IconiaHD' is proud to present a new ROM for your Acer A500 or A501 tablet.
This small team is composed of:
- HenrikE: A200 owner, responsible for an unofficial CM-10.2 build for the A200
- Doume: A200 owner, experienced linux developer
- macia10: A501 owner, tester"
The omni rom installs easily using TWRP ver 2.7 by Thor. Once I followed the OP recommendations all stages in the installation were clear. The rom runs well after the second and third boot. I even used ART. Here is my take so far: rom is fast and smooth. Browsers load pages fast, even high image content sites (CNN). Videos on youtube work flawlessly, wifi signal is very strong. I was able to load all my apps and have them run well. A very nice and responsive rom on the acer a500. Google play store works right off the bat. A few minor issues though: google music play app has a bit of chopping of the music playback. Netflix did not work for me as the app would force closed on me. I tried the netflixfix as recommended by the OP but it did not work either ( I am waiting for the next fix as suggested by the OP). Other than those two minor issues I can't wait to try the updated versions of this omni rom as it adds a new life to this acer a500. I am very happy to see that there are developers who continue to get value for us by implementing optimized roms on the a500. Thank you for your great work.:good::good::good::good:
D.
Anyone running this on the N7100?
deryckmeister said:
I have downloaded the XDA omni rom for A500:
Freshly built Android 4.4.2 ROM based on Omnirom KitKat !
"The Team 'IconiaHD' is proud to present a new ROM for your Acer A500 or A501 tablet.
This small team is composed of:
- HenrikE: A200 owner, responsible for an unofficial CM-10.2 build for the A200
- Doume: A200 owner, experienced linux developer
- macia10: A501 owner, tester"
The omni rom installs easily using TWRP ver 2.7 by Thor. Once I followed the OP recommendations all stages in the installation were clear. The rom runs well after the second and third boot. I even used ART. Here is my take so far: rom is fast and smooth. Browsers load pages fast, even high image content sites (CNN). Videos on youtube work flawlessly, wifi signal is very strong. I was able to load all my apps and have them run well. A very nice and responsive rom on the acer a500. Google play store works right off the bat. A few minor issues though: google music play app has a bit of chopping of the music playback. Netflix did not work for me as the app would force closed on me. I tried the netflixfix as recommended by the OP but it did not work either ( I am waiting for the next fix as suggested by the OP). Other than those two minor issues I can't wait to try the updated versions of this omni rom as it adds a new life to this acer a500. I am very happy to see that there are developers who continue to get value for us by implementing optimized roms on the a500. Thank you for your great work.:good::good::good::good:
D.
Click to expand...
Click to collapse
I'm filing a report with the moderators to put this into device-specific forums, as you're issuing a report against an unofficial build that, to my knowledge, no one involved with the bringup has attempted to get merged officially. (I'll check with the merge guys tonight on that...)
Entropy512 said:
I'm filing a report with the moderators to put this into device-specific forums, as you're issuing a report against an unofficial build that, to my knowledge, no one involved with the bringup has attempted to get merged officially. (I'll check with the merge guys tonight on that...)
Click to expand...
Click to collapse
Thanks for directing me to the right forum.
Sent from my A500 using XDA Free mobile app
Further Update on XDA OMNI for Acer a500 (unofficial)
I have been running this rom for the past few weeks. Here is what I have noticed. I hope that this will help further the development of the rom. I am attaching the logcat information.
a). Recent update from Google Play Music fixed the audio glitches I was having before.
b). Chrome Browser runs well has problems playing videos, causes browser FC (flash issue?). Lightening Browser works well.
c). Occasional window change results in zoomed icons in the apps section.
d). Netflix still FCs.
e). Network Location works on my Acer A500.
f). Youtube works without any issues.
D.
deryckmeister said:
I have been running this rom for the past few weeks. Here is what I have noticed. I hope that this will help further the development of the rom. I am attaching the logcat information.
a). Recent update from Google Play Music fixed the audio glitches I was having before.
b). Chrome Browser runs well has problems playing videos, causes browser FC (flash issue?). Lightening Browser works well.
c). Occasional window change results in zoomed icons in the apps section.
d). Netflix still FCs.
e). Network Location works on my Acer A500.
f). Youtube works without any issues.
D.
Click to expand...
Click to collapse
Thanks for the report! Interesting that network location works for you. It seems to work sometimes and sometimes not, would be nice to figure out why..
The latest versions of netflix don't work, even with the fix applied. Try version 3.1.2 instead: http://gsmandroidapps.com/download-netflix-3-1-2-build-1142-apk/
I haven't seen the problem with zoomed icons, does it happen often?
HenrikE said:
Thanks for the report! Interesting that network location works for you. It seems to work sometimes and sometimes not, would be nice to figure out why..
The latest versions of netflix don't work, even with the fix applied. Try version 3.1.2 instead:
I haven't seen the problem with zoomed icons, does it happen often?
Click to expand...
Click to collapse
You're welcome. The Netflix 3-1-2 build works after installing and subsequently rebooting! Thank you. The zoomed icons happens infrequently and occurs only when I go into the apps windows from the home screen. It seems to be more of a lag issue when switching windows. I installed Apex launcher and the lag has decreased significantly. In addition, the zoomed icons are no longer present.... so far. I have decided to use Dalvik runtime as the Art function is not compatible with some of my apps.
D.
omni rom for acer A501 by HenriKe
I have tried to flash this ROM several times andi keep having issues. I am on Acer 501.
Op still says to use the 4-27 build for 501 as the 4-29 build has issues.
Issues I have at multiple force reboots. (Kernel panics). Also if data is enabled then WiFi will not connect. I know I should have saved the last_kmsg but just sipped and restored previous ROM.
Still waiting for the fixed 501 version to be posted.
As stated here = http://forum.xda-developers.com/showpost.php?p=52709444&postcount=109
Some tweaks that make this Rom smooth.
I would like to suggest the following tweaks that will make your experience with this rom smoother. Make sure you have a complete backup of your a500 current system. Use these at your own risk.
Before installing rom:
1. Wipe cache, wipe Dalvik cache, "real format" data (very important).
Installation:
2. Install rom, install mini-gapps, install super user
3. Boot up rom. Set up Wifi, Set up Google play services.
4. Reboot.
5. Make a complete back of your new omni rom.
Tweaking:
6. Use "interactive"; "sio", "set on boot"
7. Set cpu to max to 1200 Mhz and min to 456 Mhz
8. Reboot
9. Install Nova or ADW launcher. Have at least 3 screen windows . Set look and field to “faster than light” (Nova)
10. Install "prop builder" editor
11. Edit the prop file as follows (see attached image):
dalvik.vm.heapmaxfree
12m
dalvik.vm.heapstartsize
12m
12. Reboot.
13. Run a benchmark app and compare. I got an Antutu score of 9036 (see attached image) up from 7700. Overall system is more responsive.
14. If all goes well, make another backup with a different name.
Good Luck and enjoy.
deryckmeister said:
I would like to suggest the following tweaks that will make your experience with this rom smoother. Make sure you have a complete backup of your a500 current system. Use these at your own risk.
Before installing rom:
1. Wipe cache, wipe Dalvik cache, "real format" data (very important).
Installation:
2. Install rom, install mini-gapps, install super user
3. Boot up rom. Set up Wifi, Set up Google play services.
4. Reboot.
5. Make a complete back of your new omni rom.
Tweaking:
6. Use "interactive"; "sio", "set on boot"
7. Set cpu to max to 1200 Mhz and min to 456 Mhz
8. Reboot
9. Install Nova or ADW launcher. Have at least 3 screen windows . Set look and field to “faster than light” (Nova)
10. Install "prop builder" editor
11. Edit the prop file as follows:
dalvik.vm.heapsize
12m
dalvik.vm.heapsize
12m
12. Reboot.
13. Run a benchmark app and compare. I got an Antutu score of 9036 up from 7700. Overall system is more responsive.
14. If all goes well, make another backup with a different name.
Good Luck and enjoy.
Click to expand...
Click to collapse
I think you have a typo. dalvik.vm.heapsize cannot be set to 12m or it won't boot. Maybe you mean from 384mb to 128mb ?
darkguy2008 said:
I think you have a typo. dalvik.vm.heapsize cannot be set to 12m or it won't boot. Maybe you mean from 384mb to 128mb ?
Click to expand...
Click to collapse
Thanks for the feedback. I made the corrections and edited my previous post to reflect what the attached image of the buildprop file shows.
dalvik.vm.heapmaxfree
12m
dalvik.vm.heapstartsize
12m
Regards,
D.
Problem waking up
Hi,
I installed this ROM, and everything seems to be working well, expect waking the device from sleep.
It sometimes happens, after the tablet is not used for a while and is sleeping, that the power led is on (white), but the screen is black. If you try to wake the device by pushing the power button, nothing seems to happen. The only option is to power it down by holding the power button, and powering up again. Very annoying!
The device is not docked and not connected to mains power.
I disabled daydreaming, and it seems to happen less frequently, but not 100% sure.
I suspect it has something to do with the tab waking up by itself to do some syncing, and somehow getting stuck.
Any ideas?
How can I try to debug this?
Any help appreciated!
You have the infamous Sleep of Death (SOD). It is/was a common problem with certain a500 motherboards. I don't have the SOD issues.
You should contact the XDA iconia HD development team at:
http://forum.xda-developers.com/showthread.php?t=2705989
I am still a junior member and I don't have privilege to post on their blog, yet.
You may try these (make a back up of you current omni rom first):
1. Ensure that the wifi is kept on during sleep. Go to Advanced settings in the wifi options. Click on check box to set scanning always available.
2. Edit the buildprop file to set the wifi_supplicant_scan_interval to 0 sec.
Cons... decrease in battery life. May not be a significant amount.
If the above settings don't work for you, check the links below.
http://forum.xda-developers.com/showthread.php?t=1704870
http://www.kylejorgensen.com/2012/08/acer-iconia-a500-sleep-of-death-and-how.html
All the best.
the_unlord said:
Hi,
I installed this ROM, and everything seems to be working well, expect waking the device from sleep.
It sometimes happens, after the tablet is not used for a while and is sleeping, that the power led is on (white), but the screen is black. If you try to wake the device by pushing the power button, nothing seems to happen. The only option is to power it down by holding the power button, and powering up again. Very annoying!
The device is not docked and not connected to mains power.
I disabled daydreaming, and it seems to happen less frequently, but not 100% sure.
I suspect it has something to do with the tab waking up by itself to do some syncing, and somehow getting stuck.
Any ideas?
How can I try to debug this?
Any help appreciated!
Click to expand...
Click to collapse
Thanks for the advice.
I'm also still junior, so I can't post there either
I never had any SOD issues before, not with the stock ICS and the 3 other ROMs I tried before.
Putting scanning always available didn't solve it, but haven't tried the buildprop yet.
Problem is that is is very intermittent: sometimes the tab runs for about 3 days without hanging, then it happens within the hour...
the_unlord said:
Thanks for the advice.
I'm also still junior, so I can't post there either
I never had any SOD issues before, not with the stock ICS and the 3 other ROMs I tried before.
Putting scanning always available didn't solve it, but haven't tried the buildprop yet.
Problem is that is is very intermittent: sometimes the tab runs for about 3 days without hanging, then it happens within the hour...
Click to expand...
Click to collapse
The Iconia Team HD just posted an update for their ROM. You may try that one and see how it goes. Another developer also posted another a500 omni ROM version 4.4.4. light. Try both and see which one works best for you.
D.
deryckmeister said:
The Iconia Team HD just posted an update for their ROM. You may try that one and see how it goes. Another developer also posted another a500 omni ROM version 4.4.4. light. Try both and see which one works best for you.
D.
Click to expand...
Click to collapse
Updating to 4.4.4 seems to have helped: haven't had the SoD issue since!
the_unlord said:
Updating to 4.4.4 seems to have helped: haven't had the SoD issue since!
Click to expand...
Click to collapse
Awesome. I noticed also that sometimes the screen does not come on with one single press of the power button (most of the times it does) when the Acer a500 is asleep. Sometimes, you just have to watch the power button and press until the white light comes on and the screen comes alive (there is no reboot, it just takes you back to the lock screen). I use to think that it was an sod but all is well.
D.
deryckmeister said:
Awesome. I noticed also that sometimes the screen does not come on with one single press of the power button (most of the times it does) when the Acer a500 is asleep. Sometimes, you just have to watch the power button and press until the white light comes on and the screen comes alive (there is no reboot, it just takes you back to the lock screen). I use to think that it was an sod but all is well.
D.
Click to expand...
Click to collapse
I'm seeing the same thing: the tab won't come alive and I think "****, an SoD again", so I press long to force a power off, and after a few seconds, the screen comes alive! Weird...
For the rest: awesome ROM, much better than the previous one I tried (don't remember exactly which one it was)!
deryckmeister said:
I would like to suggest the following tweaks that will make your experience with this rom smoother. Make sure you have a complete backup of your a500 current system. Use these at your own risk.
Before installing rom:
1. Wipe cache, wipe Dalvik cache, "real format" data (very important).
Installation:
2. Install rom, install mini-gapps, install super user
3. Boot up rom. Set up Wifi, Set up Google play services.
4. Reboot.
5. Make a complete back of your new omni rom.
Tweaking:
6. Use "interactive"; "sio", "set on boot"
7. Set cpu to max to 1200 Mhz and min to 456 Mhz
8. Reboot
9. Install Nova or ADW launcher. Have at least 3 screen windows . Set look and field to “faster than light” (Nova)
10. Install "prop builder" editor
11. Edit the prop file as follows (see attached image):
dalvik.vm.heapmaxfree
12m
dalvik.vm.heapstartsize
12m
12. Reboot.
13. Run a benchmark app and compare. I got an Antutu score of 9036 (see attached image) up from 7700. Overall system is more responsive.
14. If all goes well, make another backup with a different name.
Good Luck and enjoy.
Click to expand...
Click to collapse
Just had my recovered A500 setup as you mentioned... Yes, it's running OK.
However, AnTuTu (v 5.7.1) just keep failing...after it ran up to around 75-76 %. What ver. of AnTutu are your running (since I notice your screen looks slightly different from mine)?
I found this ROM to be the most stable ROMS available for the A500.
For the sake of completeness (most of you will have noticed this app already): For a change, Samsung have done a fantastic job and released a great app called "Game Tuner". It's simple to use, doesn't even need root, and renders all of the stuff I wrote below obsolete!
What it does is, it renders each game at an individual screen resolution, frame rate, and texture quality (texture quality only working for me since MM upgrade).
All you have to do is install Game Tuner from Google Play (above link), start it, follow the instructions to install GameMode through Galaxy Apps, and you're good to go. Create a custom profile, set default values (e.g. 75% resolution=1080p), activate the profile. Set different resolutions for other games. And if you want to control apps other than games, tap top left menu, and chose "Apps".
I've done the same benchmarks as with the method below, and the results were exactly the same, so it's really working, but without messing up the UI or impairing system apps like the camera.
Hey folks,
I've decided to put together a little wrap-up of the stuff I found regarding the sometimes rather poor 3D performance of the Note 4. This is only for experienced users who are familiar with things as rooting, backups, adb, in general: unbricking their phone if bad things happen. As usual, I don't take any responsibilty if you brick your phone or destroy it in any other way. Just make sure to activate USB debugging, and if anything goes wrong, either follow this guide, or simply reflash your ROM.
Just make sure you make a Nandroid or at least Titanium backup before you try this. Better safe than sorry...
It comes as no surprise that running a cpu at almost 3GHz takes its toll. Demanding games such as Real Racing 3 or XCOM:EW, or emulators such as PPSSPP cause the cpu to heat up rapidly, until it reaches ~80°C, before it gets mercilessly downclocked to cool down. At this point, you start noticing more or less pronounced performance drops. There isn't really much you can do, except using a custom kernel to downclock cpu & gpu, before your phone does.
But apart from that, there is another, even greater performance hog, which is also one of the main reasons for the overheating issue: the QHD resolution of our Note 4's screen. We're talking about a 3.69 megapixel resolution, that's almost twice as much as Full HD (2.07 MP), and exactly four times as much as HD (0.92 MP). Gorgeous and brilliant, beautiful to look at during everyday use, but pushing the Adreno gpu to its limits when it comes to gaming.
So, an ingenious guy called NOMone has created a nifty little tool called "NOMone Resolution Changer", already some time ago. It's available for free at Google Play. It's been widely discussed here on xda and on other forums, but I want to share my experience specifically on the Note 4.
Btw, it seems he only posted here two times, so he's most likely not active anymore, but you should head over and thank him anyway.
Now, if you're thinking "no way, why should I deliberately sacrifice my QHD resolution?", read on nonetheless. Because this tool is extremely easy to use, and if you only switch the resolution before playing a game, and revert afterwards (it's only one click), you won't have to sacrifice any visual quality. The settings stick after a reboot, so make sure to really restore defaults if you want to go back to QHD.
The trick is to use the appropriate resolution and dpi values, so your screen doesn't get mixed up.
The results are impressive, sometimes even staggering. Has anyone ever wondered why PPSSPP doesn't perform better on a Note 4 than it does on a Note 2? Here's the reason. PPSSPP gains so much performance , it's almost unbelievable.
I've also done some benchmark runs to measure the improvements (yeah, I know, benchmarks are bad, but still :angel: ). The improvement is clearly visible and, even more important, reproducable:
GFXBench GL Benchmark 3.1 (Manhattan):
1. 1440p: 449,4 frames, 7.2 fps
2. 1080p: 800,6 frames, 13 fps (+78%)
3. 720p: 1621 frames, 26 fps (+261%)
4. 480p: 2728 frames, 44 fps (+507%)
This is plain awesome. The Note 4 is listed even lower, with 434 frames, in the device list, while the 1080p Galaxy S5 reaches 775 frames.
AnTuTu (gpu score only):
1. 1440p: 16210
2. 1080p: 21253 (+31%)
3. 720p: 22524 (+40%)
4. 480p: 22523 (+40%)
Obviously, by comparing scores 3 and 4, the Note 4 hits the fps limit at HD resolution, so there's no more room for improvement in AnTuTu.
Seascape Benchmark (detail setting: Very High):
1440p: 26.9 fps
1080p: 46.6 fps (+73%)
720p: 53.4 fps (+99%, sometimes hits the frame limit of 59.0 fps)
480p: 59.0 fps (+119%, hits the frame limit constantly).
This is a beautiful OpenGL ES 2.0 test, so no cpu scores interfering with the result. Again the fps limit prevents a higher score, but nonetheless, this is pretty amazing.
Other benefits: if you're using a custom kernel, you can run gpu-intensive games at lower cpu speeds to keep the cpu temperature in check. In my case, XCOM:EW runs smoothly @ 30% (!!) cpu speed. This way, the cpu doesn't heat up to more than 60°C, which means it doesn't get downclocked while playing. If you like, you can also automate the process of setting the cpu speed with the aptly named app "Automate" . Which is fantastic, btw.
Now what about visual quality?
Seriously: it's hard to tell the difference. If you look very closely, you can see the display isn't as sharp in FHD as in QHD. But if you look that closely, you're in constant danger of triggering some random app with the tip of your nose. At normal viewing distance, especially while gaming, it's impossible to tell the difference.
So, are there any drawbacks?
Yes, there are: the UI gets messed up a bit (e.g. bigger status bar, some Samsung apps don't fit on screen anymore), and NOMone Resolution Changer doesn't seem to work with CM12.1. Well, at least for me, and other users reported so as well. I tested it some time ago, while I was on CM12.1, and even thought it was a fake app, which it isn't! Seems that the resolution is somehow hard coded into CM12, and you can only switch dpi. There's probably nothing you can do when you're running CM, except try your luck.
But if you are running a Touchwiz ROM, stock or custom, it should work as intended (Emotion Revolution ROM r10.1 in my case). And you can simply ignore the UI issues, as long as you only switch the resolution for gaming. It's not a real issue then, because the status bar is hidden anyway while the game is running.
If you want to keep your device running at FullHD permanently, it's a bit more complicated: first, you'll need Xposed, so you can use the App Settings module to set Android System and SystemUI to 480 dpi. This'll fix the UI (Not needed. Just reboot)
Some apps like phone, contacts, S-Note scale down to the lower dpi setting, whereas Samsung keyboard and the camera won't (camera works, see post #10 below).
So you'll have to install another keyboard like SwiftKey (if you don't have it already), find a working camera app (3rd party or hacked Note 4 camera), and clear your Google Play data (at least I had to, it wouldn't install any apps after the changes), and you're good to go. There might also be other issues I'm not aware of yet. But apart from the ones I described, everything's working fine so far.
Have fun!
you don't need root to change the dpi and the resolution.
enable usb debugging and adb the following:
adb shell wm density 480
adb shell wm size 1080x1920
adb reboot
if you want to revert back:
adb shell wm size reset
adb shell wm density reset
adb reboot
the changes persist after reboot.
I am using it like that for some time. Everything is much faster. Even the browsing..
the only 2 bugs I noticed is the Samsung keyboard (i switched to swiftkey) and the action memo (c'mon Samsung devs, code properly..)
mitko76 said:
you don't need root to change the dpi and the resolution.
enable usb debugging and adb the following:
adb shell wm density 480
adb shell wm size 1080x1920
adb reboot
if you want to revert back:
adb shell wm size reset
adb shell wm density reset
adb reboot
the changes persist after reboot.
I am using it like that for some time. Everything is much faster. Even the browsing..
the only 2 bugs I noticed is the Samsung keyboard (i switched to swiftkey) and the action memo (c'mon Samsung devs, code properly..)
Click to expand...
Click to collapse
You're right, you don't necessarily need this tool. All it does is simplify the process. And you should really be able to use adb commands to fix your phone when you mess it up. But NOMone's tool comes in very handy when you're away from your pc and need to switch resolutions quickly. In my case, it's when I want to use the camera: the UI is messed up at 1080p and I haven't found a way to fix it yet, except switch back to QHD. Or the other way round: if you want to play a demanding game on the train at lower resolution, but go back to QHD again.
I'm using 1080p resolution permanently now, because I get a smoother UI, a cooler phone, better battery life, and much better performance. I hope they don't give us 5" UHD screens next...
Could you please explain what is wrong with the camera on 1080p 480dpi? I am using these settings and have 0 problems with the camera. Just curious.. If possible please attach a screen shot. Cheers
The UI is messed. I can't see most of the buttons, and can't take a photo, see attached screenshot.
Xelasarg said:
The UI is messed. I can't see most of the buttons, and can't take a photo, see attached screenshot.
Click to expand...
Click to collapse
Using my method and my values, it is absolutely fine for me. Do you restart after changing the resolution and the dpi?
I am on UK BTU 5.1.1
mitko76 said:
Using my method and my values, it is absolutely fine for me. Do you restart after changing the resolution and the dpi?
I am on UK BTU 5.1.1
Click to expand...
Click to collapse
I even wiped /cache and /dalvik. Strange. My device is a Snapdragon N910F. Is yours an Exynos N910C perhaps? If not, would you mind sending me your camera apk for testing?
Thanks!
Xelasarg said:
I even wiped /cache and /dalvik. Strange. My device is a Snapdragon N910F. Is yours an Exynos N910C perhaps? If not, would you mind sending me your camera apk for testing?
Thanks!
Click to expand...
Click to collapse
very strange indeed. My device is n910f as well. Not rooted and fully stock. I used the Debloater app to disable all unused apps (works via adb) and the method descried in my other post to change the resolution and dpi. The camera is working absolutely fine i.e. no visual changes or glitches. As I am not rooted I am not sure if I can give you the camera apk. It is basically the same apk as in the stock 5.1.1 BTU rom. Try my method on the stock rom with my values and I am sure it will work.
Cool
mitko76 said:
very strange indeed. My device is n910f as well. Not rooted and fully stock. I used the Debloater app to disable all unused apps (works via adb) and the method descried in my other post to change the resolution and dpi. The camera is working absolutely fine i.e. no visual changes or glitches. As I am not rooted I am not sure if I can give you the camera apk. It is basically the same apk as in the stock 5.1.1 BTU rom. Try my method on the stock rom with my values and I am sure it will work.
Click to expand...
Click to collapse
Well, I went ahead and downloaded _alexndr's COI3 stock debloated rom base (Deodexed), extracted SamsungCamera3.apk, replaced the one in my /system/app dir, set permissions, rebooted, and everything's working fine now. :good:
No idea what the Emotroid guys did to the camera app.
I've attached the apk to this post in case anyone else is having this issue.
Man, I've been playing XCOM:EW at 720p, and my phone didn't get warmer than 59°C, even after 2+ hours. And the performance boost is just so incredible... Turns out I don't even mind the 720p resolution in 3D games, it didn't bother me at all.
Just a warning:
I just managed to render my phone useless with this. After changing resolution and DPI, the phone did a soft reboot (as it should), startet booting, then, after the initialisation of systemUI reboots. Has been Bootlooping the past hour. ADB doesn't work, as reboot it's unauthorised and boot loop doesn't allow for any authorisation. Tried resetting via build.prop and userinit.sh. Even Direct Script Injection into init.rc didn't work.
Cache wipe -> no chance
System wipe and reflash -> Nope
In the End i ended up factory resetting and reflashing complete rom. This did work. Not to rant or anything, just a little story for those that are not capable to troubleshoot problems: This might screw your Installation!
domsch1988 said:
Just a warning:
I just managed to render my phone useless with this. After changing resolution and DPI, the phone did a soft reboot (as it should), startet booting, then, after the initialisation of systemUI reboots. Has been Bootlooping the past hour. ADB doesn't work, as reboot it's unauthorised and boot loop doesn't allow for any authorisation. Tried resetting via build.prop and userinit.sh. Even Direct Script Injection into init.rc didn't work.
Cache wipe -> no chance
System wipe and reflash -> Nope
In the End i ended up factory resetting and reflashing complete rom. This did work. Not to rant or anything, just a little story for those that are not capable to troubleshoot problems: This might screw your Installation!
Click to expand...
Click to collapse
Hence the warning at the beginning of the thread.
But seriously: which method did you use? The NOMone app or the adb commands? Because only the adb command needs a reboot to take effect, NOMone does not reboot: it changes the resolution on the fly, then waits 10 seconds for confirmation and switches back to default resolution otherwise.
It's impossible to tell what went wrong in your case, might have been anything from a bad adb command to a malfunction of the app or your rom. I guess if you enter bad values, both methods might break your SystemUI. I managed to do so by using Automate to activate the shell commands on app launch (no bootloop, though, only permanent FC of SystemUI), but I was able to fix it with adb easily.
It's a shame it didn't work for you, most people who are using this method are very happy with it.
THANKS !
dooes this improve battery as well /
gonna try this
Boody hegan said:
THANKS !
dooes this improve battery as well
Click to expand...
Click to collapse
Yes, it does, at least a bit. The screen does still burn a lot of juice because it's so big and bright, but the cpu stays much cooler. Less heat=less power consumption.
Thanks alot , i'm on simplrom v5c and googy max kernel v2
can this still work ..
Xelasarg said:
Hence the warning at the beginning of the thread.
But seriously: which method did you use? The NOMone app or the adb commands? Because only the adb command needs a reboot to take effect, NOMone does not reboot: it changes the resolution on the fly, then waits 10 seconds for confirmation and switches back to default resolution otherwise.
It's impossible to tell what went wrong in your case, might have been anything from a bad adb command to a malfunction of the app or your rom. I guess if you enter bad values, both methods might break your SystemUI. I managed to do so by using Automate to activate the shell commands on app launch (no bootloop, though, only permanent FC of SystemUI), but I was able to fix it with adb easily.
It's a shame it didn't work for you, most people who are using this method are very happy with it.
Click to expand...
Click to collapse
It was completely my fault. I knew what i was getting into, so no problem. It's just that, the "mistakes" i did could easily be done by accident by some less experienced users.
First off, i'm on CM12. NOMones Sollution doesn't seem to work there. CM does a "Hot Reboot" to reload the system UI. No matter what you set in NOMones app, the resolution doesn't change. DPI does though. This seems to be a CM related issue. Maybe they hardcode the resolution at build time...
After that i tried another app, which had the Orientation labeled backwards. So it set 1920x1080 landscape instead of portrait. After that the Phone Bootlooped the System UI. It would always boot up to the PIN Enter Screen and then reboot.
As said, no big Problem. I knew what to do and was able to bring my phone back to working state. Just make sure that you are 100% sure about the numbers you put into such apps and keep in mind that even with such "small" changes you should always have a up to date Backup of everything.
Boody hegan said:
Thanks alot , i'm on simplrom v5c and googy max kernel v2
can this still work ..
Click to expand...
Click to collapse
It should, unless SimplROM is CM12-based. NOMone Resolution Changer, as well as similar apps and the adb method, aren't limited to specific devices. In theory, they may all work on all Android phones. You'll have to try it out yourself, just make a backup before you do so!
domsch1988 said:
It was completely my fault. I knew what i was getting into, so no problem. It's just that, the "mistakes" i did could easily be done by accident by some less experienced users.
First off, i'm on CM12. NOMones Sollution doesn't seem to work there. CM does a "Hot Reboot" to reload the system UI. No matter what you set in NOMones app, the resolution doesn't change. DPI does though. This seems to be a CM related issue. Maybe they hardcode the resolution at build time...
After that i tried another app, which had the Orientation labeled backwards. So it set 1920x1080 landscape instead of portrait. After that the Phone Bootlooped the System UI. It would always boot up to the PIN Enter Screen and then reboot.
As said, no big Problem. I knew what to do and was able to bring my phone back to working state. Just make sure that you are 100% sure about the numbers you put into such apps and keep in mind that even with such "small" changes you should always have a up to date Backup of everything.
Click to expand...
Click to collapse
Right, thanks for clarification. I don't remember the hot reboot in CM12, but I know the resolution switch didn't work when I tried it on my Note 2 some time ago. Funny that for once Touchwiz is more customizable than CM.
If you're still interested, but hate the Samsung colour scheme (like me), you can try out Emotion Revolution ROM r10.1. It's based on the latest COI3 TW firmware, but they themed the notifcation/status bar and toggles to somewhat more like stock Android, see attached screenshot. Looks pretty sleek, performance is easily on par with CM12, and the Emotion kernel has tons of great tweaking options. Or you can go for their Port Note 5 r2.1 ROM, also based on COI3, which should offer full Theme Store support. That's the one I'll flash next. :good:
Xelasarg said:
Right, thanks for clarification. I don't remember the hot reboot in CM12, but I know the resolution switch didn't work when I tried it on my Note 2 some time ago. Funny that for once Touchwiz is more customizable than CM.
If you're still interested, but hate the Samsung colour scheme (like me), you can try out Emotion Revolution ROM r10.1. It's based on the latest COI3 TW firmware, but they themed the notifcation/status bar and toggles to somewhat more like stock Android, see attached screenshot. Looks pretty sleek, performance is easily on par with CM12, and the Emotion kernel has tons of great tweaking options. Or you can go for their Port Note 5 r2.1 ROM, also based on COI3, which should offer full Theme Store support. That's the one I'll flash next. :good:
Click to expand...
Click to collapse
Nah, TW is no option... I choose CM because of the straight forward no bllsht Apps approach. Plus Nightly builds via OTA... In no possible way am i going back to TW
AnTuTu Benchmark @ 1080p, performance governor, stock cpu frequency (2.65 GHz): :highfive:
(OK, cpu was also very cool when benchmark started, 28°C).