yashsingh1/xdaforums huggingface dataset:
[G2 Q&A, Help & Troubleshooting] Vitalstatistix:
My D802 (2 years and 2 months old) was running on the following

Rooted : Yes

Recovery : TWRP Blastagator v3.0.0.1

ROM : Blisspop v6.0.1 (FEB05 Build)

Bootstack : Hybrid

About a week ago, phone all of a sudden started heating up without any warning. The phone was idle, no gaming, no flashing, nothing. The screen went blank, the temperature continued rising, I could hear the phone working in the background, I tried turning the phone off. After an hour the phone was back to normal temperature, I tried to turn on the phone but it wouldn't turn on even after charging for a long time. Tried all methods (fastboot, download mode, factory reset etc) , even when I plugged in the device to a PC it did not even detect anything (not even as 'Qualcomm etc' as it does when it is bricked etc).

Took my G2 to the nearest authorised service center, we tried to troubleshoot where the problem was at the center by

- Swapping batteries (my phone still didn't work)

- My motherboard on a test G2 device at the center, the phone booted up but was stuck in the bootscreen (blisspop logo)

- A new motherboard on my G2 and it looked like the phone worked but the display was not

Representative's Conclusion: ROM has caused overheating, leading to shorting of the circuit in the motherboard and the heat also damaged the display. Repair costs equivalent to $300 (here in India).

What could be the root cause for the over heating which eventually led to mother board and display being damaged?

( I have been flashing custom roms on this specific phone for close to 2 years without any problem, and even the latest ROM and the build was working without problems for over 2 weeks before the phone over heated)

I really want to understand the root cause so that if it was something that I did which caused this or anything else , I can be more careful in the future.

Is there anyway I can salvage the phone with minimal expenditure or is it just an overpriced paperweight now?

Kindly help!
[Android General] nxss4:
Hello,

I'm in a battle with my 16gb galaxy s4 (well, more like 8gb actually) over free space.

I'm using FolderMount to move/mount some big apps and files to the sd card.

Suddenly I remembered that, once updated, system apps can be replaced by their factory version.

Doesn't that mean that the factory version of every system app is stored on the device?

If so, couldn't I gain some space by uninstalling some system apps (like some google apps) and reinstalling them as user apps?

Thanks in advance,
[Galaxy Grand Prime General] thereallugo:
https://www.youtube.com/watch?v=-YWfmc7mywk

including wifi and data + all hopefully we will see cm13
[Galaxy Grand Prime General] Has.007:
You Should Provide The Source..

http://xdaforums.com/grand-prime/development/cm11-cyanogenmod-11-galaxy-grand-t3263993

Cheers.
[JAM, MDA Compact, S100 General] GnatGoSplat:
I like the HTC Home Plugin that came with the WM6 I flashed into my HTC Apache. Mainly I like the big clock and large icons.

HTC Home Plugin, unfortunately, only works with WM6 so I can't use it on my Magician (i-mate Jam). Is there any free WM2003 home plugin that is similar in appearance with at least the big clock, and can support custom themes? I tried searching Google and most of what I find is for WM5 or newer or not free.
[JAM, MDA Compact, S100 General] ronski:
phonealarm + touch skin
[JAM, MDA Compact, S100 General] twolf:
rltoday+skin:

http://rotlaus-software.de/forum/viewtopic.php?id=519
[JAM, MDA Compact, S100 General] korbenph:
tried both implementations on rx3715.

@phonealarm +Touchlke Skin v2

- straighforward

-weather not working (its okay)

@rltoday +Touchlike Skin

- tricky

- needs to install rltoday, mortscript, skin

- memory hog

my 0.02cents
[JAM, MDA Compact, S100 General] jaugusto:
check this out:

http://xdaforums.com/showpost.php?p=1609954&postcount=516

;)
[Nexus 6 Android Development] RenderBroken:
R1 is HERE!!!

Things to note:

I had been working on this release for some time now. About 3 weeks. I have been getting a feel for the n6 and where I think I can gain some optimization and not lose performance/battery. I use MSM_Hotplug as the default hotplug. I have tuned to to what I believe will give you just as fast an experience than with the Stock "All 4 cores online" MPDecision. Except I am keeping up this performance with only 2 cores enabled. I could not be happier with what I have been able to pull off. If you look through my source you will see that I have tried to piece together a cohesive kernel without just mass importing from another. My plan for this kernel will be to have one that is deliberately constructed and as lean as possible. I am going to aim at keeping out as much cruft as possible. Lastly, note that I do this work for myself first and for you all second. I work 2 jobs and have a family that comes first. I love Android Kernel development and ope to get others involved as well. Lets keep this thread interesting with development discussion and trials. Also, I am not against some OT as long as it doesnt devolve into baselessness and drama.

