yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] GaboWinter:
1. Just go to the path /system/media and replace the bootanimation.zip with the one that you choose.

1.1 I didn't create any bootanimation by the way :eek:

2. Only if you activate the tablet mode on Settings - Interface - General UI - Force tablet mode.

Sent from Nyarlathothep's SGSII..."Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn"
[Samsung Galaxy Nexus] andrew2163:
So I recently updated from stock JB to the latest CM10.1 and I've ran into problems sending SMS messages, I often get the Message Not Sent notification and the red exclamation point out next to the message. No one else, that I've talked to, via FB groups, have seen anything like this.

Some background, SMS was working fine on 4.1 (VZW) but I got the occasional Bug when unlocking the phone where the phone vibrates 2 times and opens up GMail to send a bug report, anyways.

Cm10.1 Experimental

Stock Kernel

Stock Radios

32 GB LTE VZW Nexus

Was suggested it may be the SMSC code, but that would affect every message, not just particular ones.

Other info: I can sometimes, re-word the message(after multiple attempts to resend after reboot, toggle airplane mode/wifi/data) and it will send, though the messages it occurs on have no special characters are small enough not to be converted to MMS

Any info/assistance would be great, Thanks!
[Nexus 4 Original Android Development] show-p1984:
Welcome to the most customizable N4 kernel on xda :)

Bricked-Kernel Nexus 4 (mako)​

Features:

* Based upon Googles msm 3.4 source

* Various other fixes (look @ github)

* Compiled with gcc4.7.2 toolchain (linaro 09.12)

* -O3 optimized

* Snapdragon S4 & CortexA15 optimizations

* Sweep2wake

(Disabled as default, activate through an app like KControl or over sysfs: echo 1 > /sys/android_touch/sweep2wake)

* DoubleTap2Wake

(Disabled as default, activate through an app like KControl or over sysfs: echo 1 > /sys/android_touch/doubletap2wake)

* replaced qcoms hotplug binary with msm_mpdecision (IN-KERNEL, better battery life + performance)

* Extensive sysfs interface for mpdecision with all the tuneables you want (/sys/kernel/msm_mpdecision/)

* replaced the thermald binary with my IN-KERNEL solution. (/sys/kernel/msm_thermal/)

* export krait version to: /sys/kernel/debug/krait_variant

* modified ondemand governor

* Allow OC up to 1,83Ghz, faux123 (from a thermal point of view that is now SAFE)

* Allow UC down to 94,5Mhz

* Fixed min cpufreq resets

* Undervolting (faux123)

* Default clocks: 384min & 1512max

Zip features:

* ramdisk module insertion

* removes governor overrides from the ramdisk

* adds init.d support to your ramdisk (if not already supported)

Check the compare links for the rest :)
​

Where is tha Changelog???

There will be no more changelogs.

Instead the download pages were outfitted with compare links to github for each download.
​

What is sweep2wake?

[youtube]RtmxlnikTiQ[/youtube]
​

How to install?

Flash through recovery. #done.
​

How to uninstall?

Flash this through recovery:

Bricked_uninstaller

Bye.
​

Where to complain about errors/bugs?

Please use the Issuetracker for bugs/errors/feature wishes!

Issuetracker @ https://github.com/showp1984/bricked-mako/issues

showp1984@googlemail.com

IRC Chat: Freenode IRC #bricked
​

Download:

No Guarantees! If it kills your grandmother or your device, I am

NOT

responsible! If you understand this:

(If you download, please hit Thanks below my post! Thank you!)

>>> DOWNLOAD <<<

​

Donor List:

​

> Hall of fame <

Thank you very much!

​

Stock Nexus4 JELLYBEAN JWR boot.img (flash this if you come from another kernel)

Source:

​
[Nexus 4 Original Android Development] show-p1984:
If you look for an app to control your kernel: http://xdaforums.com/showthread.php?p=47773391#post47773391 :)
[Nexus 4 Original Android Development] jarjar124:
it is finally here!!!

i spy sweep2wake ;)
[Nexus 4 Original Android Development] alewis2k12:
So over clock is safe with this???
[Nexus 4 Original Android Development] cmikeh2:
Looking forward to trying this out! Looks awesome. Just out of curiosity is there any reason why this zip is so much larger than the zips for other kernels?
[Nexus 4 Original Android Development] il buono:
I can't wait to get bricked! ;)
[Nexus 4 Original Android Development] Locksmith81:
OP is your friend :D

---------- Post added at 08:38 PM ---------- Previous post was at 08:38 PM ----------

It's a yes
[Nexus 4 Original Android Development] mpttrung:
Flashed it and will report soon :D

