Certainly is hideable!read in features list:
- Nav Bar Hide on Lockscreen
is the navbar hideable for *all* like in other aokp roms?
note has physical buttons. i don't need software buttons
Off topic I really like the fire stigs would you be kind to point me in the direction to get something like thatGuys can someone run some quick benchmarks for me?
I am having really bad performance , specifically the CPU part as the GPU seems fine. For example Linpacks which I was getting over high 110s before (GB rom) I am getting at best 70s.
Quadrant just got me 1900s.
And before someone comes saying benchmarks are BS, I have been doing this for a while now so I know my things.
But the fact is this low performance is reflecting on my actual phone use.
One of my main things to use is emulators and the Mame emulator that I use to run Afterburner 2 super smoothly now runs super choppy.
So basically some benchmarks will give me an idea if something is wrong with my installation.
Thanks!
Sure thing...right here http://cooltext.com/Off topic I really like the fire stigs would you be kind to point me in the direction to get something like that![]()
Thanks I'll take a look
Same issue here. Not EVERY time, but ocasionally i get SOD and have to pull the battery out. Is it kernel related only?This ROM is nice but the kernel is draining the battery too fast, I get SOD every time it sleeps I have to remove the battery. so I flashed Franco R4 and it worked beautifully but I can't access my SD card Samsung 32GB class 10. Flash back CM kernel and I see it.
Anyone know how to manually mount the SD card via terminal or adb? I did edit the file in etc/vold.fstab but still no SD while on Francisco R4.
Sent from my GT-N7000 using Tapatalk 2
Chrome beta only works with 160 or 280 and higher.This rom is really great. So far So good aspecially with 240dpi. But I am facing some problems like Chrome beta FC. I also tried 241dpi, 250dpi and 260dpi. It did not work. Is there any solution for this?
Thanks for your answer, But Could you please advise me Which resolution is more convenient to use for daily.Chrome beta only works with 160 or 280 and higher.
i like 280.Thanks for your answer, But Could you please advise me Which resolution is more convenient to use for daily.
I have yet to see an SoD with this build, (just jinxed myself im sure) but yes - these are generally kernel related. All current CM9 builds seem to have the same issue - Asylum, CM9, this is no different.Same issue here. Not EVERY time, but ocasionally i get SOD and have to pull the battery out. Is it kernel related only?
Does Abyss kernel works with this rom? cheers.
Do you use it on your AOKP? Why don´t you just give us a link?For anybody having problems: google for tegraowners forum and find the thor kernel v08. It supports usb host, and spirit fm and touch recovery ntfs mount support and much more... Just a suggestion...
it works in aosp/aokp/cm9 without any significant issues. i don't want to give the direct link since the dev of the kernel is not a member of xda. i don't want to act as spammish message writerDo you use it on your AOKP? Why don´t you just give us a link?![]()
There's a version 1.8.1 now as well as 0.9.For anybody having problems: google for tegraowners forum and find the thor kernel v09. It supports usb host, and spirit fm and touch recovery ntfs mount support and much more... Just a suggestion...
This is what Entropy has to say about it:There's a version 1.8.1 now as well as 0.9.
I wish he would join XDA. I don't see why he isn't, its one of the biggest android forums out there.
Edit:
My bad, its just the recovery version.
I really wanted it for the OCing part.... :\Thor is a pirate - a GPL-violating kangbanger. He was effectively banned from XDA for multiple GPL violations.
To put things shortly:
For the kernel, the GPL REQUIRES you to provide source to anyone you provide a binary to.
For userspace stuff, the Apache license allows you to withhold source, however those who do so with CM9 code will be effectively shunned from the community for being a douchebag.
My OTG cable arrived last night - I found the fix and it's in the review process now. At the same time, I finally had time to make our storage configuration match that of I777/I9100 - You'll see internal/external SD cards swap when it merges. (Recovery will now correctly be using the internal SD when it says internal...)