Kind Regards,

Render
[Nexus 6 Android Development] RenderBroken:
Reserved
[Nexus 6 Android Development] neobuddy89:
Welcome to Shamu! :)
[Nexus 6 Android Development] Lawlrus:
Glad you finally made it bro.

Whole family is here now.
[Nexus 6 Android Development] OptimaPrime:
First Blackbird and now Render did I accidentally wander back into the G2 forum?
[Nexus 6 Android Development] TransportedMan:
Same performance as all cores online with only 2? Alright I certainly have to try this out to see if that could be the case.
[Nexus 6 Android Development] bleached45:
RENDER!? Here on the N6? You made the G2 another beast. I love Hydra Kernel but I'm really glad to check this out.

Good to see you again man.
[Nexus 6 Android Development] RenderBroken:
Please do and let me know!

Now to hedge my bet a little, we all know if I were multi-tasking, of course running 4 cores is always better than 2. What I am talking about is the User Experience (UX). The UX is comparable to using the Stock Hotplug driver but I am using Neobuddy's Modded MSM_Hotplug. That coupled with other changes I have made around the kernel allow me to use 2 cores as long as you are touching the screen, 1 core only after a certain amount off time when you stop touching the screen. Of course when you open an app or do something intensive like that, the 3rd and 4th core can/will online to accommodate the extra load till the load is below a certain threshold and then the normal 2 cores online while touching the screen algorithm kicks back in. Using this setup allows for a smooth UX while keeping battery drainage to a minimum but is able to scale properly when the need kicks in.

So what this means to those of you that do not understand the above, this kernel is battery conscious and smooth while scrolling and browsing and will kick into overdrive when needed like during gaming and other heavy, intensive processes like using Titanium Backup.

This is why I like to balance different changes in the kernel to make sure the UX is not messed with. Just remember, I run my own kernel and it would drive me nuts if there was needless lag all over the place!

Hey! Glad to be here. I have been wanting to get a phone that uses the newer 3.10.x based kernel and could not pass up the great deal I got for my N6! Also, I too really enjoy Neobuddy's work and you will see many things that I use of his. We share alot of the same Design goals I believe so there will be some things that will feel familiar and some that will be new.

But I could have kept making more and more changes to the current kernel and decided that I had to release now or I never would anytime soon. I need more ppl to test my kernel and there is no better way than releasing it to the wild!
[Nexus 6 Android Development] arifqur:
What a reminder of the good old days of the G2.

Your purchase of the N6 means we will really get the max out of our N6 as well.

Welcome to this great community.
[Nexus 6 Android Development] danmaman:
Hi Render

Welcome to the N6 family :o

Kernel is fantastic, great battery

But is this normal on the screen?

Thanks in advance

And enjoy the time here :good:
[Nexus 6 Android Development] RenderBroken:
Thanks!

Yes, that is supposed to happen. Those two SYSFS's are not present in my kernel because they did not work anyways. Our sound driver doesnt allow for us to make changes to those variables. Now, the reason you see the error is because Synapse back end sees that we are using Faux's Sound Control and expects all 5 SYSFS entries to be there when infact there are only the 3 that are really used.

Same with Franco's. I just modded the OG Sound Control driver to remove the unneeded cruft.

Thanks for the report! Glad to clear that up.
[Nexus 6 Android Development] danmaman:
OK no problem... I understand

Now I'll do a full charge, and let's see how the kernel runs :good:

Thanks a lot
[Nexus 6 Android Development] noidea24:
One of my favorites on my vs980 LG g2, glad to see it on Shamu! I'll be testing this with mokee later today, if I can wait that long.

Also, is it against the rules to ask you to add a patch?

I use my Nexus 6 as a keyboard for my server computers to navigate through BIOS settings, I use an app called "USB keyboard". But the app needs this patch to run here
[Nexus 6 Android Development] RenderBroken:
Hey! Glad to see you here. And, no, its perfectly fine to make a request. I will always consider them and if it makes sense, I will make the changes requested. Also, that was something I was going to merge in anyways! :) I will go ahead and queue it up for R2.
[Nexus 6 Android Development] Droidphilev:
Hello,