Do it need to wipe cache ??
[Nexus 4 Original Android Development] show-p1984:
Soon(tm)

I am currently making final adjustments to sweep2wake :)

Perhaps it will be a christmas present?

From a thermal point of view: Yes.

But if you set a too high clock and your chip craps out because of too much voltage, that won't save it.

Overclocking is dangerous. It will never be safe, the thermal guard just makes it as safe as on any other phone. :)

Yes, because of sooooo many optimizations I pumped into the kernel it was getting pretty big, too big for it to fit inside the boot.img with the ramdisk. SO I had to remove stuff from the kernel and put it into modules (wlan,cifs,tun) which are inserted into the kernel upon boot.

You won't feel the difference but it enabled me to include these optimizations.

(the prima wlan module is 22megs or so... freaky big thing.)

It wipes cache for you.
[Nexus 4 Original Android Development] mpttrung:
Opps ! It stucks at Google logo @@

I am using stock, any idea ??
[Nexus 4 Original Android Development] show-p1984:
I am too on stock, works for me though.

Gimme last_kmsg after you got it into recovery.
[Nexus 4 Original Android Development] mpttrung:
Red : what do u mean ??
[Nexus 4 Original Android Development] harpo1:
Were you on Franco's kernel?
[Nexus 4 Original Android Development] mpttrung:
Yeah ! U got stucked too ???
[Nexus 4 Original Android Development] alewis2k12:
Anybody got a safe OC limit?? And thanks for the help....and coming from Franco as well
[Nexus 4 Original Android Development] show-p1984:
1.7 should be safe, apq8064 is built with that max freq in mind.

Though to be clear: THERE IS NO SAFE OC FREQ. OC IS ALWAYS DANGEROUS!

To all those who have problems, I will provide a stock boot.img in the first post. (gimme a few seconds)

Stock Nexus4 boot.img (flash this if you come from another kernel)
[Nexus 4 Original Android Development] UZ7:
Yeah if you're kernel hopping make sure you reset back to stock. :good:
[Nexus 4 Original Android Development] mpttrung:
Flash to stock using fastboot ?
[Nexus 4 Original Android Development] ceejay83:
you could also reflash your rom
[Nexus 4 Original Android Development] show-p1984:
This :)

It is being thermal throttled.

Look at /sys/kernel/msm_thermal/conf/ To change your settings.

Low being the lowest throttle (first) and high the highest throttle (last).

I wouldn't change the shutdown temperature though. That is currently @ 80°C and you have to change it with some thought put into it.

For starters, the shutdown will try to power off your phone gracefully, in other words it does the whole sync dance so that your phones partitions don't screw up. Should that fail, or take too long it will force the power off.

Within that time the temperature might still rise and we know for a fact that the phone craps itself somewhere beyond the 84°C mark. So I would highly suggest to leave the shutdown temp @ 80°C. While saying that, the max throttle shouldn't be set within 4°C to the shutdown temp. (currently: 76° max, 80° shutdown)

If you move them closer together there is a chance that a temperature spike might trigger the shutdown temp before the max throttle can cool down your phone.

All of this is ofc theoretical. Under normal (25°C ambient temp) circumstances there is no way that your phone is still heating up at the mid throttle step (as it is set as default). If you are in the desert the max throttle keep the temps at bay too, and if you let your phone stress testing in the summer in the sun, the shutdown temp is there for you.

As it is always: Every setting that is in Bricked is tested under every possible scenario I could think of. If you f*ck around with these settings and you brick your phone, it's not my fault. Now happy tweaking.

PS:

To run benchmarks without changing settings @ max the refrigerator is a nice hint. (only if it is >5°C though, everything else might kill your lcd)

Put it in there for 15 minutes, get it out and run the benchmark.

But set it to silent. I freaked out my mother a few years back who just wanted to get something out of it when the phone began to rang like crazy. She never jumped that high again.
[Nexus 4 Original Android Development] Dave778:
0.6 is unstable for me. Keeps turning my phone off. Have to keep turning my phone on as it shuts down every 10 mins or so.

0.5 was great but had a lag issue for me when waking up from sleep.
[Nexus 4 Original Android Development] yym789:
Base my experience, please never, never try OC 1.83G and run benchmark test. it will kill your nexus 4. My first nexus 4 got killed when I run benchmark on 1.83G.
[Nexus 4 Original Android Development] zimphishmonger:
That would be QUITE strange, as I have two separate apps telling me temps. Even in deep sleep, that would be fairly erratic behavior

for something as sensitive as a temp sensor, almost to the point of defect. Must be a strange side effect of too much UV, like the photo "halos" some people use to test if UV is too low.

