yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] bleuxeon:
Minimum CPU voltage

Hi,

After testing Franco's kernel, ElementalX, I will give a try to Glitch and I have 1 question :

-what's the minimum voltage allowed for CPU? (on Franco and EleX it is 700mV)

Thanks
[Nexus 7 (2013) Original Android Development] shaolinz:
Love glitch kernels just wish there was a cm one so I'm stuck on elemental x for now with aosb until one comes out
[Nexus 7 (2013) Original Android Development] soldier1184:
what's up just flashed AOSP DJ Kangs build sun jul 13 2014 edit ( settings about device ) anyways i flashed that with glitch and it works..... but i only flashed it with like 2.1 ghz OC i believe and some other settings any other time i try and install glitch onto say liquidsmooth or etc it boots ( sometimes ) and it flashes a white rectangle over the bootani ( no matter which it is ) is that cpu to high hardware freak out gpu stress or what cause im unfamiliar with this device im not a noob by anymeans ive owned android for sometime and have flashed multiple lg samsung etc and tablets some name brand other's not ive had this tablet now for 5-going on 6 days nothing's been dropped etc my wifi sucks ( maybe someone has a fix for that due to i go into the etc folder etc fiddle with settings ( not familiar with those settings either ) im more pc prone with that realm of tweaking but anyways sorry for getting off subject but yeah the wifi is something i would like to fix due to running of it constantly no my routers good my other phones have ran off it as well as my retired sammy tab 4 7 that i replaced with this tablet i just hope that i didn't by something that is going to give me problems...ok back to current subject when i flash the glitch kernel specifically it well hence the name GLITCHES literally my boot screen sometimes doesn't even go past the google logo or as stated goes past google logo "boots" ( well ok it don't boot cause i reboot into recovery constantly ) and it flashed a large white rectangle or even sometimes multiple colors across the screen im hoping i didn't term this tablet ( i don't believe so due to being able to run other roms etc and flash other kernels get in through adb etc etc but im really wanting to know if i should take this tablet back and replace it with the same and hope for a newer better outcome or what cause ya i burned 230+ on this at walmart 6 days ago and i would like to get my money out of it so hopefully someone can give me some idea of what to correct or what settings to load when flashing kernels and also ( CAN ANY OTHER THE OC freq's etc be changed "added" into the ini scripts and hosting files ) ( ie i flash say 1.7ghz can i go into the ini file and change that to register the higher oc levels ) hopefully all this made sense thanks for any help that is given also i design boot animations i did one for the samsung blaze and many of the dev's picked it up and started using it so if you want a boot ani let me know anyways hopefully someone can help me here i would appreciate it also help with the wifi issue to thanks and sincere regards
[Nexus 7 (2013) Original Android Development] :
Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] tetakpatak:
LOL :D +1

tetakpatalked from P5110
[Nexus 7 (2013) Original Android Development] bleuxeon:
Nobody? :(
[Nexus 7 (2013) Original Android Development] soldier1184:
whiskey tango foxtrot hooah ( ie wtf over )
[Nexus 7 (2013) Original Android Development] matcho13579:
You have to test it by yourself
[Nexus 7 (2013) Original Android Development] bleuxeon:
I am asking for the hardcoded minimum CPU voltage, not for what voltage that would be stable :rolleyes:
[Nexus 7 (2013) Original Android Development] :
Well it took me a while to get through that massive wall of text, but I think I know what you're asking ;)

1) First issue I believe is that you aren't able to boot after flashing glitched with OC settings?

Have you tried flashing glitch with stock settings?

If you ARE able to boot with stock settings, then your n7 isn't able to cope with the OC settings you applied. What I'd do is start from stock and flash again while increasing the clock one step each time.

If you AREN'T able to boot with stock settings, then I have no idea what's going on. Someone else may have an idea.

2) As far as whether you should return the n7 for a new one:

I would say there wouldn't be a valid reason/concern yet to do so.

3) Regarding whether you are able to change settings post installation:

The only settings you can't change are the CPU and l2 / bus settings. Just reflash the kernel if you want to change. Rest of the settings you can change via trickster mod. (Read 1st and 2nd post of the thread)

4) Slow Wi-Fi issues:

I haven't experienced this, but have seen some people that do have issues. Maybe someone else can chime in.

Isn't it around the 600 ~ 650 range?

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] bleuxeon:
Well...

I don't know, that's my problem :D

Maybe it is written in a file but I don't know were to look for.

