yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Kney.:
Noob question: Is Paranoid Android CAF/CM based or Aosp based? ?

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] RealSlimShadyMC:
AOSP
[Nexus 7 (2013) Original Android Development] Kney.:
Thanks a lot! ?

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] MadMatt89:


I had a serious conversation about this issue so please stop hating around. I just stated that I don't have the problem which I had with ElementalX, no offence to anyone. Maybe it helps someone.
[Nexus 7 (2013) Original Android Development] NYCHitman1:
Stating you have an issue without providing the proper support on your end is not helpful at all.
[Nexus 7 (2013) Original Android Development] yousif666:
I installed PAC-MAN 4.4 on my nexus 7 DEB version but after booting i just see the loading screen and nothing happens, i installed the CM11 version of the kernel.
[Nexus 7 (2013) Original Android Development] teddy0209:
It should work... Have you happen to install bionic and dalvik tweak?

If you did, then start again and don't install that...
[Nexus 7 (2013) Original Android Development] yousif666:
Now i didn't install the dalvik tweak and it worked but what is the bionic?
[Nexus 7 (2013) Original Android Development] teddy0209:
It goes with it... =) just one button to tick... Don't really remember the entire option, but that's it, you've managed to make it work...
[Nexus 7 (2013) Original Android Development] hello247:
I had an issue with the screen recognising multiple touches on the screen when I was only placing my finger on one point on the screen. Could this due to uv of the gpu. This issue happens once in a while.

I don't remember having this issue before.

I'm using 450mhz with - 100mv undervolt
[Nexus 7 (2013) Original Android Development] coolek33:
Been there. It happens to me also but I don't think it's kernel related. Had on stock too.
[Nexus 7 (2013) Original Android Development] hello247:
Hardware fault? I hope not
[Nexus 7 (2013) Original Android Development] matcho13579:
Are you holding your device when it's happening? It could be an issue with majority of Nexuses, try to google it
[Nexus 7 (2013) Original Android Development] SickBeast:
I have found the sweep to sleep very glitchy heh lol. The screen was randomly turning off when I had it enabled.
[Nexus 7 (2013) Original Android Development] hello247:
doesnt really matter if i hold it or use it on my desk. Never mind, i found quite a lot of people have multi touch issues. my other Nexus 7 (2013) doesnt have this problem at all. guess every device is different. cheers anyway :good:
[Nexus 7 (2013) Original Android Development] wapvirus:
Working perfectly on my N7 flo with IOAP so fast I was using KControl to change settings but this was not always working correctly so now I just setup in aroma and leave it alone, by far the best kernel I have tested with this ROM super combination
[Nexus 7 (2013) Original Android Development] Banished Angel:
I'm considering switching over to this kernel and a custom ROM from stock. What settings is everyone running? Overclocks? Undervolts? Governors? Just looking for some input.
[Nexus 7 (2013) Original Android Development] SickBeast:
I use extreme l2 cache, 600mhz gpu, and I leave the CPU at 1.9ghz but once I install the kernel I leave the CPU at 1.5ghz and I undervolt it. Mine eats up a ton of juice beyond 1.5ghz.
[Nexus 7 (2013) Original Android Development] hoangtungst:
I have stuck boot when flash CAF version for PAC rom
[Nexus 7 (2013) Original Android Development] marsaltito:
Is Pac CM11 based ? If not then try AOSP kernel .
[Nexus 7 (2013) Original Android Development] teddy0209:
reinstall and uncheck dalvik patch...
[Nexus 7 (2013) Original Android Development] ngyurov:
I'm using latest PAC nightly with the CAF version of this kernel. I don't use any uv, my CPU is at 1.7, intelidemand governor, and GPU is at 450. L2 is at the improved setting. I've also set multicore power saving to 2.

With this setup my tablet runs very smoothly,and battery life is great, however PAC drains more battery compared to slim for example.

I'm not using any of the s2w and d2w functions as I don't find them useful,given the fact that my case is magnetic, and they get in my way.

When flashing make sure you flash the right version of the kernel, CAF is for CM based ROMs. Also do not enable the dalvik optimizations as they tend to make most ROMs boot loop .

I'm also using this - http://xdaforums.com/showthread.php?t=2670902 .
[Nexus 7 (2013) Original Android Development] SickBeast:
I don't know if this is a glitch or not, but even when I disable input boost my minimum cpu frequency is listed at 900mhz in trickster and when I look in the info tab the CPU never goes below 900mhz. Perhaps this explains some of the battery life issues. I have overridden it back to 384mhz and I will report back later with my findings.
[Nexus 7 (2013) Original Android Development] ngyurov:
I'd say remove trickster, reinstall glitch, making sure that minimum frequency is set to 384,and then use something other than trickster to change kernel settings, like ROM toolbox for example.