Let us know what you find out :)
[Nexus 4 Original Android Development] undercover:
Our of interest, what are negative sides to low UV? Say if it runs stable, no artifacts in camera etc, are there any negative effects still?
[Nexus 4 Original Android Development] ptr_hamilton:
The way I've tried it. Adb cat /proc/kmsg > kmsg.txt

But while doing this it doesn't shut down

I have aokp by roman too.maybe he tweaked something which affects kernel..
[Nexus 4 Original Android Development] show-p1984:
Try this one: click me

Gn8 (already in bed)
[Nexus 4 Original Android Development] Higgsy:
I'm getting the phone shutdown completely I have been using the 0.65 version out of the box. Seems to happen when the phone tries to deep sleep (just an observation). It happens the first time the screen is off with me. Using PA Beta 8. Done a fresh install too and same. I will try yo get some logs but from what the other dude says it doesn't happen when its logging.

Sent by Galaxy Note
[Nexus 4 Original Android Development] bigballa:
This exactly happened to me also on the latest one. As long as the screen was on it wouldn't shut down. The moment the screen went off. After 5 min or less the phone would power down.

Sent from my Nexus 4 (AT&T)
[Nexus 4 Original Android Development] ptr_hamilton:
Okay it happend while logging from internal terminal. Here's the log. Hope you'll find something :o

http://db.tt/wQDpjuds
[Nexus 4 Original Android Development] Shaky156:
Reads 80°c temp n shutsdown
[Nexus 4 Original Android Development] valkyrjur:
I have the same problem but more faster. Justo locking The Phone with v0.6 and i need to power on after that everytime
[Nexus 4 Original Android Development] Audioboxer:
Like others I'm on the Xylon ROM and after coming out of deep sleep the phone shuts down.
[Nexus 4 Original Android Development] show-p1984:
Now that is some serious good work. :good:

It shows:

<4>[ 446.532488] ################################
<4>[ 446.532488] ################################
<4>[ 446.532519] - 80 OVERTEMP! SHUTTING DOWN! -
<4>[ 446.532519] ################################
<4>[ 446.532549] ################################
<4>[ 446.532580] Failed to start orderly shutdown: forcing the issue

Which is exactly what I expected. Additionally to that I did my own investigation which indeed shows that temperature sensor 1 (which I included for backup reasons and because it generally showed ~1-2°C more) is indeed itchy in deep sleep.

it ranges from a few thousands to a few hundreds.

I will add a check so we can get rid of the shutdown after I ate my pizza :P
[Nexus 4 Original Android Development] Shaky156:
Lets apply some artic silver thermal compound to our socs :p

Edit: serious note, @show-p1984 normally the temperature never reaches shutdown as its controlled the voltages and cpu freq get limited
[Nexus 4 Original Android Development] show-p1984:
I don't exactly know what you mean by that, but the shutdown everyone gets on 0.55+ is due to a false positive and it's my mechanism that is triggered, not the socs failsafe.

For some reason the 2nd thermal sensor just goes wacky and transmits some serious bullsh*t :eek:
[Nexus 4 Original Android Development] Shaky156:
Looking back at it that didnt make sense but it did in my head lol! I mean i take it its your code on thermal thats shutting the devices down?
[Nexus 4 Original Android Development] show-p1984:
Lol :D

Indeed, it's my code. The failsafe I added to make it more secure kinda failed us with false positives because of the backup thermal sensor I added to the watch list (sensor 1).
[Nexus 4 Original Android Development] estallings15:
Looking forward to trying out this kernel once that is corrected. Thanks, OP.
[Nexus 4 Original Android Development] Ludacon:
Awesome, thats whaht i figured but i wanted to make sure, through some more testing it looks like if i keep hte GPU down to 300mhz or 325mhz the CPU doesnt throttle. I might take a look and see if theres anything i feel ok messing with, but im much more hesitant OCing my phone than say my desktop. I can go get another processor immediatly, who knows when i can get another N4 lol.

Thanks for the speedy response! looking forward to even more bricked goodness!
[Nexus 4 Original Android Development] :
Do you have the cm/caf version still at your pipeline?
[Nexus 4 Original Android Development] krizina:
Does s2w works for you? I have frozen screen while in pocket. While in call keep touching screen, also. This happens on all kernels. Was using bricked for a week with KControl but still the same. Tried both stock and slim rom.

