yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II N7105 Android Development] rogersb11:
LMAO, it's all good man. I'm sorry you've had so much trouble. Well DN3 is TouchWiz as you know and the Linaro toolchain I was using to compile the kernel appears to have been the issue. So while running my kernel the reboots were from that, I'm just not exactly sure where because the kernel uses very little debugging which helps with speed and battery. I'll fix that later because for now I am just using a different, more stable toolchain. The no boot at all issue you had is from the blobs that my kernel uses and DN3 kernel is older and CAN'T use those blobs causing the bootloop issue. Doing a complete wipe and install should set you up exactly as you were before. Then when it's running good again WITHOUT my kernel is the best time to make a backup. I changing some things in my STweaks setup and then I will be uploading 3.8 which I used to do a clean install on TouchWiz WITHOUT it plugged in and I put it throught some strenuous stuff while it was downloading updates from google because that it when latest issue arose for me and I didn't have one single issue so I THINK at least the issue is solved for the time being and DN3 users can use my kernel again. It worked for DN3 in the very early stages but hadn't worked correctly in some time, basically since I changed the toolchain. Thought I'd be ready by now but not quite. VERY VERY CLOSE tho. Again sorry you've had so many issues. I didn't have a device for several weeks and wasn't really able to work on anything but I'll get tho that when I release because I have someone I owe a MASSIVE thanks to
[Galaxy Note II N7105 Android Development] neopanther:
Where I stand now is I wiped EVERYTHING but the ext. SD card. I flashed back to CWM to flash the rom. I tried to load the rom unplugged but it started power cycling. As soon as I tried again with it unplugged it completed. I started thinking maybe it's a battery issue but as long as I'm in rcovery (either) it stays on unplugged with no problem. Could there be something in my sd card that is carrying over? Should I flash the rom from the phone's memory? The rom loaded fine but I guarantee the moment I unplug it the phone'll shut off.

---------- Post added at 09:33 PM ---------- Previous post was at 09:29 PM ----------

I meant I tried it again with it PLUGGED and it worked. Now it's sitting on the Samsung galaxy note II screen and won't stop power cycling. I'll leave it for a few minutes and see if anything changes. I don't get why something with the whole OS removed is making it do this. All I know to do next is wipe the whole OS again and then try to put it back to stock. Unbelievable.

---------- Post added at 09:45 PM ---------- Previous post was at 09:33 PM ----------

Now it's loaded the entire OS and still won't stop power cycling the moment I unplug the phone. That does sound like the kernel to me becteause it has something to do with charging. Of course I'm nowhere near the expert you are. Sigh......Now it's telling me the battery is at 16 percent though it's been charging all morning.
[Galaxy Note II N7105 Android Development] rogersb11:
You mean internal sd and external you didn't wipe? It COULD be something in your internal sd for sure. That actually happens all the time. Using only the rom and without a custom kernel the issue HAS to be in rom or some sd file. Flashing from either sd should be fine as far as that goes. And what do you mean by power cycle? When's it's plugged in but off it's just sticks at the battery screen until you pull the battery? That is from the dn3 kernel not supported the lpm( low power mode) for off charging. If you didn't wipe your internal sd I'd back it up and wipe if it was happening to me. Solved issues for me several times. Clean wipe and install of the rom only leaves very few things that could be causing this. I'm not finished but in just a minute I'll upload a test version of my kernel you can try before it's fully ready but I'd still seriously consider backup up and wiping that internal sd. So many junk files that you don't even realize are there get stored over and over. I wipe mine every now and then just to avoid this
[Galaxy Note II N7105 Android Development] rogersb11:
Good grief. You said you isn't flash my kernel this time correct? So gotta be whatever kernel they have included in the rom
[Galaxy Note II N7105 Android Development] neopanther:
I'm sorry. To clarify I wiped everything but my sandisk 64 gb micro sd. I wiped internal a bunch of times. I just did and then flashed cwm. That's exactly what I did before. I have a thought: The one I'm trying to flash says N7100 (the dn3 version) Maybe when trying to fix this I wiped out the LTE version that I needed. The only thing is LTE shows it's working on the phone. So I doubt that's it but to try all possibilities...sigh...I'm willing to try anything. I didn't flash your kernel AT all. I have been flashing the rom off my external sd (the sandisk). I'm thinking I have the right rom. (DN3_v5_N7105_by_E-Team) especially because (as I said LTE appears to be fully functional). I can't find the LTE version of the rom because it appears e team took it off the site. I was going to redownload it to test it. I'm scratching me head on this one. Maybe I'll look for the correct apni kernel you mentioned. Booting and fully functioning only when plugged sounds really odd.
[Galaxy Note II N7105 Android Development] rogersb11:
That's the correct ROM version. Something wonky is going on in there then if didn't flash a kernel at all. I don't run that rom so I can't help there. You can try this if you want but it has blobs so if it doesn't work rom will need dirty flashed to replace what mine will delete. Trying to finish the full update and an old blobs zip before I actually release but you're more than welcome to try this as a test. It's working for me flawlessly on my TouchWiz rom. Maybe try my recovery. Switching back and forth is a pain imo but up to you. My Philz has a twrp mode to restore old twrp backups. Anyway here's the test kernel, up to you. If you download it tho let me know when you have it so I can remove the download from DB until fully finished. Just letting you have it to see if it helps you

