yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] jsn:
Hmm.. Thats also something I experienced once.. I thought it was after flashing a kernel though (in my case).

The N7 probably crashed and locked up. I had to hold the powerbutton for about 12 seconds to have it reset and restart normally again.
[Nexus 7 Original Development] anilpalepu:
Had the same thing happened to me thrice now...

Its seems to happen during deep sleep..had to boot back up holding power for 10-12 seconds..
[Nexus 7 Original Development] nemotheblue:
Loving you for the Sherlock reference! :D
[Nexus 7 Original Development] Hessi93:
Thank you very much! I was getting worried.

Skickat från min Galaxy Nexus via Tapatalk 2
[Nexus 7 Original Development] olrait:
Got 2 freezes (followed by a reboot) since latest kernel release. Both took place when gaming, or just after gaming while doing other stuff.

Noticed tablet was pretty hot where tegra chip is when having the issue.

Running stock rooted rom. No tweaks on kernel (as is).
[Nexus 7 Original Development] Bosio91:
I'm having an issue with the latest franco.kernel updater app (paid version). I'm on Pure AOSP ROM with r4 installed, and when I open the app, it acts like if it was on my Galaxy Nexus, showing the M5 and r248 builds, leankernel builds, etc... Yesterday I installed ParanoidAndroid 2.1, installed the app, and it worked as it's supposed to on the N7, showing the correct nightlies. I tried deleting data from the app, uninstalling and reinstalling after a reboot, but it still acts as it would on the GNex, GSIII or HOX...

Any ideas on how to solve this? It would be much appreciated :)

Thank you!

EDIT: in the app, under the MAIN tab, it says "Your device is not officially supported in this app... etc...".

EDIT 2: Tried a full wipe and re-flashing Pure AOSP, and the app still isn't recognizing my N7 as it is... So I'm just going to do a full restore and stay at STOCK
[Nexus 7 Original Development] franciscofranco:
Probably because the person that made that rom decided that it was cool to change the device string and it ****ed everything up. The app reads form the Device Name in the settings menu and it should read "Nexus 7" for it to work.

Anyway people with strange reboots etc on r5 try this from adb or terminal:

echo runnable > /sys/devices/system/cpu/cpuquiet/current_governor

On reboot it gets back to balanced so test it for a while without rebooting. You can also do this from my app if you have it. Report back please.
[Nexus 7 Original Development] Bosio91:
I tried this, but nothing happened. The app still wouldn't recognize my N7 as what it is. It might be just me and my mediocre terminal/adb skills, but nevertheless, I had planned today to do a full restore back to stock, and now everything is working. And I do have your app, I think it was the first (and best) purchase i made on Google Play since I first got my Gnexus :D

STOCK FTW!

Thank you for your help Francisco!!

P.S.: I saw you were visiting Barcelona :o I hope you enjoyed my home city and that you were well received!

Saludos!
[Nexus 7 Original Development] franciscofranco:
Lol the command wasn't for you, was for the users having those strange reboots. The only way to have the app recognize the device is if the Device Name is "Nexus 7". If the creator changed that line then we're ****ed. So either use stock or a decent rom that doesn't change that ****.

Yep I enjoyed it very much, thank you :)
[Nexus 7 Original Development] olrait:
Having same issue with updater, it does not detect correctly my N7, so I can't use it. I'm on stock rom though.

Will try suggestion about kernel reboots, will report back. Thanks !
[Nexus 7 Original Development] Bosio91:
I just did a full restore to stock, including locking and unlocking the bootloader, and everything is working flawlessly with r5. Perfection in it's simplest form :D
[Nexus 7 Original Development] jamesst20:
Well no, install the rom you want. Then

1. Install a File Manager

2. Go to /system

3. Open build.prop

4. Make sure the line ro.product.model is like this ro.product.model=Nexus 7