I am on different kernel now, but no help. The best I come up with is TouchControl app. At least no more frozen screens, but still 50% times can not wake by sweep, have to use power button.
[Nexus 4 Original Android Development] Archmag3:
dont use s2w and d2w at same time...
[Nexus 4 Original Android Development] Emilius:
Is it 20140525_040223_exp_cm-6ef0a9c.zip for 4.4.2 or 4.4.3? tnx
[Nexus 4 Original Android Development] sss_ddk:
I keep my phone in a case so no risk of touching screen while in pocket. IT happens that while on a call you wake up the screen, so i end up in settings usually right after the call :)

Had problems at boot when using apps to enable S2W (Trickster etc.). So now i use an init.d script to enable S2W at boot and it works just fine.

Occasionally, i'd wake my phone and the screen would freeze (only power button helps in these situations to reboot). Maybe you have this issue but it doesn't happen often.
[Nexus 4 Original Android Development] krizina:
Never used both at the same time.
[Nexus 4 Original Android Development] krizina:
Boot problems are solved by kernel config tool, e.g KControl, trickster does not help you there, but init.d is fine.

During call touches are resolved using AutomateIt (+ shell execute plugin) or alike to disable s2w during call and enable it after hangup, Tasker should handle it also.
[Nexus 4 Original Android Development] sss_ddk:
Thanks. Never really bothered me so never looked for a solution but i appreciate the help :)
[Nexus 4 Original Android Development] Emilius:
Why I am losing WiFi on CarbonROM nightly 4.4.3 and latest oasp beta (20140605_083506_exp-5bece24.zip) kernel?
[Nexus 4 Original Android Development] Rohit02:
might be the kernel is not updated with the latest wifi drivers..
[Nexus 4 Original Android Development] Emilius:
I was thinking that latest bricked oasp beta is for 4.4.3. That is the reason why that should be included in the kernel name. This is way is really hard to understand. Going back and read all the posts is not possible for me, I am way to busy for that ;(
[Nexus 4 Original Android Development] humba80:
I'm using the beta 20140605 with Mahdi-Rom 4.4.3. WLAN working fine here.
[Nexus 4 Original Android Development] Emilius:
Yes, it all good. With latest SlimROM nightly 4.4.3 is all good. No problems with WiFi at all. Mast be something with Carbon ROM then. :good:
[Nexus 4 Original Android Development] eltonpestana:
I can flash this kernel on cm11 based on 4.4.3?
[Nexus 4 Original Android Development] michelemascia7:
yes :)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] sgs505:
On 4.4.4 ...
[Nexus 4 Original Android Development] Boris_pain:
There was an error "status 7" on my nexus 4 with stock 4.4.4, last CWM, I tried the last stable kernel and last beta. I installed TWRP instead of CWM and then was finally able install the kernel to 4.4.4
[Nexus 4 Original Android Development] justthefacts:
Can you give us some CM love?
[Nexus 4 Original Android Development] sss_ddk:
Anybody manage to take photospheres without crashing?

KK 4.4 and latest beta kernel.
[Nexus 4 Original Android Development] TheNerd:]:
Running nicely on L developer preview :)
[Nexus 4 Original Android Development] karim-ps:
Great job guys.

I don't know why whenI flash this Kernel I lose WiFi , I'm using ParanoidAndroid ROM; Any suggestions please ?
[Nexus 4 Original Android Development] passlogin:
[MENTION=4195844]show-p1984[/MENTION] I want to ask

is scaling_min_freq is set to 918MHz after boot behaviour is normal?

Oh yeah, what does the KControl GPU Control module offers?
[Nexus 4 Original Android Development] jmtjr278:
[MENTION=4195844]show-p1984[/MENTION] this is far and away my favorite kernel. Battery is phenomenal, performance is very speedy and scrolling is so smooth.

Please keep up the great work!
[Nexus 4 Original Android Development] justthefacts:
No more love for Mako? :(
[Nexus 4 Original Android Development] TheNerd:]:
He got a stable release out for mako with a ton of features. Until L what more is needed to be done?
[Nexus 4 Original Android Development] justthefacts:
New S2W and DT2W
[Nexus 4 Original Android Development] Nicknoxx:
Yes! With the death of Touch Control I'd love a way of getting an updated S2W
[Nexus 4 Original Android Development] groovepeppy:
same here, wifi are broken

pardon me cause i don't provide any logcat

really need wifi so i flashback other kernel

willing to flash back if there are fixes for the wifi
[Nexus 4 Original Android Development] hardwareadictos:
Any Lollipop love? :)
[Nexus 4 Original Android Development] justthefacts:
Lollipop love there is.

The question is "any Mako love"?
[Nexus 4 Original Android Development] Emilius:
Lollipop?
[Nexus 4 Original Android Development] show-p1984:
Here you go:

EDIT:

I just realized that this may have looked like a troll post, it wasn't though :)