Dear [MENTION=3847629]Tk-Glitch[/MENTION] , would you mind telling us what's the lowest core voltage allowed by your kernel? :confused:
[Nexus 7 (2013) Original Android Development] poondog:
https://github.com/Tk-Glitch/Glitch_Flo_AOSP/blob/google-flo/arch/arm/mach-msm/vdd_limits_8064.h

700mV according to his source
[Nexus 7 (2013) Original Android Development] bleuxeon:
ohhh nooooooooo :crying:

Same as Franco or ElementalX kernels.

I was hopping that Glitch would allow lower voltage since it allow lower freqs.
[Nexus 7 (2013) Original Android Development] poondog:
Would introduce a lot of instability

You could easily change this one line and compile :)
[Nexus 7 (2013) Original Android Development] bleuxeon:
Maybe, maybe not :D

Here is my UV table.

As you can see, it looks like there is room to undervolt below 700mV.

Regarding the "compile"...it is not an option for me :cyclops:
[Nexus 7 (2013) Original Android Development] THEBANDIT420:
It changes from device to device depending on the soc binning
[Nexus 7 (2013) Original Android Development] bleuxeon:
Did you look at my voltage table's title?

I am aware of PVS and BIN, but in case of Glitch kernel, its hard coded to 700mV regardless of your CPU's PVS.

I don't like low frequencies like 81MHz, but if I could run it @ 550mV...I could change my mind ;)
[Nexus 7 (2013) Original Android Development] THEBANDIT420:
Why lol its not gonna effect battery life and the device already runs cool at those lower frequencies
[Nexus 7 (2013) Original Android Development] poondog:
Just on this topic

I did a kernel with a friend who his device could take low voltage 700 easy

Anything under 700 (I set the min 600) was unstable

This was HTC m7 which has very similar cpu
[Nexus 7 (2013) Original Android Development] bleuxeon:
Thanks for the info, but on how many devices did you tried it, and what was the PVS of the device(s)?

Also, when you did test [MENTION=1601421]600[/MENTION]mV, was the frequency as low as 81 MHz?

I can anderstand that there is a hard low limit in mV for a chip and that it wont run with anything lower.

But, I can also tell you that I did seen in the past at least 2 others famous kernel's makers ( DorimanX : Galaxy S2 , Franco : Nexus 5) that did at first stated that the lower allowed voltage was and will ever be XXXmV to finaly, a few weeks/months later, lower this "I will never change" lower limit of 100mV ;)

With these very low first frequencies in Glitch's kernel (81MHz and 162MHz), I think it worth trying something lower than 700mV, even if it comes with a bunch caution, warning, hazard red flashing aroma's screen :D
[Nexus 7 (2013) Original Android Development] poondog:
I think PVS is different on m7. He was PVS3

freq was actually 384MHz. Generally this "I never change" is for the users.. I don't do UV myself, I ship my kernel with 50mV under stock and then lets users take it from there. That way theres a slight benefit for everyone. But in my case (can't speak for glitch) I have the voltage lower limit at 700 and not lower so that users cannot damage their devices with my kernel (even though they understand, its damage that can be avoided)
[Nexus 7 (2013) Original Android Development] bleuxeon:
How undervolting could damage a phone? Possible data loss? :confused:

Anyway, just a question :

If

setting the minimum voltage to 600mV or anything lower than 700mV is

rock stable

for 81MHz or even 162Mhz, is it good or bad news?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
I'll lower the limit to like 600 or even 500 for the adventurous guys around here as a test build. That'll feature some Aroma/F2FS checking script fixes (the stock AOSP or alike roms booting issues should be gone) as well.

The rebase is going well, though I need more time still ;)

EDIT : Experiment added to this post. Minimum voltage is down to 500mV in this one. Feel free to try it if you feel adventurous like [MENTION=4459653]bleuxeon[/MENTION], and don't apply settings at boot ;)
[Nexus 7 (2013) Original Android Development] shaolinz:
Tk-Glitch any chance on a new cm kernel?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
After the rebase, yes for sure !
[Nexus 7 (2013) Original Android Development] shaolinz:
Thank you sir and hope you are feeling better
[Nexus 7 (2013) Original Android Development] bleuxeon:
Thanks A LOT :good:

I will test now. and let you know.

Thanks again :good:
[Nexus 7 (2013) Original Android Development] bleuxeon:
I would have never thought that one day I would have to tweak a governor to run 4 cores on @ 81Mhz to run Antutu or Pi stress test :cyclops: :laugh::laugh::laugh:

Very fun so far ;)
[Nexus 7 (2013) Original Android Development] bleuxeon:
OK : very first testing done with the new kernel's lower voltages!

A quick sum for my CPU (PVS=3):

-The BAD news : the lowest stable voltage for the lowest frequency is 600mV for 81MHz