Try using CPU spy to see if it goes to lower frequencies during idle, you might be dealing with some CPU hogging app.
[Nexus 7 (2013) Original Android Development] SickBeast:
I would do that but I have heavily customized trickster. I think you are right though and it held the settings from a previous installation.

---------- Post added at 09:53 PM ---------- Previous post was at 09:22 PM ----------

Ok i can confirm that trickster caused the issue, not the kernel. There is no glitch lol.
[Nexus 7 (2013) Original Android Development] ngyurov:
I've had similar problems with trickster, that's why I suggested that you remove it. It randomly changed CPU governor for me.
[Nexus 7 (2013) Original Android Development] habylab:
I had that too
[Nexus 7 (2013) Original Android Development] vince2008:
Great score....got this score with stock rom running and glitch kernel.
[Nexus 7 (2013) Original Android Development] mus1mus:
Just wanna share this,

L2 OC to FAST made my RAM SPEED score up to 2K!!!

I can score 30K with 1836!!!
[Nexus 7 (2013) Original Android Development] vince2008:
Thats awesome mus1mus......I normally run L2 OC extreme @ CPU 1836 as daily driver and score 30k+ antutu.
[Nexus 7 (2013) Original Android Development] Blizzard300:
How you're able to score more than 3k points in 2d graphics? The highest score i've ever had was 1,7k with similar settings... Through fps unlock?
[Nexus 7 (2013) Original Android Development] sam298:
Installed cm11 latest glitch kernel on my aosb rom. Wont go past aosb bootscreen. Reinstalled glitch without qualcomm dalvic checked, tried wiping cache and dalvik cache. Stuck at bootscreen. Anyway to get past boot screen? Tried reinstall again with all stock settings and no dalvic improvements. still stuck.. please help.
[Nexus 7 (2013) Original Android Development] kingston73:
I would maybe flash aosb over and make sure everything is working and also redownload glitch kernel. I have the same combo and it's working great for me.
[Nexus 7 (2013) Original Android Development] CreepyE:
Problem is that you wiped cache and dalvik

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] teddy0209:
Disregard this
[Nexus 7 (2013) Original Android Development] sorevilo:
Will this work on factory stock ROM? Rooted
[Nexus 7 (2013) Original Android Development] sorevilo:
Sweet
[Nexus 7 (2013) Original Android Development] hakcenter:
Anyone noticing a significant drain of over 1% per hour while the device is asleep ?

I don't think it's making it into deep sleep but I have no wake locks /shrug
[Nexus 7 (2013) Original Android Development] xanthrax:
Do you use multiboot? If yes, have you updated the app to the latest?

Sent from my Darkside of Nexus 4
[Nexus 7 (2013) Original Android Development] creeve4:
Sweep2wake/Sweep2sleep/Doubletap2wake will increase standby battery drain.
[Nexus 7 (2013) Original Android Development] Ramrod421:
Tried to install this kernel because it sounds like it's a good one but it doesn't work. I flash the kernel, reboot, it shows apps updating and then just sits at the ROM logo forever. I'm on Slimkat. I know it works with Slim because others have it but for some reason it doesn't work with mine.
[Nexus 7 (2013) Original Android Development] akaHardison:
Just a small request:can you add a rtl8187l wlan driver in your kernel.
[Nexus 7 (2013) Original Android Development] teddy0209:
You sure you installed the right version? Or did you check the option for dalvik patch in aroma...?
[Nexus 7 (2013) Original Android Development] Ramrod421:
I think so. I used the AOSP version since Slim is based of AOSP. I did not check the dalvik option.
[Nexus 7 (2013) Original Android Development] PlayingPoise:
Did you install the CAF version or the AOSP version? Try both and see which works. Also, the Dalvik libraries might give your device the bootloop, so try to not install that.