Thank you for this release!

The default settings are ok for day-to-day use please? Or is it better to set everything up myself? (im not very familiar with synapse and that UKM thing). If something really needs to be set up by user i would use Kernel Adiutor.
[Nexus 6 Android Development] RenderBroken:
I actually use Kernel Aduitor myself. I have not updated my UKM in awhile. It looks like I will be needing to make some changes to make it compatible with SHAMU. Also, of course the default settings are good. I think only a few things were left out when I released. One being setting the default gov to Interactive. It scales better than SmartMAX imo. Also the Min and Max Freqs were not set to stock like I want the default settings to be. I cannot remember anything else but even with those things missing, the kernel runs freaking great. I am really excited for the future of this kernel.

ATM, I am getting 1.5 Hours SoT per 25% but that is also with using wifi 100% of the time and Bluetooth connected to my headset listening to music and audiobooks all morning. This measurement was about 5 hours of use. I have listened to about 3 hours of music/audiobooks and have been connected to wifi for about 3 hours. I am what I consider a moderate to heavy user. I also use my phone for work so I have 3 email accounts syncing along with their calendars (I have two jobs). So all in all, I am pretty impressed considering I have the settings setup to be smooth without sacrificing performance and battery too much. What is the point of having such an awesome phone if you deal with lagging and stuff. I will alwasy opt for a smooth UX while building this kernel. I assume everyone can at least get to a charger at the end of the day so I am not too worried about making a marathon build. But I am sure you can tune this kernel to be one though. More features are incoming that may help.
[Nexus 6 Android Development] danmaman:
Hi mate

i use the default settings with smartmax....and i'm happy with it:good:
[Nexus 6 Android Development] Droidphilev:
Hi,

Thanks all! Will flash and keep setting as they come.
[Nexus 6 Android Development] danmaman:
:good::good:

I only changed vibration... That's it
[Nexus 6 Android Development] RenderBroken:
well rest assured that its fixed in R3.
[Nexus 6 Android Development] Amaze209:
Can't wait for R3 ?
[Nexus 6 Android Development] RenderBroken:
If those of you dont really care for using XDA for updates. You can join my G+ Community at:

Render Kernel
[Nexus 6 Android Development] Dachfenster:
Yes, it was some memory heavy browsing I guess. Quite a few things running in the background and loaded a huge site.

Same thing with first freeze beforehand.

Otherwise it's running god damn smooth, absolutely love it and can't wait for r3. :)

Thanks mate! :highfive:
[Nexus 6 Android Development] RenderBroken:
Hey guys, I just wanted to drop in and let you know that I have not stopped working on R3. MAJOR changes incoming. I have been using G+ to help with testing builds. RIght now I am on Test build 36. That should let you know how much work I put into these releases. R3 should be ready very soon.
[Nexus 6 Android Development] RenderBroken:
R3 is here!!! Finally!

Download

Things to note:

This build will completely change many conceptions many of you have. I know it has changed my own. Know that this build has taken me many weeks to perfect. It has taken 46 test builds to get to the point where I feel ready to release. I am very proud of what I have been able to do. It is nice to look back from now, to when I started and see the growth that has been made. Now I am helping others learn when I wish there was someone to learn from back when I started. Whatever, now to the meat and potatoes. . .

Changed from a Load based hotplug driver (MSM_Hotplug) to a new hotplug driver from [MENTION=3795148]neobuddy89[/MENTION] called State Helper. It has been designed primarily with the N6 in mind. There has been much testing between us and I feel it is ready for Stable builds.

It is designed as follows:

1. It will online all 4 cores now

2. It will respect Thermal Driver and BCL - This means that if you have Core Control enabled in either, it will not online a core that Thermal/BCL has purposely offlined.

3. It will have different configurables

4. One configurable is Battery Level Thresholds (batt_level_eco, batt_level_cri) batt_level_eco is set at 20% battery life and at this level it will only allow a maximum of 3 cores online. At batt_level_cri (10%) is will only allow 2 cores online

5. You can control the number of cores during screen off, currently it is set to 2

Once again, all of the above is configurable. You can adjust all of the above values.

So Hotplugging has changed drastically with R3.