This underclock/undervolting isn't realy intersting since...

-The GOOD news : 384MHz can be undervolted to 637.5mV :good: (remember that stock is 900mV!)

384Mhz will compute 4.74 time faster than 81MHz for a litle extra of +37.5mV.

So I don't think 81 MHz is the lowest frequency to choose, but at least, its here...

270Mhz is in fact a litle bit more interesting since during my tests it has been rock stable at only 612.5mV

Again, that's only a first test and it needs more testing.

Attached : testing results.
[Nexus 7 (2013) Original Android Development] tetakpatak:
Hey I just LOVE to see you back, [MENTION=3847629]Tk-Glitch[/MENTION]!! :)

tetakpatalked from Nexus 7 flo
[Nexus 7 (2013) Original Android Development] Medel-Silver:
81mhz and 384mhz with same voltage don't drain your battery the same way, a simple formule say that, 81 x 600 = 48600 , 384 x 637.5 = 244800
[Nexus 7 (2013) Original Android Development] borxnx:
The matter is time per clock, not the bare theoretical minimum of power per cycle. Jesus, are you trying to pull extra seconds from your battery? Make your own damn kernel
[Nexus 7 (2013) Original Android Development] SynnyG:
Thanks for telling us your results, it's always good to have some new things to try !
[Nexus 7 (2013) Original Android Development] bleuxeon:
Here is the spreadsheet that may be more readable than the graphic.

I think that devices with PVS higher than mine (PVS=3) would be able to undervolt lower than 600mV, and maybe as low as 500mV.

In fact even on my PVS=3 CPU, 587.5mV was stable for 81MHz but I did increased it to 600mV just because 575mV crashed and 587.5mV gives me sightly lower Pi results than 600mV.
[Nexus 7 (2013) Original Android Development] darkspore:
Wi-Fi doesn't work for me. I use MIUI ROM...
[Nexus 7 (2013) Original Android Development] THEBANDIT420:
Voltage isn't the only factor that determines how much the CPU will drain so 384 will drain a lot more than 81 even if the voltage was lower
[Nexus 7 (2013) Original Android Development] BlechMann:
Hi!

Im experiencing some probs running 151 version... Its some more hooking and glitching in typing textfields in Browser vor scrolling UI. Installed 147 Version now and the lag is gone... ?!
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Hello !

May I ask what rom are you running ?

Thx
[Nexus 7 (2013) Original Android Development] BlechMann:
Running latest DJL4.4.4
[Nexus 7 (2013) Original Android Development] Swagthoo:
Best setiings for glitch Kernel

I am curious what would be the best settings for this kernel on flo for battery life
[Nexus 7 (2013) Original Android Development] joeyddr:
With the test kernel my device actually sleeps. Nice. 151 I get a ton of suspend back offs
[Nexus 7 (2013) Original Android Development] tetakpatak:
I have only set the highest frequence to 1.5GHz and find battery life simply awsome by still strong performance. I'm on Carbon nightly 4.4.2 and Glitch r142

Carbon & Glitch are my winning combination :)

Here are my other settings:

tetakpatalked from Nexus 7 flo
[Nexus 7 (2013) Original Android Development] joeyddr:
actually mine started doing it again after a while, if i put elemental x on it goes away.
[Nexus 7 (2013) Original Android Development] bleuxeon:
What is your ROM?
[Nexus 7 (2013) Original Android Development] joeyddr:
Aicp
[Nexus 7 (2013) Original Android Development] bleuxeon:
Ok.

Paranoid here, so the issue arise on 2 differents ROMs...

I will give a try to CleanROM and see what's happend.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
It's the buggy base guys. Better wait for the rebase I guess..
[Nexus 7 (2013) Original Android Development] shaolinz:
I'm waiting Glitch love using your kernels just waiting on the cm based .....keep up the great work and hope your feeling better

PimpedOutNexus7 !!!! Buh-Bam!!!!
[Nexus 7 (2013) Original Android Development] bleuxeon:
oki

I am realy curious to know where the bug is hiding since it happens very randomly.

I was at first supecting my undervolting when I did see it again @ stock.
[Nexus 7 (2013) Original Android Development] aircooledbusses:
Gotta say thanks for all your doing and I've been using glitch as long as I've had my n7. Take care of yourself.

Curious if anyone is running f2fs all. Only my data and cache stick. Any redirect to threads that may help are appreciated.
[Nexus 7 (2013) Original Android Development] tetakpatak:
I was- and I'm back to ext4 again.

Check my "dual boot FAQ thread - devil2 kernel" for Note 2