5. Save & Reboot and Enjoy :)
[Nexus 7 Original Development] espionage724:
I thought I read that some person was having problems with N.O.V.A 3 and Pure AOSP, and was told to edit his build.prop to fix it. My assumption is, if you build straight from AOSP sources, the build.prop doesn't have your specific device information, but I don't know.

But as mentioned, you can try editing that file with the proper information, and it should work fine :)
[Nexus 7 Original Development] Bosio91:
I actually realized that I don't need anything different from the stock ROM. In fact, it has been giving me better performance overall, so I'm staying put with it.

Nevertheless, thank you for the help. Next time I get the flashing craving, I'll try this out and see if it works. I'll report whatever happens ;)
[Nexus 7 Original Development] Mr. Steve:
I'm pretty sure TWRP recovery just asks if you want to wipe dalvik and cache after you flash any zip file, it doesn't only do it specifcally for kernel zip flashes.
[Nexus 7 Original Development] ÜBER™:
When you dip below the 400 frequency.. Its using the companion core. It just displays it as one of the real cores.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] icepuente:
Look at his kernel source. He just modified the normal cores to be able to scale below 400 MHz
[Nexus 7 Original Development] RootTheMachine:
Yeah, he said it wastes power when it switches between the companion core and the main cluster.
[Nexus 7 Original Development] Bigzinewicz:
Use Odin if can't get into bootloader.

Try Odin if you can't even get into the bootloader. Search the forums or try the WugFresh Nexus Root Toolkit forum for help as well. I know this is all off topic completely and apologize just wanted to offer assistance as I have been in similar situations before and always got out of it due to XDA forums and helpful people.
[Nexus 7 Original Development] powerdoesntrun:
Thanks. I've tried wugfresh but I seem to have no fastboot so no luck. I'm trying to figure Odin out but I can't figure out how to use it. Thanks for trying. I'm looking in other forums but it doesn't look good.
[Nexus 7 Original Development] ÜBER™:
Odin is only for Samsung devices.. AFAIK.
[Nexus 7 Original Development] franciscofranco:
It's not using the companion core, just the normal 4 cores but I made it to scale from 100 to 1300.
[Nexus 7 Original Development] franciscofranco:
What the hell did you do to corrupt the bootloader? What command did you use?
[Nexus 7 Original Development] powerdoesntrun:
All I did was flash this kernel on my n4, because I wasn't thinking, in CWM. The screen doesn't turn on and the only sign of life is that windows beeps when I plug it in. No vibration, no fast boot. I honestly never thought a kernel could do that
[Nexus 7 Original Development] osm0sis:
Very nice trick! :)

Just wanted to let you know .DS_Store files are all through your N7 zips. No big deal obviously since you aren't pushing /system/ right now, but I thought you should know.

Also it would be better if the zip extracted the boot.img to the Tegra3/N7-specific /dev/block/platform/sdhci-tegra.3/by-name/LNX rather than /dev/block/mmcblk0p2 which could be used on any device.

If you're not going to mount system and check the build.prop to see what device it is (as follows), then extracting by-name is at least some kind of safety against mishaps...

assert(mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system"),
getprop("ro.product.device") == "grouper" ||
getprop("ro.build.product") == "grouper");