https://www.dropbox.com/s/cp3t4eg3umniksj/Shift-3.8.zip?dl=0
[Galaxy Note II N7105 Android Development] neopanther:
So I wiped it COMPLETELY using twrp. Then Flashed the stock rom. Still doing it. I wiped the OS. Still doing it. Restored the OS. Still doing it. Restored the nandroid backup still doing it. The second I unplug the phone. Dead. It also tells me the battery is dying when it's not. Something about it seems to have changed something in its system. I suspected the battery at one point but a battery would die even in recovery if that low. The 3.8 shift kernel didn't work. I wiped the entire system and flashed back to stock. I waited til' it was loaded pretty well to pull the cord out to see if that made a difference. Nadda. A software file won't cause a hardware problem will it? This is crazy.
[Galaxy Note II N7105 Android Development] rogersb11:
Something is up with your device for sure. Nothing in anyones kernel for this device would cause this issue. You did flash the wrong Agni tho but that still shouldn't be a factor. My kernel rebooting TW is nothing new in the last month as everyone has had that issue but what's happening to you is way different than any other. You said you're flashing stock, how? you need to be using Odin at this point to just restore the device to pure stock. then just root and start from there. Sounds like you've got some corruption somewhere. Kernel flash is crazy coincidence but without it would have ZERO affect on this issue. It leaves literally nothing and doesn't change any software and sure can't change your hardware. I don't know what latest tmobile is or what BL you have but Odin to version you have BootLoader of for sure. It's your only option
[Galaxy Note II N7105 Android Development] neopanther:
Yes. I used Odin to flash back to stock. I was stock and unrooted. Then I rooted. That's what's happened here. I've never had a device stubbornly refuse to behave like this. I'll look into something else but this is indeed bizarre.
[Galaxy Note II N7105 Android Development] gregsarg:
Hey peeps....we are back in business. ..so let's rock this thread. ..and this device for a long time to come.

I hate locked phones. .and came back in support of our generous devs...

[MENTION=5554845]rogersb11[/MENTION]

You give heart and soul to our users here.

And a spare device is a small price to pay for your fantastic work.

Thank you for the great code Brother...and for all you give to us.....g
[Galaxy Note II N7105 Android Development] lucaoldb:
Just a little bit unstable

I own one N7105 and I've been using with DN3 Rom your first release since day one without any trouble. The rom i odexed (by me) and many things are different from the "stock" DN3 in system, but it has been very stable with you kernel since august.

Now I'm testing version 3.8, wich makes the phone surely faster, but not everything is ok.

1) after flashing the kernel with TWRP and rebooting, there was no way to save wifi passwords (I went to recovery and fixed permissions, which solved this issue);

2) after the first, second and third boot, most apps did not work and the phone rebooted or even went black (I had to remove battery);

3) no wipe was useful, I just had to wait some minutes for the phone to get somehow stable;

4) for some unexplained reason, the cpu clock was set to 2160 and it was very likely the reason why the phone was so unstable and hot as hell;

5) now the phone looks quiet:) but cpu settings don't stick after reboot (and that's once again why it's unstable for some minutes, since the CPU flies to 2160 Mhz and my N7105 cannot bear it).

Anyway, it's not bad indeed, so thanks!

By the way, after wiping dalvik and cache and flashing the first kernel of yours, I was unable to boot. I did not make a single attempt, but 4 or five, so there must be something that prevents the original kernel from being functional.