I saw no performance boost and it was very complicated way to install system updates.

tetakpatalked from Nexus 7 flo
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4773115]aircooledbusses[/MENTION]

I did it during testing but reverted to ext4 system in the end. F2FS feels well worth it on data partition (and to an extent on cache as well), but I don't think it's really interesting on system. As far as I know, most if not all roms for N7 2013 are formatting the system partition as ext4, so it would require to modify the updater script each time you want to update/switch rom to get it to format system as F2FS. An annoying process with very small performance gains as most of the heavy data will be on the.. data partition. :p

Not worth it IMHO.

BTW If you didn't modify the script for your current rom, that's why it doesn't stick. Or if you did then updated (from omnirom update for example), then it has just changed the partition back to ext4, as I was explaining before.
[Nexus 7 (2013) Original Android Development] PlayingPoise:
For whatever reason, I get this weird error where if my tablet doesnt wake for a while (I don't use it for hours or so), I won't be able to turn the screen on. The only way it goes back on is if I hold the power button so it forces itself to turn off, then turn it back on. I have MultiROM, and this doesn't occur on the Android L preview, just on my primary, which is Carbon's latest nightly.
[Nexus 7 (2013) Original Android Development] shaolinz:
Tk-Glitch can't wait until a new cm version of your kernel is out I like using your kernels the best!

PimpedOutNexus7 !!!! Buh-Bam!!!!
[Nexus 7 (2013) Original Android Development] BlechMann:
Hi Guys!

Experiencing some Probe here using DJL4.4.4 Rom with glitch r147 (latest glitch lagged in this). My nexus sometimes getting stuck in screen lock, no chance to wake by powerbutton or dt2w... Everything else working great. Anyone else sich this bug??! Vor anyone with solution?!

Bye!
[Nexus 7 (2013) Original Android Development] nokiagye:
Same here on 151
[Nexus 7 (2013) Original Android Development] 91ludesit:
R152 still won't boot with data formatted to f2fs on the stock Google rom.
[Nexus 7 (2013) Original Android Development] Valantar:
First of all, a huge thank you to Tk-Glitch for this amazing kernel. Really did wonders for the performance of my N7. Unfortunately it seems to kill WiFi on the latest official CM11 Snapshot release. No idea why, it just refuses to turn on. Have reflashed both stock and Glitch kernels at least four times each (glitching with slightly different settings each time), and WiFi is completely dead. Have gone back to the stock kernel for now, but I'm really, really looking forward to the rebase! Hopefully the next CM release will give me both amazing performance and WiFi :D
[Nexus 7 (2013) Original Android Development] nokiagye:
R152? Where is it?
[Nexus 7 (2013) Original Android Development] quickdraw86:
In post #1816 of this thread...

http://xdaforums.com/showthread.php?p=54328261
[Nexus 7 (2013) Original Android Development] bitstra:
this kernel r152_test runs fine with android L preview 79!

No probs with root+SuperSU - other custom kernels had those...

Great job! - Thanx
[Nexus 7 (2013) Original Android Development] whirl08:
152 test is fantastic thank you.
[Nexus 7 (2013) Original Android Development] aircooledbusses:
+1

---------- Post added at 11:09 PM ---------- Previous post was at 11:07 PM ----------

Same here. I don't think it is carbon related. I think I experienced it with liquid and vanir as well
[Nexus 7 (2013) Original Android Development] tetakpatak:
I've never faced such problems with Carbon & Glitch. Still on 4.4.2 and r142, I feel no need for update for my N7 is just perfect this way (Gapps Slim mini, most of G-apps arw dark toggleable)

tetakpatalked from Nexus 7 flo
[Nexus 7 (2013) Original Android Development] _delice_doluca_:
I have exactly the same problem on the stock ROM. First I thought it was related to OCing and un-thicked all the options while making a clear flashing but that did not help either
[Nexus 7 (2013) Original Android Development] shaolinz:
Anything new glitch? How ya feeling?

PimpedOutNexus7 !!!! Buh-Bam!!!!
[Nexus 7 (2013) Original Android Development] aircooledbusses:
Tried the latest l preview and went back to carbon nightly glitch 152 clean install.

Been frequently rebooting with some 22 errors and boot reason watchdog, which I think is better battery stats. Would y'all recommend rolling back to 151, or reinstalling the kernel with less aggressive settings?

Last kernel log

https://www.dropbox.com/s/odc5p74hn2gknxz/2014-08-23_13.52.zip?dl=0
[Nexus 7 (2013) Original Android Development] russell664:
I tried glitch with the most recent liquid build. After my tablet is left in sleep mode for a while, it is unable to wake again, unless I hold the power button and invoke a full reboot.

I will post logs the next time it happens.
[Nexus 7 (2013) Original Android Development] nokiagye:
Same here... anyone have serious lags

?
[Nexus 7 (2013) Original Android Development] AndyYan:
Very occasionally, after waking the tablet, it would only respond to a few actions before halting. This also happens on ElementalX though.

Sent from Google Nexus 4 @ CM11
[Nexus 7 (2013) Original Android Development] russell664:
I don't tend to have the lags. I always have the unable to wake up from sleep after an extended period of time. It never happens on elementalx though.
[Nexus 7 (2013) Original Android Development] agentcelsius:
I occasionally had dead screen after a night of sleep when I was onr151, I am currently on elementalx and have no problems waking screen. i've had dead screen issues on stock, PA beta, dev preview & modded L, with r151. but not on EX kernel.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
The bug is fixed on the new base. I'm doing my best to release the next update as fast as possible considering the annoyance. Thank you for your patience, I know it's taking a while.
[Nexus 7 (2013) Original Android Development] Andromendous:
Take all the time you need bro. Great things come with time.
[Nexus 7 (2013) Original Android Development] tetakpatak:
You are our hero, [MENTION=3847629]Tk-Glitch[/MENTION]! :D

tetakpatalked from the legendary i9000
[Nexus 7 (2013) Original Android Development] russell664:
Thank you for your great work.

Take your time, its great to see you have worked out the kinks. :)
[Nexus 7 (2013) Original Android Development] Mayday_XL:
I have no DS with r151 (stock rom).
[Nexus 7 (2013) Original Android Development] ANDR01DN00B:
Is there a way to implement a doubletap to sleep function along with wake on the L- version? Sorry if you had mentioned a response to this earlier.