...What block does the bootloader live on for the N4? :(
[Nexus 7 Original Development] ÜBER™:
Gotcha i was just assuming since you said 100-300 frequencies were back in. :silly:.
[Nexus 7 Original Development] Meannekes:
One more question, does the kernel something to the sound?

Because today i used my sound the first day since Weeks.

And the sound is scratchy (Bad english sry)

Last time i used the sound, i was on stock kernel

Gesendet von meinem Nexus 7 mit Tapatalk 2
[Nexus 7 Original Development] Bigzinewicz:
Yeah I was thinking of Galaxy Nexus fixes sorry he's right Odin won't work either if the bootloader is corrupted not sure if there is anything else to be done but bite the bullet and try ordering another phone when available again.
[Nexus 7 Original Development] powerdoesntrun:
Just curious. Is at all possible to throw an error or something if the kernel doesn't match the device and stop the flash? If so, it might be worth doing. I was stupid, but wouldn't that help idiot-proof the process a little more?
[Nexus 7 Original Development] osm0sis:
Yup both the things I wrote in my last post would catch or prevent it flashing to the wrong device.
[Nexus 7 Original Development] powerdoesntrun:
Ah, didn't see that. That would be brilliant. Sure beats making one dumb mistake and losing several hundred dollars.
[Nexus 7 Original Development] franciscofranco:
You didn't lose any dollars, thats what warranty is for. But in any case can you get to Download Mode? I don't remember the key combination, a Google search will tell you.
[Nexus 7 Original Development] ÜBER™:
LG has download mode? :confused:
[Nexus 7 Original Development] powerdoesntrun:
Does Google ever turn down RMAs (or I guess LG) due to rooting? I always see everyone worrying about it and asking the question, but ive never heard of anyone actually running into it.

Is that device checking thing a possibility? If so why don't all devs do it?

As far as download mode, I'm not sure. I pretty ,much have nothing on the screen no matter what keys I hold down. None of the toolkits are finding fast boot or adb
[Nexus 7 Original Development] ÜBER™:
Cant really tell the contents if it wont come on.. or be detected by a computer.
[Nexus 7 Original Development] xI mEzMeRiZe Ix:
That's how I always view it. If it doesn't come on, no problem...none of my modifications can be found so getting a replacement shouldn't be an issue. If it comes on, no problem...I can easily fix what I did. This is what I try to explain to my friends when they are scared of rooting.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] mobilehavoc:
Flashing a kernel even the wrong one shouldn't break the boot loader right?
[Nexus 7 Original Development] osm0sis:
On the N7 the mmcblk0p2 partition is the kernel, on the N4 the same partition is part of the bootloader.
[Nexus 7 Original Development] xI mEzMeRiZe Ix:
Aaaaaaaaaand it's gone

Sent from my Nexus 7
[Nexus 7 Original Development] powerdoesntrun:
This is probably where I need to say that I'm not lying that flashing the kernel is all I did. I have nothing to gain from that. Just trying to prevent it happening to other people. Finding a solution without having to RMA it would be a bonus.

---------- Post added at 08:50 PM ---------- Previous post was at 08:48 PM ----------

I have to say after a day like today, I really needed that laugh.

---------- Post added at 08:56 PM ---------- Previous post was at 08:50 PM ----------

There's a message in all this. That message is apparently an advertisement telling people to buy Franco's app instead of flashing manually, something I regret not doing, at this point.
[Nexus 7 Original Development] osm0sis:
And make damn sure you're in the right thread and are downloading a zip meant for your device. :(

Really ****ty that it happened to you man. I hope the RMA goes smoothly.
[Nexus 7 Original Development] powerdoesntrun:
Where were you this morning??
[Nexus 7 Original Development] mobilehavoc:
Ouch. Bad luck indeed.
[Nexus 7 Original Development] osm0sis:
Wish I could have been there to help. Honestly. It sucks. :(
[Nexus 7 Original Development] mobilehavoc:
This.

Or at least append the device names to the files so it would be n7-boot-rXX.IMG at a minimum. I always double check before using fast boot for this precise reason. There are no safety checks built in to fast boot, very easy almost top easy to brick your device.

Like they say with great power...
[Nexus 7 Original Development] powerdoesntrun:
I think its karma for ordering an N4 on launch day and actually getting it the next week.
[Nexus 7 Original Development] mobilehavoc:
I hope not I got it the same week of launch so I'd be super cursed
[Nexus 7 Original Development] opz187:
I'd like to take this opportunity to have a moment of silence in remembrance of our fallen android devices. You served us well..
[Nexus 7 Original Development] powerdoesntrun:
In case there are any mods circling overhead, I consider this all very relevant to the kernel. I'd hate to have to shoo you away with my old broom.
[Nexus 7 Original Development] joaquinf:
I can confirm this. I've done the same and feels indeed smoother.

---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------

Man, reading this makes me feel sad. I'm so sorry about this. I hope everything goes well with the replacement unit
[Nexus 7 Original Development] ragnarokx:
I'll give them a shot. What are these tunable values?

Sent from my Nexus 7
[Nexus 7 Original Development] osm0sis:
:good:
[Nexus 7 Original Development] joaquinf:
Actually I've left the hispeed_load at 700. I couldn't perceive any difference between that and 1000 speed wise. On higher values the device tends to get warmer though.

These settings are a great combo
[Nexus 7 Original Development] Mr. Steve:
Relevant: http://www.youtube.com/watch?v=Q1u-BHllPxs

---------- Post added at 12:34 AM ---------- Previous post was at 12:32 AM ----------

Tell me something, why is the N4 designed like that? Wouldn't it always be a good idea to have the bootloader and kernel in two separate partitions?
[Nexus 7 Original Development] osm0sis:
You misunderstand. They're in separate partitions but different manufacturers position (mount) them differently within the filesystem.

On the N7 mmcblk0p2 is LNX or boot (the kernel), and mmcblk0p6 is USP or staging (the bootloader) on grouper (p7 is USP on tilapia).

On the N4 mmcblk0p6 is boot (the kernel), and mmcblk0p2 is sbl1, one of several sbl partitions which appear to be part of the bootloader.

Those just happen to be inverted for these devices. It's usually fairly random across manufacturers and even devices. For another example, the GN has mmcblk0p7 as boot (the kernel), and mmcblk0p1 as xloader (the main bootloader) and mmcblk0p2 is sbl, another part of the bootloader.

Confusing? You bet! Follow the links for the full partition lists for each device so you can see what I mean. Total count, numbers, use and naming differ across them all.

GN Reference: http://xdaforums.com/showpost.php?p=21840433&postcount=2 & http://xdaforums.com/showthread.php?t=1812959

N4 Reference: http://xdaforums.com/showthread.php?t=2010338

N7 Reference: http://xdaforums.com/showpost.php?p=35103211&postcount=16
[Nexus 7 Original Development] Mr. Steve:
I think I follow, so basically when the guy flashed the N7 kernel zip on his N4 his recovery put the N7 kernel where one part of the N4 bootloader existed right?
[Nexus 7 Original Development] ragnarokx:
So these values are not set using Francis app, right? Or maybe I'm missing something.

Sent from my Nexus 7
[Nexus 7 Original Development] illmatic24:
I changed the hi speed freq manually to 1000 MHz and it seems much snappier opening up apps and browsing in general. I've also set the min cpu to 200 mhz as I read somewhere 100 mhz actually consumes more power than 200 mhz. Is it worth changing any of the other parameters?

echo 1000000 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
[Nexus 7 Original Development] 1pop23:
First day running R38 and it is smooth, fast, and battery is long lasting. Only tweak I have done is setting GPU to run at 512mhz instead of 414mhz. Really love this kernel.
[Nexus 7 Original Development] exzacklyright:
It's not letting me update the kernel with the app. Says md5 values don't match!

Sent from my Nexus 7
[Nexus 7 Original Development] 1pop23:
Just had my first crash while on chrome. Could be the torrent app I was running though as when I pulled last_kmsg.txt it was blank
[Nexus 7 Original Development] johnnyman25:
Im on r37.do i need to wipe cache and dalvik before install r38?thx!
[Nexus 7 Original Development] UmmelGummel:
no, just flash
[Nexus 7 Original Development] NicoGa:
I think this is for Exynos 4 processors. Would be good to know it is effectively true for tegra 3 ....

See II) Question 8 of:

http://xdaforums.com/showthread.php?p=19846276

Envoyé depuis mon Nexus 7
[Nexus 7 Original Development] :
Hi guys. Is this kernel compatible with Nexus 7 3g?
[Nexus 7 Original Development] powerdoesntrun:
That's what I've been told happened to me and it makes sense. Its sort of like trying to practice safe sex in a world without protection. You can take all the precautions necessary, but one mistake with the wrong person and you're done. It's your own fault but it would be really nice to have some damn condoms.

If that's too adult oriented, I apologize. I just woke up and remembered that my phone is a paper weight.
[Nexus 7 Original Development] osm0sis:
Sadly yes, that's exactly what happened when he flashed it on the wrong device, because the zip uses those direct partition numbers. Hopefully he'll have no problem RMAing it. :(

You're missing Governor Control. It's in f.Ku in the Freq/Volt section. :)

Yup that's a new safety check built into f.Ku to prevent flashing a bad download. Wait a little bit and try again, or if you're on mobile data connect to Wi-Fi, etc. etc. :good:
[Nexus 7 Original Development] darkdonkey:
Yep, I got a nexus 7 3g and it works great, I don't have any microsim in it though, so I couldn't test mobile data.
[Nexus 7 Original Development] nagle3092:
Anyone else having the screen detect false inputs on r37 and r38? Not sure how to describe it but after using either release for awhile the screen starts freaking out. Its registering inputs all over that I'm not making forcing me to force reboot. When I rolled back to r31 its fine again.
[Nexus 7 Original Development] :
Thanks for letting me know. I should have my next week and I'll test it with micro sim. BTW have you heard of samba mobile? That's where I got my micro sim for my new n7. You pay £2.50 and you earn data for watching ads. Earned 1.6 gb of free data so far.. Uk only.
[Nexus 7 Original Development] johnnyman25:
So guys r38 works fine?which governor do u use and what governor settings?
[Nexus 7 Original Development] osm0sis:
Please read back 2 pages. Always. ;)
[Nexus 7 Original Development] ragnarokx:
Sorry for the questions - I usually leave my kernel set to whatever Franco sets it to. So for the values posted earlier:

60000

65

1000Mhz

45000

15000

65 must be up_threshold, which I see. The 1000 for hispeed_freq I don't see in the app, so that must be set manually? And I'm not sure where I enter 60000, 45000 and 15000. Two of these must be for sampling_rate and sampling_rate_min?
[Nexus 7 Original Development] osm0sis:
Interactive governor. Looks like you're using ondemand. ;)
[Nexus 7 Original Development] ÜBER™:
Your using the on demand gov... This is for interactive governor and it goes in order from top to bottom. Minus the input_boost

Sent from my Galaxy Nexus
[Nexus 7 Original Development] ragnarokx:
Whew, I thought I was going crazy! Thanks :o
[Nexus 7 Original Development] robrob777:
Does anybody has the r29 zip or r28zip(those didnt have the freeze problem afaik)? Those Were the ones that worked the best. Franco has only 32+ in his site.

Thanks
[Nexus 7 Original Development] blipp:
r38 doesn't have the freezes that r37 did, it's ok to use it, no need to go back to the 20s(which also might be for 4.1? Don't remember what number started 4.2)
[Nexus 7 Original Development] osm0sis:
They worked best because you were running them on JB4.1.x. :p

r38 is back on track. Don't worry. And hopefully JB4.2.2 in late Jan/Feb will fix all the other crap Google broke.

I think r31 was the first JB4.2 compatible build. :good: :)
[Nexus 7 Original Development] RootTheMachine:
It's because they are set at the same voltage, so in theory 100 MHz will take twice as long to do something than if it was at 200 MHz, thus using more power. This also means it will hold wakelock longer if running at that speed. Even if the voltage is less, it won't be more efficient.
[Nexus 7 Original Development] osm0sis:
If you isolate them sure, but that's not factoring in that the governor ramps up the CPU freq to meet load/demand.
[Nexus 7 Original Development] Bigzinewicz:
r38 is the best build so far.