It is a work day, so I cannot pull adb logs, but I could/will do it tonight or during the next days.
[Galaxy Note II N7105 Android Development] rogersb11:
Hot as hell indeed lol. That's crazy and would absolutely explain the reboot on startup issue but I don't know why it's set so high. Default cpu max is 1600. Mine starts there FOR SURE. Not sure why yours wouldn't. If someone could link me to the 7105 dn3V5 I would test it but I can't find anything but V2. I'm still single booting running SaberKat which is TW as well and hadn't had this happen to me. Initial log could be helpful. Thanks for the detailed response

Also the somehow getting stable after waiting seems to work. When I install TW I always just let the phone sit for 15 minutes after I log into Google and that seems to eliminate any issues. I have no idea why it's like that. After that initial install tho TouchWiz runs great. I fixed this issue on my rom so if you get me a link to v5 I'll look into this as well
[Galaxy Note II N7105 Android Development] lucaoldb:
The link to the rom should be this one http://electron-team.com/ROM_NOTE2LTE/ but it's not reachable atm and I don't know why.

This one is the thread, anyway http://xdaforums.com/showthread.php?t=2541860

The phone is ok if you manage to let it boot and sit for 10 minutes or even longer. But, if due to any reason you have to reboot, it is very hard to let it work again. So, in its current state, this kernel is not suitable for DN3 rom as a daily driver, since rebooting the phone is something which is often required.

I hadn't yet used adb logcat with this rom so, after seeing the device was correctly displayed when typing 'adb devices' I typed, as usual, 'adb reboot' and later on 'adb logcat > logcat.txt' but it gave me 'Unable to open log device '/dev/log/main': No such file or directory' which should mean that logcat is not enabled for this rom. I was obviously unable to pull a logcat direcly from the phone too.

Since it's a pain to let the phone boot in the current conditions, I don't know if I will spend some more time in enabling logcat, which does not look difficult (I have never done it, because it's the first time I face this issue, but this how-to does not look too complicated, since it just requires to load a kernel module, after all http://bitmote.com/index.php?post/2013/02/19/Enabling-Logcat-in-Custom-Android-Roms) but is almost impossible when the phone is so unstable. And, to be true, it is not very nice to see the cpu flying to 2160 Mhz for minutes, since the N7105 is my primary smartphone and I don't feel like turning it into french fries!

It's a pity, because this kernel seems faster than the first release, which was rock solid:)

I will test your kernel with another tw rom which is laying on my sdcard ready to be flashed and I will report what happens.

Edit: it's more or less the same with Alliance rom 4.4.2... It looks my N7105 dislikes the 3.8 kernel.......
[Galaxy Note II N7105 Android Development] rogersb11:
Ok thanks. Yea like I said it should NOT be going to 2160. 1600 default and stweaks sets it to the same thing. If it does that on boot then that's gotta be the reboot issue. I'm gonna pull the rom and install when I get a chance. I'll look into adding something to lock the boot up cpu speed as well. Like I said I'm running SaberKat which is my tw rom and I've never had that happen, ever. It is a shame, this thing has tons benefits and the newer versions are significantly improved. You said the very first release works fine without any issue? The one labeled shift dual boot kernel? This is easily the best input I've received about dn3. Thanks

Edit:well I was gonna pull it now but didn't realize it was on mega, ugh lol. I'll pull it tonight. That's crazy it doesn't have adb. Kernel enables it on flash. That's a real bummer
[Galaxy Note II N7105 Android Development] rogersb11:
I'll have something for you shortly. Biggest change between initial release and all the others (the one that don't seem to work) is overclocking. I did a massive cleanup in there and dropped the max OC to 2000. Above that is almost unable anyway so I'm thinking we should be good. Awesome bit of info about the cpu spiking man. Nobody had ever mentioned this or I could have fixed this issue long ago. I'll upload when the build is finished. I had to reconfigure stweaks with the new settings
[Galaxy Note II N7105 Android Development] rogersb11:
Ok, couple updates. Reduced wifi wakelock, dropped OC max to 2000 and added Safe Boot Speed set to 1600. Should alleviate the issue with DN3. Upload to XDA kept failing but here's 3.8.1 at AFH https://www.androidfilehost.com/?fid=95784891001616471 and I'll try to upload here again later
[Galaxy Note II N7105 Android Development] neopanther:
Got another phone shipped to me via t-mobile coming today. Ahhhhhhh.....Now is there a way to block t-mobile from seeing it's rooted? They can see it? It even shows up on the website!
[Galaxy Note II N7105 Android Development] lucaoldb:
I will try the new release this evening. Just one thing, I forgot to say that I am still on 4.1.2 bootloader, though I can't imagine why it should cause these issues. Anyway, I will try to test the kernel after a clean install of the rom, because there could be some junk around and I don't want to blame you kernel:)