And I think IMO that this is the kernel I'll be using for a while if not forever on my new N7. Great job and keep up the great work!
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Thank you all guys. It means much to me. I hope you'll like the next release as much as I want to finish it and share it with you all. Thank you from the botom of my heart.

Thank you sir !

*Spoil* (:laugh:)

Actual development build features the same gesture system as Flar2's Elemental X kernel (Thanks to his great work), so you'll be able to tweak it as much as you want to suit your needs.

/*Spoil*
[Nexus 7 (2013) Original Android Development] ANDR01DN00B:
Haha we won't be able to thank ANY great Dev enough if they present us with phenomenal work! But what would I use to tweak it? Is there an app or some file in sys/Android_Touch or an init.d script?? I'm on Android L preview ROM so any xposed modules aren't going to be an option unfortunately.

EDIT: derp as usual I didn't thoroughly read OP because I am lazy :) got it.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Forgot about Android L already :P You may be more limited than I said, though it's already pretty configurable. I think (and hope) it'll cover your needs as it is.

Don't be so hard on yourself (if it's even english), I probably did update the OP after your message anyway.. I'm lazy to go check the exact hour :) I'm pleased to be able to answer you.

--------------------------

ALERT !

I couldn't wait more so here's a little "preview" or "beta" or a so called development build for the people following the thread. [MENTION=5242870]ANDR01DN00B[/MENTION] you will be able to try on L. I'll get myself a L rom as well as I didn't use it for some time now. Parts of my F2FS ramdisk is/was based on L preview though, so it should help compatibility even with L + F2FS.

[MENTION=3258801]russell664[/MENTION] [MENTION=4795439]nokiagye[/MENTION] [MENTION=1105540]agentcelsius[/MENTION] This build should fix your performance and SoD issues.

The changelog is basically available in the 2nd post, minus a few things, and a few previous features are missing (kernel-based NEON & cache LoUIS for example) as well as some optimizations.

I've added a "PRIMAtor4.4.4.zip" file in the downloads section to get wifi working on any 4.4.x rom when using this build (if required. Example : 4.4.2 rom, or 4.4.4 rom using old wifi blobs, etc.).

Enjoy guys ! Also, feel free to report bugs you may encounter. Thanks !

EDIT: Works nicely with L + F2FS !
[Nexus 7 (2013) Original Android Development] russell664:
Android L, who need android L? :p

Anyway, once i'm home i'll try your new development release, and see how it goes. :)
[Nexus 7 (2013) Original Android Development] matcho13579:
No SoDs for now, I got one or two in 3 hours with the previous build, great work as usual! :)
[Nexus 7 (2013) Original Android Development] tetakpatak:
There is an Xposed module for that.

ROMs like SlimKat or Carbon have customizable soft buttons where you can press (long or short) any of them to sleep...

tetakpatalked from the legendary i9000