There have also been a huge number of governor changes/tunings and such. You will not believe the amount of batterylife you will now get while maintaining an even smoother experience than you are used to. It has been fine tuned so that when using Interactive, it will idle at 268MHz pretty quickly. It will REMAIN at 268MHz without jumping around like you are used to seeing in Interactive or other kernels. I was quite blown away with this finding. I have never seen Interactive behave the way it does in R3 ever in any kernel before and I have tested many. Not only that but CPU-Boost has been fine tuned for the best performance/battery I could get.

I have completely redid Low Memory Killer and removed the VMPressure commits that I believe were the cause of all the Low Memory Thrashing/freezing. I maintain a steady 500MB - 700MB RAM free at all times.

There are MANY more changes under the hood but I went about this rebuild with a couple things in mind, stability, speed, and simplicity. You can make too many changes to a thing before you turned its code path from 100 lines to 1000 lines. This means more time to complete the function. But you guys be the judge and as always let us know what you think either the G+ Community HERE or here in the XDA Thread.

I would like to thank all the Testers in the G+ Community. You have been invaluable to this rebuild process. For those that like to see the detail of what all I have done see the MASSIVE changelog below.

Changelog:

Too MASSIVE to post here, there is a character limit lol
[Nexus 6 Android Development] neobuddy89:
All the best, [MENTION=5438598]RenderBroken[/MENTION]. :)
[Nexus 6 Android Development] fares70:
Thank you for your hard work ! Downloading right now .
[Nexus 6 Android Development] Tex99:
Wow, it s so smooth !!!! That s great, thank you for the hard work!!

Just a notice, wake gestures don t work, in particular sweep2wake (works only d2tw if I enable only this)
[Nexus 6 Android Development] RenderBroken:
Guys, you have been using R3 for some time now. I want to know how it is running for you all. LEt me know so I can adjust accordingly.
[Nexus 6 Android Development] christianpeso:
I seem to be getting a slight bit of lag scrolling thru my Instagram where I was not getting it before. Coming from the stock UnicornsBlood kernel that comes with Dirty Unicorns. Currently messing around with input boost speed and times to see if I can get it straightened out. Level of battery wear seems to be the same so far. Still too early for me to tell to be honest.
[Nexus 6 Android Development] Stroky:
Wow that Sounds great.

Hopefully it works with Exodus, will try it later on.

Gesendet von meinem SGP511 mit Tapatalk
[Nexus 6 Android Development] fares70:
Just did clean install of todays RR build with R3 release . Everything is supersmooth und very fast . Will report back about Battery backup in a day or two. Thanks Dev , great Work !
[Nexus 6 Android Development] golfgtiedition30:
I flashed R3 yesterday with a clean ROM flash.

After a days usage on stock settings the battery seems excellent with no lag/stuttering in scrolling.
[Nexus 6 Android Development] RenderBroken:
Right on. Most likely it is due to them using Stock MPDECISION and it boosts to 1.5GHz for 3 seconds. But I have also been making more tuning changes. Thanks for listing your previous kernel so I can get a baseline of your experience.
[Nexus 6 Android Development] Shamestick:
Been pretty smooth for me though battery life hasn't been great even with minimal use. No rogue apps either according to BBS. Have been running stock settings except lower vibration strength and screen RGB. I've only been on it for one charge though so I'm not holding snyhting against it and will continue to run and see where it goes
[Nexus 6 Android Development] michele72:
Hello, I've been using this for few days, needs more time to settle down and establish if battery is better than HellsCore at similar settings. I absolutely love the Mako hotplug in Hells so it will be difficult to leave.... One thing that definitely doesn't work as intended is the wake gestures, as another user reported as well. I figured out that to make double tap to work I have to remove all other gestures options and select "halfscreen". No other option works, and even prevents the double tap to work if selected. Particularly, the "draw circle to open camera" doesn't seem to work at all. Will report on battery usage and overall smoothness soon. Thank you for your hard work anyway!
[Nexus 6 Android Development] Dachfenster:
Had a reboot today before my alarm could go of - that was pretty nasty tbh :laugh:

Is there a way to configure the hotplug settings? Always had problems when only allowing 2 kernels when screen's off, so I'd like to change that.

Apart from that running smooth af (except for the wake gestures as already mentioned).

Edit: At some point my hardware keys stopped working til reboot - don't know if rom (pure nexus) or kernel related though.
[Nexus 6 Android Development] Daandofreak:
Try input intervall 500 ms and boost for all cores 1190., no more lags on my side.
[Nexus 6 Android Development] :
Anyway that you could PM me the path for the new hotplug and the sysfs files in that path? Some should be pretty obvious, like the percentages or number of cores. But if they're not... then the expected values would be super.