Just wanted to quickly say that the latest build r38 is giving me great battery life and performance on interactive gov and everything default settings. No more freezes or reboots and keyboard lag is gone on stock and Swiftkey as well so just wanted to thank franco for all the hard work.
[Nexus 7 Original Development] powerdoesntrun:
This is off topic, but this is the only place I've seen this :good: phenomenon. I imagine it mean a good job or something, but I don't get the syntax.
[Nexus 7 Original Development] Metallice:
No.

Running 100MHz for 2 seconds will consume less than 200MHz for 1 second and off for 1 second.

If the voltage is the same they would consume the same amount, but that's only if the off state consumes no power which it doesn't.

P = (f)*(v^2)

Sent from my Galaxy Nexus
[Nexus 7 Original Development] Spacemonkie4207:
Science!
[Nexus 7 Original Development] RootTheMachine:
Okay, well I just said that because some Aries (exynos3) devices had both steps at the same voltage, while Exynos4 ditches the 100 step altogether.
[Nexus 7 Original Development] franciscofranco:
R38 doesnt have freezes and <r31 is for 4.1.
[Nexus 7 Original Development] joaquinf:
Dat signature ;)
[Nexus 7 Original Development] xtcme:
R38 and newest Clean ROM....match made in heaven.

top 2 kernels I have tried are faux 123 and Francos. Now to run a complete batt cycle.
[Nexus 7 Original Development] bland.life:
Is the updater app not working anymore?