On an unrelated note, do you think you could add Intelliactive as a governor upon the new release? I've been using it on my Galaxy S3 and I absolutely love it, I'd love to see it be released in this kernel :D
[Nexus 7 (2013) Original Android Development] kingston73:
I thought Slim used CM as a base, no?
[Nexus 7 (2013) Original Android Development] coolek33:
It's aosp.
[Nexus 7 (2013) Original Android Development] teddy0209:
all this time, i thought slim is based on cm... just try both as mentioned above...
[Nexus 7 (2013) Original Android Development] Nekromantik:
Is it normal for USB otg power to not always work properly? I have to reboot to get it charging and sometimes it's not using AC charging. You have to unplug and replug power cable to get it to say AC charge.
[Nexus 7 (2013) Original Android Development] Clark Joseph Kent:
Sir, you wont hurt my feelings, but tell you what, lets not try....But please be nicer to those trying to help you, you are the one asking for help....
[Nexus 7 (2013) Original Android Development] SickBeast:
Test

---------- Post added at 01:00 AM ---------- Previous post was at 01:00 AM ----------

Mods are you deleting my posts?
[Nexus 7 (2013) Original Android Development] hakcenter:
Realistically I was just asking for a yes or no or for tk to say something. Seems like this little bunch needs some leather skin.

Does anyone's device also sleep of death on 142. I use the same exact settings between 140.1and 142 sod's quite randomly. I Havant seen tk post in awhile I wonder where he went.
[Nexus 7 (2013) Original Android Development] 3dawg:
At least once a day.
[Nexus 7 (2013) Original Android Development] kingston73:
The only instability I've seen is an occasional reboot and that is always when I'm using Chrome. Everything else has been great. I'm on aosb using the cm version of glitch. I think for anybody to help you'll need to give more info.
[Nexus 7 (2013) Original Android Development] SickBeast:
Ok since other people are being so forgiving, I'm going to help hakcenter get better battery life. Here is what you need to do:

1. Leave the CPU at 1.5ghz and undervolt it on all steps if you can by at least 50mv. On my tablet, I hit a voltage wall beyond 1.5ghz and there are very little gains in clocking higher anyways.

2. Overclock the cache to extreme if you can.

3. Overclock the gpu to 600mhz but do not lower the voltage.

4. Enable intelli-plug and disable mpdecision.

5. Max out the multi core power savings.

6. Download install and run greenify. Hibernate any apps that are waking up your device.

7. Use the interactive cpu governor.

8. Do not use input boost.

9. Enable the art runtime.

10. Profit.

I get about 10h of sot with these settings and it is considerably faster than stock.

Have a nice day. :)

I call these settings "beast mode".
[Nexus 7 (2013) Original Android Development] animania260:
I initially has this problem as well when I upgraded to 142- but there is really no changes that would cause this. So I reset all my Trickster settings to stock- U/V, GPU, CPU, etc > reflashed stock kernel > then reflashed 142 > cleared dalvik and fix permissions in TWRP.

After that I had no more "sleep-of-death" problems.

Not sure what was going on there.

I'm going to post an updated AOSP Glitch kernel with the new Linux 3.4.83 fixes in a few hours. There's quite a few fixes for: ext4 filesystem, memory management, etc. I've been running it all day with no issues. Just a little update until Glitch does his official release- if anyone wants to use it.
[Nexus 7 (2013) Original Android Development] Divine_Madcat:
Keeping the discussion on track, i will say the last few days i have had a SOD or two.. isn't a huge deal, but yes, it is happening..
[Nexus 7 (2013) Original Android Development] SickBeast:
It all depends on your settings and how far you push your hardware. Mine has been completely stable for weeks.
[Nexus 7 (2013) Original Android Development] Divine_Madcat:
For what its worth, i was running the same setting with the previous kernel, and was NOT experiencing it (as a matter of course, i even did back down my settings slightly just in case)...
[Nexus 7 (2013) Original Android Development] teddy0209:
Mine also is stable, cpu @ 1700, gpu @ 450, all default...
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
I get the SOD when I set the minimum cpu below 384mhz multiple times a day but at 384 I get none.

Mine runs stable at 1.998ghz and gpu at 545mhz.
[Nexus 7 (2013) Original Android Development] hakcenter:
I don't need help making battery life better I'm asking general questions. It may be news to you but I make the most battery efficient ROM for the e4gt. I appreciate the thoughtfulness. I get over 10hrs of screen over a week seriously though thanks.

I'm not using any strange settings just standard and no s2wake etc. Like I said 140.1 is fine but I get screen off discharge and sod on 142. Tks change log in the post is pretty vague and I don't really feel like browsing github finding the problem and forking his kernel.

Just waiting for a response from him as it looks like others get a sod. Not setting min under 384 either.