Thanks!

(Haven't been able to download yet, but I'm really looking forward to it!)

you should be able to do something like this to get the info:

(taken from superuser)

for f in *; do echo "Filename: $f"; cat "$f"; done

or if busybox/toybox have the "more" command

more * | cat

to list them all and their contents easily.
[Nexus 6 Android Development] modernbummer:
Running well for me. No random reboots. Seems to be a good balance of performance and battery life.
[Nexus 6 Android Development] II_DiE_4:
Hey Yoinx. Can you also lookup the Auto high brightness? It doesn't seem to work
[Nexus 6 Android Development] :
Works fine on every kernel I've tested it with. Not really related to this kernel though (unless it's specifically not working here). No reason to derail Render's thread.
[Nexus 6 Android Development] RenderBroken:
Not sure what the problem is for Wake Gestures, I have the exact same code as Neobuddy and they work fine for him and not me. I did have the exact same code as Flar's kernel and got the same results. So not exactly sure but it is not highest prority atm, though I will not give up on it. I really only use DT2W and with the stock kernel settings I ship mine with, DT2W works as intended. Its when you make any changes to any other wake_gesture sysfs, things go nuts. But as I said, I will continue looking into it.

For the reboot, I need more info like:

APPROX Battery Level

Rom name

Logs

Logs

More Logs lol

Particularly, console-ramoops and dmesg-ramoops. They are located here "/sys/fs/pstore"

The sysfs entries are located here:

/sys/kernel/state_helper/

batt_level - lists the current battery level (Really just for information).

batt_level_eco - This is defaulted to 25% and is the level at which 2 cores are taken offline (This is designed to help with BCL Reboots at low batt levels)

batt_level_eco - Number CPUs allowed online at batt_level_eco.

batt_level_cri - This is defaulted to 15% and is the level where only 1 cores is left online.

max_cpus_cri - Number CPUs allowed online at batt_level_cri.

batt_limited_cpus - The number of cores allowed online due to battery levels listed above. Once again just here for information purposes.

current_temp - self explanatory

debug_mask - self explanatory

enabled - self explanatory

max_cpus_online - number of cores when screen is on.

max_cpus_susp - number of cores when screen is off.

target_cpus - Number of cores State_Helper believes should be online at screen on/off.

therm_allowed_cpus - The number of cores allowed online due to Thermal driver with Core Control enabled. Once again just here for information purposes.
[Nexus 6 Android Development] Dachfenster:
Thanks for the answer. The funny thing is: I haven't had a reboot since then.

So fingers crossed. :o

The sweep to sleep gestures do work btw.
[Nexus 6 Android Development] RenderBroken:
yea, I know. But they dont work 100% right. sweep to wake, I could get to work in all directions, just not left to right.
[Nexus 6 Android Development] Dachfenster:
Had a reboot today at ~58%.

The logs you asked for are here:

https://onedrive.live.com/redir?resid=D79D8695F9A10E9C!1774&authkey=!AMAgNARCev9KLDE&ithint=folder,

Edit: Reboot today at the exact same battery level and again whilst screen off. Today's logs can be found under the link, too.
[Nexus 6 Android Development] Stroky:
Flashed Version 3 right now.

Lets see how it goes!

Never seen before a touch boost of 2 seconds but with a low freq :)

Gesendet von meinem SGP511 mit Tapatalk
[Nexus 6 Android Development] Virus1x:
With synapse are we unable to change the cpu govenerner
[Nexus 6 Android Development] rignfool:
Don't use synapse... Use kernel aduitor...
[Nexus 6 Android Development] Dachfenster:
Regarding wake gestures: there might be a fix by flar2 addressing the issues here as well.

http://xdaforums.com/showthread.php?p=66350641
[Nexus 6 Android Development] :
Seems to be running pretty good so far.

State helper seems to work pretty well too.
[Nexus 6 Android Development] Seanzle:
This kernel is boss
[Nexus 6 Android Development] :
This kernel runs excellent with AOSiP...no lags, decent battery.... I think I found a keeper!!!
[Nexus 6 Android Development] pillo85:
Can I run this kernel on stock ROM or is it exclusively for CM/AOSP ROM?
[Nexus 6 Android Development] BeDesireS:
Stock is nearly the same as aosp, so sure you can use this kernel on stock rom, if you can flash it.

Send from my AOSiP powered Nexus 6