If you click on the image you will be taken to the latest beta for aosp, which is lollipop.
[Nexus 4 Original Android Development] show-p1984:
Mako's lollipop boot image rootified @ https://drive.google.com/open?id=0B1Tn7X59NcPxek1ZTENxbnBzRTA&authuser=1
[Nexus 4 Original Android Development] karthi89:
After flashing the boot image, we should flash the kernel am I right?
[Nexus 4 Original Android Development] show-p1984:
yes. That image is just the stock lollipop boot.img minus the one line preventing us from getting root.
[Nexus 4 Original Android Development] justthefacts:
Well well well. Look what the cat has brought in.

There is love for Mako after all.
[Nexus 4 Original Android Development] kevinnol:
Mako is love mako is life ;)

Running the kernel now for a few hours, no problems at all. - except that the low memory killer gives me an kcontrol fc.. which is more of an app issue but yeah

Edit: I forgot to give you my thanks for bringing bricked lollipop to the mako :victory:
[Nexus 4 Original Android Development] hardwareadictos:
New kernel from 29 of november avaliable :)
[Nexus 4 Original Android Development] jacomail95:
I bought many months ago kcontrol app. Now, using the new beta kernel, Low Memory Killer section force closes itself when clicked :)

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] kevinnol:
Update inc :p
[Nexus 4 Original Android Development] amack10:
I flashed the boot IMG and installed the kernel and set to highest CPU freq and when I run a benchmark to see what kind of performance I get I get really low scores. Could I have installed something incorrectly
[Nexus 4 Original Android Development] hardwareadictos:
Missing your updates so much [MENTION=4195844]show-p1984[/MENTION] :( do you have any tweaked governor in your kernel?
[Nexus 4 Original Android Development] show-p1984:
ondemand is tweaked through thresholds. There shouldn't be anything more than ondemand + the ability to set a max freqs that you will need.

I opted out of all this governor madness after it became clear that ondemand, properly tuned, serves about 98% of all use cases.
[Nexus 4 Original Android Development] Utkarsh-ezzo:
nice
[Nexus 4 Original Android Development] CrazyGamerGR:
awesome kernel
[Nexus 4 Original Android Development] suarez1907:
? wanna install this kernel but i dont see release date for kernel in your site.There is many much kernel for mako and no information of versions
[Nexus 4 Original Android Development] show-p1984:
You have noticed that right column, did you?
[Nexus 4 Original Android Development] CalculatedRisk:
Hello,

Sorry if I'm missing something, but what is the latest release of this kernel (beta or otherwise) for stock 4.4.4? I can't find any information about it. Thanks.
[Nexus 4 Original Android Development] Streetwalker:
Hi.

I just cherry-picked s2w and dt2w into my own kernel and I'd like to mention that even though both work great, dt2w actually requires three taps to wake the phone. One to apparently make it start to listen and then a double tap to actually wake it up. I don't think I missed anything while merging (my commit log for reference: https://github.com/WalrusMod/android_kernel_google_msm/commits/cm-12.1), and I remember having the exact same issue with faux123's kernel on kitkat.

Thanks in advance.

Edit: Looks like this kernel isn't actively maintained anymore. I have no real need for the patch so I'm just gonna drop it as it causes my touchscreen to go berserk.
[Nexus 4 Original Android Development] show-p1984:
I have no idea where you went wrong. Since my time is currently focussed on other things I can't dig through your whole source either to figure out what is the issue.

How did you reach that conclusion?
[Nexus 4 Original Android Development] Streetwalker:
No problem, as I said I don't really need it. This is just a kernel I build for personal use and I found dt2w/s2w less natural than just hitting the power button.

For the record I merged 11 commits that touched drivers/input/touchscreen (e804382 and onwards) and added the necessary options to my defconfig. I deleted the commits now though.

Latest commit on the master branch was over a year ago, last commits on the experimental branches are just you merging lollipop sources and a few defconfig tweaks in november. Doesn't look like an active project to me.

As for the issues, the touchscreen would become completely unresponsive (or almost) with either dt2w or s2w enabled (under conditions I didn't try to identify but it's definitely reproducible), which made the device impossible to unlock.

Apologies if my edit seemed rude or anything, I suck at phrasing things.
[Nexus 4 Original Android Development] show-p1984:
I am only merging the current bricked base with upstream google because this kernel has everything it needs.

I haven't checked lately if google has updated the sources, but when I last checked (before the 5.0 release on the n6) there were no changes and usually it takes Google quite some time to get to the n4.

I also assumed most ppl would wait for the mem leak fix in 5.1.1 before switching to lollipop as a daily driver.