It's probably the revision upgrade.
[Nexus 7 (2013) Original Android Development] marsaltito:
CM11 r142 (no undervol. Rest default by aroma) , no SOD .
[Nexus 7 (2013) Original Android Development] NYCHitman1:
That's interesting. No issues on my ROM with Glitch. Running 384-1728 CPU. 504 GPU. -50 uV across the board. Not using any of the S2W settings. SOD's were solved for me after v140.1.
[Nexus 7 (2013) Original Android Development] just lou:
I haven't had a single issue with r142 running with stock rooted ROM, and moderately overclocked.
[Nexus 7 (2013) Original Android Development] creeve4:
Same here, not a single SOD. I've been running r142 since it was released. Stock rooted. Moderate OC. UV -50 across the board.
[Nexus 7 (2013) Original Android Development] tibere86:
My exact settings except for -75uV. Not a single SOD and the best battery life of any kernel I've used.
[Nexus 7 (2013) Original Android Development] ngyurov:
Are you using max screen of frequency? Because I noticed that when I have it enabled, 1620 is unused CPU frequency for some reason. Max screen off for me is 1026,otherwise all other settings are same as yours. Does yours use the 1620 frequency?
[Nexus 7 (2013) Original Android Development] tibere86:
I'll have to check when I get home but I do use the default max screen off frequency of 1026mhz.
[Nexus 7 (2013) Original Android Development] hakcenter:
Does anyone use alternate speeds for their cores? I do 1700 first two then 1500 last
[Nexus 7 (2013) Original Android Development] just lou:
Seems a little silly to me. Just my opinion.
[Nexus 7 (2013) Original Android Development] adomol:
Silly? I have them at 1700, 1500, 1300, and 1100 (cause I don't like even numbers.) Now that's silly!
[Nexus 7 (2013) Original Android Development] mdamaged:
Actually, those are even numbers. You need to set them to 1701, 1501, 1301, and 1101!
[Nexus 7 (2013) Original Android Development] adomol:
Dang... Now I have to rethink my OCD!
[Nexus 7 (2013) Original Android Development] Shillopellos9:
i think intelli_plug got an update 2.2
[Nexus 7 (2013) Original Android Development] ngyurov:
How does setting different frequencies for every core affect performance and battery life? Is it beneficial, and if yes - how? Is it something similar to how the eight core Samsung processor uses lower frequency cores for light tasks and switches to higher frequency ones when the demand increases?
[Nexus 7 (2013) Original Android Development] hakcenter:
Most operations are two cores at best for my use so when it gets intense I don't see a need to have 0.000001msec faster loading. I would almost disable the cores honestly.

Anyways on rare occasions of high load I don't see the benefits for high core speeds ymmv
[Nexus 7 (2013) Original Android Development] ngyurov:
What app do you use to tell how many cores are working? I'm using CPU spy, but it doesn't have any info about the cores?

Also - how do you set CPU cores to frequencies lower than 1512? Because that's the lowest value I see in the aroma installer.
[Nexus 7 (2013) Original Android Development] mdamaged:
I know you weren't asking me, but I use System Monitor by Christian Göllner, the lite version is free, but does not have floating apps, the other version allows you to view core operations (among everything else) while in an app, as it draws on top of whatever app you are running.
[Nexus 7 (2013) Original Android Development] ngyurov:
Nice, that's an awesome app,beats CPU spy. However I still haven't found a way to set core frequencies below 1.5 Ghz. Any ideas?
[Nexus 7 (2013) Original Android Development] mdamaged:
I think you can do that with Snake Charmer (in FauxClock that is what it is called) setting?
[Nexus 7 (2013) Original Android Development] ngyurov:
I can't find such an app on play store. I found some multicore manger app on play store, but it's very buggy, free version very limited and paid one doesn't seem worth it.
[Nexus 7 (2013) Original Android Development] mdamaged:
It's called Faux123 Kernel Enhancement Pro now. You might find the setting in Trickster, not sure. But yeah, you should verify if that setting will even do you any good before spending any money.
[Nexus 7 (2013) Original Android Development] ngyurov:
The kernel enhancement app is paid version only, no trial, and trickster doesn't support the feature. Hope some of the people that use different clock speeds for every core share the knowledge.
[Nexus 7 (2013) Original Android Development] adomol:
You could pop open glitch-settings.conf in your sd root to set your core speeds there... Although, I have to say that if this conversation about setting each individual core to a unique frequency was prompted my post a couple pages back, I have to stress that I was being sarcastic. But maybe it didn't come out that way. I have all cores set to 1728 and it runs like a champ.
[Nexus 7 (2013) Original Android Development] ngyurov:
I did some research, and according to it, and to the system monitoring apps I tried, the first core does almost all of the heavy lifting, while the others basically slack, especially the third and the fourth.

I'm going to try setting the first to higher frequency, while tuning the rest down, to see how it affects battery life.
[Nexus 7 (2013) Original Android Development] adomol:
Also, if you want to get more from your battery, you can find the undervoltage sweetspot.

Here's a guide to dialing it in: http://xdaforums.com/showpost.php?p=21642901&postcount=3885
[Nexus 7 (2013) Original Android Development] ngyurov:
The config file doesn't allow me to lower the frequencies from stuck - 1512. I need to find something that allows me to tune every core separately, like what performance control from AOKP offers, but for every core.
[Nexus 7 (2013) Original Android Development] adomol:
Just out of curiousity, which frequencies are you looking to set your cores to?
[Nexus 7 (2013) Original Android Development] ngyurov:
I'd like to set the first one to 1.8,second to 1520, and third and fourth to 1000.
[Nexus 7 (2013) Original Android Development] adomol:
I think the improvement to battery life by setting those cores to 1000 would be negligible as they are usually off most of the time anyway.
[Nexus 7 (2013) Original Android Development] Purplezigar:
r142 isn't booting on the Snapshot M4 build of CyanogenMod. I didn't do any crazy settings, just the normal stuff I usually do.
[Nexus 7 (2013) Original Android Development] tsimitsangaz:
Guys any good suggestion for better battery life and smoothness to aroma installer? What about Smartmaxx governor?
[Nexus 7 (2013) Original Android Development] adomol:
Are you using the right version of the kernel for your rom? Should be the CAF variant.

---------- Post added at 05:20 PM ---------- Previous post was at 05:14 PM ----------

You can play with your undervolting options. But I would suggest using Trickster MOD so can dial it in before deciding on a setting.
[Nexus 7 (2013) Original Android Development] Purplezigar:
Yup I have the CAF version. I don't know why it's not booting with it. I was booting on the 17/2 version but the M4 it isn't.
[Nexus 7 (2013) Original Android Development] adomol:
What happens when you flash it?
[Nexus 7 (2013) Original Android Development] Cuzz1369:
I dont like aroma. Call me old fashioned or whatever. What kind of problems could I expect if I extract the boot.img and flash it directly.
[Nexus 7 (2013) Original Android Development] hakcenter:
No kernel settings all sorts of problems. What's wrong with an intuitive installation
[Nexus 7 (2013) Original Android Development] animania260:
Alright, ladies and gentlemen.

This is the 2nd revision of Glitch's kernel I've built- since hes been away/busy.

I never posted the 1st one since nobody seemed to care, to each their own.

But this 2nd revision has a lot of good stuff in it, so I figured Id post it for those that want to try it.

*******This is ASOP ONLY!!!!!!!!!******** Might do a CM build next week.

Same (slightly newer) SaborMod 4.8.3 GCC Cross-Compile Tool-chain optimized for Cortex-A15 Arm chips.

Lots of EXT4, SCHED, MM/Subsystem fixes from mainline 3.4.y. Now up to the latest 3.4.85 mainline kernel updates.

More upstream SCHED,MM,Mutex and other performance improvements cherry-picked from Faux123s & Franco kernel.

Also there is a little hack from Franco N7 kernel that allows the Back-light Brightness to go down to its lowest value- its fairly dark, for those that love to save battery or low-light reading.

Commits are here if you want to check them out: https://github.com/animania260/Glitch_Flo_AOSP/commits/google-flo

Overall I've seen a decent speed improvement, and that is with some power-saving settings turned on.

Let me know what you think, if you test it. And yes I have tested it for over 24 hours- no issues so far.

Link: https://docs.google.com/uc?export=download&id=0B22ZNBermHGrVjBoWkE2NGswMU0

There is some new Hotplug stuff for Faux123 intelliplug I want to merge and test out next week.

Credits: TK-Glitch for his awesome base kernel (and who he has credited in OP), Faux123, Fransico Franco, mainline kernel developers.
[Nexus 7 (2013) Original Android Development] tsimitsangaz:
Yeah ...animania260 keep on going !!! nice job installed and runs smooth and fast with stock settings . do you have any specific setup (aroma) that you like and prefer? I will report back tomorrow . Thank you. (also I 've tested new Hotplug stuff for Faux123 intelliplug on my motog and it is working fast combined with intelliactive gov) you should merge it. So all in one kernel !! kudos!