Regardind the DB shift kernel (the first one) it has worked for months and still works for Dn3.
[Galaxy Note II N7105 Android Development] rogersb11:
Bootloader shouldn't matter. I know someone who's ran it on same one without issue. Right the very first one. Only difference from it and second release was OC and charge values so I'm sure this is it. Thanks, just let me know. If it still doesn't work I'll pull the rom but I'm pretty confident this issue will be gone
[Galaxy Note II N7105 Android Development] lucaoldb:
Good news, 3.8.1 looks stable for Alliance Rom which gave me the same issues as DN3 (I will test Dn3 as soon as I can, but I am sure it'll work as well).

The main difference is that Cpu does not overcome 2000 Mhz when the phone boots but, after using the phone for 9 minutes, CPU spy diplays 39 seconds at 2000 Mhz. So, when it boots, there is no limit to 1600, but 2000 Mhz is a frequency that my N7105 can easily bear. This happened after the very first boot without any setting applied with stweaks.
[Galaxy Note II N7105 Android Development] rogersb11:
Well actually during the actual boot 1600 is used WAY more this way. I need to make a couple more adjustments but I thought it'd be good. It goes over because cpu can scale all available frequencies which is helpful in other areas. I know it went over for some seconds, same here but is doing what its meant to do. I didn't completely lock it in purpose. Thanks for the feedback, your mention of the cpu allowed me to fix this. Awesome. [MENTION=1097804]sawdoctor[/MENTION] you were best with dn3 issues and I know you run it as daily driver, anyway I can get you so flash and confirm dn3 fixed. Want more than 1 confirmation before I 100% call it fixed. Thanks in advance. Kernel come long long way since you last ran. More boeffla configuration coming to stweaks and led control as well later today or tomorrow
[Galaxy Note II N7105 Android Development] lucaoldb:
DN3 - 3.8.1 release works fine

Tested DN3 too, no problem.
[Galaxy Note II N7105 Android Development] rogersb11:
Awesome. Thanks man. Still can't upload to xda. About 50 failures throughout the day. Almost switched to my afh awhile back abs wish I would have. Probably have 3.8.2 up tonight or tomorrow. FULL boeffla control in stweaks, led control support and read ahead value for internal and external instead of just the one
[Galaxy Note II N7105 Android Development] rogersb11:
Doesn't matter since new is working now and is obviously a better option but original kernel wouldn't boot because starting with 3.1 I updated and included the new Mali drivers so going back stock or to a kernel without the mali update (I think we all have it) you have to durty flash the rom. I'm going to make a zip with just the old blobs to eliminate having to flash the whole rom again
[Galaxy Note II N7105 Android Development] :
Sorry I'm on the n4 atm but still have my n2. I'll test it with alliance first as I've been helping them with thier n7105 release and then test it with dn3 for you
[Galaxy Note II N7105 Android Development] DerTeufel1980:
Hey, if you are in testing moods, here's my android 5.0 rom:

http://xdaforums.com/showthread.php?t=2954876
[Galaxy Note II N7105 Android Development] :
Np will download and test now

---------- Post added at 11:55 AM ---------- Previous post was at 11:31 AM ----------

Flashed latest kernel on both alliance and dn3. Both booted up but with alliance every time I open an app phone reboots with dn3 every time I open an app phone switches off and have to pull battery. Bit pushed for time atm but I'll test again later pull some logs and see if I can see what's going on. With dn3 could well be left over files from agni. I know both dn3 and alliance run a kernel script to fix root don't think that's anything to do with it though
[Galaxy Note II N7105 Android Development] rogersb11:
That's 3.8.1 from afh? XDA woukdnt let me upload all day
[Galaxy Note II N7105 Android Development] rogersb11:
I'm pulling now. This nameless? I made the changes to everything but smdk4412 common tree to build cm12. Plan to start a build after dinner today but I'm pulling this now to flash a secondary

I've got my kernel with new mali amd se disabled so I'll use them together. I haven't formatted to f2fs again yet so I'll just try single boot
[Galaxy Note II N7105 Android Development] DerTeufel1980:
It doesn't boot currently. Maybe I didn't disable selinux in kernel...

For gps.h (needed to fix build), you need to look at d2-common or jf

I took it from d2, sbrissen said to me he updated gps from jf
[Galaxy Note II N7105 Android Development] :
Sorry didn't see 3.8.1 I installed 3.8 from xda, not really been following the n2 too much. I'll download 3.8.1 when I get in
[Galaxy Note II N7105 Android Development] rogersb11:
Yea XDA wouldn't let me upload yesterday so 3.8.1 is on my AFH. Someone had it working on both of the ROMs you were talking about, just trying to confirm
[Galaxy Note II N7105 Android Development] rogersb11:
If you get the 5.0 ramdisk I can try to boot it with my kernel. I built a cm12 one last night with newest Mali and Se disabled. I was gonna build before I left but I still have to pull the sli repo and make the gps changes as you mentioned
[Galaxy Note II N7105 Android Development] neopanther:
I gotta tell you. You were right. Sigh....It was just the battery. Bought a new one and it stopped immediately. Stupid stupid stupid of me. Always start simple and branch out, right? So I got a replacement that came in from T-mobile. I'm sending it back asap, but I'm going to use the old one to test the new kernel and stuff. Might as well. Can't believe this. Your help has been deeply appreciate. So I'll get back to you after seeing what happens.
[Galaxy Note II N7105 Android Development] rogersb11:
Lmao. I figured man. Make sure to pull 3.8.1 from a few posts back. Xda STILL won't let me upload. At least 100 attempts. Uncool lol. Glad you're in business tho. I knew it was device related
[Galaxy Note II N7105 Android Development] neopanther:
So I have another much easier question if you don't mind. I'm having a bit of trouble figuring out how to set up tethering with the rom. I know how to make it work on stock using wifi tether router. The name I chose shows up but refuses to connect then disappears. When I downloaded Dn3 before the stock tethering app worked without registering with t-mobile. I did it this time and it showed up. Also two APN's were listed this time. There was only one before. It seems like it updated itself somehow and had another APN there. So basically I'm trying to figure out if that was made to allow a tethering alternative to the regular APN. Any advice will be appreciated again. At least this time it's not something stupid!:eek:

---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------

...and I also saw you mention having trouble uploading the new 3.8.1. I'll check it out.
[Galaxy Note II N7105 Android Development] :
Confused me for a minute, the last 2 uploads were 3.8.1 lol. Just tested the last one, not tried dualboot but works fine. Very smooth and great to see you finally nailed stweaks , stweaks is a PIA?
[Galaxy Note II N7105 Android Development] neopanther:
...and I also saw you mention having trouble uploading the new 3.8.1. I'll check it out.
[Galaxy Note II N7105 Android Development] rogersb11:
If it's on dn3 you'll have to ask in their thread. I don't have any experience with the rom that would be helpful. When I tether I use my aosp rom because it's simple but I dual boot so it's easy to just switch over. Tethering on TW requires more work. I'm sure in dn3 thread the know exactly what to do tho
[Galaxy Note II N7105 Android Development] rogersb11:
Sweet. Yea it was not easy. Somethings are simple with it but others not so much. I have new stweaks build with FULL boeffla control that I'll upload probably tonight. I still need to add led notification control before I do but kernel abs stweaks is massively improved from when kernel actually worked on dn3. Can't believe it was just a cpu issue. I could have fixed that easily lol. Oh well. Glad I added safe boot now anyway. It's useful
[Galaxy Note II N7105 Android Development] rob_z11:
So following last few pages, I don't know if devils 5.0 and kernel 3.8.1 boots up or not? I can try..
[Galaxy Note II N7105 Android Development] rogersb11:
He got nameless running? 3.8.1 will NOT run lollipop BUT I do have a lollipop kernel when the system is ready
[Galaxy Note II N7105 Android Development] rob_z11:
I don't think he has. He found few problems and fix few from his post, and have not posted any update to Version 3. I wonder if you were able to his nameless version 3 with your new kernel?

This is the thread in which he has mentioned you.

http://xdaforums.com/showthread.php?t=2954876