The app is stuck on r25 as the latest on my N7.
[Nexus 7 Original Development] exzacklyright:
Tried updating multiple times and md5's won't match.

Sent from my Nexus 7
[Nexus 7 Original Development] FReaKRaNT:
I think you need the donate version. I don't think that the free version is being updated. I have the donate app and it shows R38 as the latest stable version.

Cheers, FReaKRaNT
[Nexus 7 Original Development] 1pop23:
Its being updated. I use the free version and flashed to R38 with it

Never mind, I do have paid version
[Nexus 7 Original Development] Puzzlegirl:
I would doubt that, since Franco has said he hasn't had time to update the free app yet since moving countries and getting a new job. The free app was last updated in October which is before JB 4.2 was released.
[Nexus 7 Original Development] 1pop23:
Ya I was wrong. I forgot I had the paid version
[Nexus 7 Original Development] AngryGamer025:
Help

I am running AOKP grouper mr1 build. I just flashed the latest franco kernel with the free app. And I rebooted and now I get the error: com.android.phone has stoped and I cannot do anything. Please help!
[Nexus 7 Original Development] 1pop23:
Flash everything back to stock, then using fastboot manually flash r38. Once that's done flash your new ROM. Should fix everything

Edit:

Assuming you have WiFi model

Stock 4.2.1:https://dl.google.com/dl/android/aosp/nakasi-jop40d-factory-6ac58a1a.tgz

Franco.Kernel R38: http://minooch.com/franciscofranco/Nexus7/4.2/boot-r38.img
[Nexus 7 Original Development] AngryGamer025:
I restored my nadroid, so I am now running again AOKP Mr1 build 1 with stock AOKP kernel. Can I now just manualy flash the r38 kernel?

Send from my Nexus 7 using Tapatalk HD in Dutchy style

Devices: Nexus 7 - Rooted with stock OS
[Nexus 7 Original Development] redsuns:
is this compatible with the stock rom?
[Nexus 7 Original Development] denzel09:
yes
[Nexus 7 Original Development] johnnyman25:
Anyone have any crashes with r38 version using interactive governor?
[Nexus 7 Original Development] denzel09:
no
[Nexus 7 Original Development] Mac of York:
So far, r38 is everything we've come to expect from Franco... an amazing kernel.