Database Develop

21/09/2010 [Xperia X1][FroyoRedux-Port][CM6][Testers needed][Neopeek]

http://www.neopeek.com/en/forum/14-Android-ROMs/364-Xperia-X1FroyoRedux-PortCM6
check this neopeek testers need again....

Installing as I type! Can't wait the original kernel to get the battery related patches!

I am having a wired problem - after a while on standby, upon waking up the phone, it freezes. Clock doesn't advance and phone does not respond on buttons/slider. So I do a soft-reset after which in winmo I get a message sdcard is not formatted, do I want to format it. and indeed file system is damaged. And this happens for a second time in a row now! I havent had problems like that with other distributions, at least ones that require ext2 partition. Anyone have advice?
Sent from my Milestone using XDA App

well, i cant charge

So far, it's perfect. Two issues that need to be resolved before I use it permanently is the charging and the battery drain.
Getting really close!

So far, it's perfect. Two issues that need to be resolved before I use it permanently is the charging and the battery drain.
Getting really close!
Click to expand...
Click to collapse
Ok so far so good! BUT: Would you provide us a lil bit of more info!
Which kernel did you use? Included one (=21/8) or that from SuperFroyo??

vatoloco said:
Ok so far so good! BUT: Would you provide us a lil bit of more info!
Which kernel did you use? Included one (=21/8) or that from SuperFroyo??
Click to expand...
Click to collapse
Sorry, was in a bit of a rush
Working: Marketplace, WiFi, GPS, battery meter, sound, messaging, gmail app, browser, ( bluetooth, I think )
Not: Camera, charging, power management
Used: Only the included files, nothing more.

May anyone please test this kernel?
Test-Kernel
I am awaiting your feedback

Hey guys, my Galaxy S should arrive tomorrow.
@all Developers:
Thank you very much for the good work, keep it up
@the rest:
I wish you good luck, that you can enjoy android on your X1 as i will do it on my new phone.
Maybe i'll look back in here from time to time, to see the progress.
Best regards from germany
See ya!

report?
Total performance is smooth
My location , Wi-Fi, Market , Battery Meter , GMail, Sound, Music is working
other function. i didn't use it.
Overall performance is good, but Force Close dialog is too much show..... when i try to do anything. there's a delay (about 5~10sec?)

All of you guys should really post which kernel you are using. It will be very helpful for the developers!
I am downloading at the moment, will try the kernels and post the results
Original kernel + points about FroyoRedux:
- Charging works (I had it plugged when I launched Android, actually does increase WM battery percentage, too)
- Battery meter shows too much, but I think it will calibrate itself if I finish charging
- Speaker bug is there, headphone plug and unplug fixes that
- A bit faster than CyanogenMod6 with Tremere's kernel
- Nice theme
- Mass storage does not work (should I install a driver or something?)
- Sometimes stops responding to any other key than the top power button = home
- 3D does not work
- Sound and calling work fine, cannot adjust in-call volume (possibly due to the keys not working, but I had this problem with CM6+Trem too)
- Pretty much every app works, YOUTUBE TOO (lags a bit, but works)!
New testkernel:
- Phone reboots when first screen of android comes up
- I just replaced files, it crashed at lockscreen
- Ran a new installation, it crashed at black android system (title) -window
SuperFroyo kernel:
- Fastest one, menu scrolling is pretty nice with this kernel
- 3D does not work, Neocore crashes
- Sound works
- Youtube works, and lags less than with original kernel
- Charging does not work, battery meter shows what comes to it's mind

vatoloco said:
May anyone please test this kernel?
Test-Kernel
I am awaiting your feedback
Click to expand...
Click to collapse
Tried copy/paste of those two files straight into root of SD-card (can only guess as it's not written anywhere). Phone reboots as soon as it comes to PIN-code page. Tried to restart a couple of times but nope.
Tried the SuperFroyo-kernel as well. Much faster in comparison to kernel from tremere's build 21/8.
Else, nothing more to add other then lkoljo wrote.
Big thx!

tried this kernel
xperia-xdandroid-kernel-20100922
Sound didn't work??

I'm useing the test kernel now, and it booted up without any problems
Gonna test Battery life for 2 hours, then switch back to vm to see if it gives good result's

Did you use the test-kernel from scratch. I mean when first booting up? or did you try first included kernel then after booting up you replaced kernel? I ask this because it's just not clear for me: You say it works w/o hassle and others report that they can't even get into the Launcher or that they have a black screen. I am just confused now

I did first use Tremere's Kernel with your build, and then i just copied the test kernel start from vm and booted it up. It's fast and stable it seems, i did use Android in standby mode for one and half hour. Well i did look around in system meny and such tried calling it but no signal just vibrate wich i did turn on. Battery used in android is 20% from fully charged 100% Switch back to vm says 78% so the meter seems almost correct. Tried original charger but it didn't work, Then tried pc usb charging and it seems to work Gonna try Xdandroid's new kernel now released today. Will get back to you tomorrow
I have now tested the new Xdandroid kernel released 23/9/10 for one and half hour now, switched back to vm and guess what?
i had 100% when i started android, used it for one and a half hour and then i switched back to vm it had only used 9% battery
Thats the best result i ever had using android, so hey if only sound/ mic problem gets fixed then this would be great
Grab the new kernel from thier Xdandroid wiki

I have tested 21/09/2010 [Xperia X1][FroyoRedux-Port][CM6] with the latest kernel from xdandroid (23/9/10) and it works very well, stable and fast. And the battery is a big improvment!!
I also overclocked it to 640mhz and the UI is then superfast.
Keep up the good work

winkgw said:
I have tested 21/09/2010 [Xperia X1][FroyoRedux-Port][CM6] with the latest kernel from xdandroid (23/9/10) and it works very well, stable and fast. And the battery is a big improvment!!
I also overclocked it to 640mhz and the UI is then superfast.
Keep up the good work
Click to expand...
Click to collapse
you use zimage to?

FYI: In the next days there will be heavy updates regarding some of my builds. Fixed almost everything I could! Just trying out today some of the kernels released lately and then I think we will have a really really good CM6-Ports ready for all of you! Everything that's working in XDAndroid "Final" should then also work for us! So maybe I will call my builds "Pre-Final". Another thing that I should mention is that user ferlanero from xda-devs has today shipped over his X1 from Spain to Germany (my location). Once I receive it I will be going to try some NAND-related stuff!
X1 from user sequester will be my porting-device to test ports and latest nightlies from Cyanogen
X1 from user ferlanero will be my nand-test-device
Be prepared to get the proposed updates (see above) on this weekend. Again speical thanx to sequester and ferlanero for supporting me! This really motivates me in doing all this stuff!

Yes zimage to at lest i did

TP CM9 changelog and known issues?

Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.

StoneRyno said:
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
Click to expand...
Click to collapse
Known issues are basically the camera and mic don't work, some folks have wifi issues and some don't... and some have issues with the audio acting up when waking from sleep... I myself am happy to say I don't have wifi or audio issues... but camera and mic are driver issues that may never get to work. All in all very stable though
Sent from my cm_tenderloin using Tapatalk 2

If camera and mic are the only problems then I see no reason not to give it a shot. I don't know if I would ever use them.I was concerned that it was missing core functionality making it something one wouldn't use as a daily OS and only switch over to it for test scenarios and then switch back. I have cm9 on my Samsung epic (the one with hw kb). Would the current latest nightly be the one to go with?

Just curious, why are the camera and mic drivers so difficult? I would have thought having them running on WebOS was at least some of the work. I guess porting said work to Android is a completely different ballgame.

I wonder if the wifi/audio issues are still being worked on tho? Or are those of us with those stuck with em forever?

The big thing for me was hardware video decoding. Alpha 1 fixed that for YouTube, and alpha 2 finished the fix for Netflix and others.
If you haven't already, check out the thread at rootzwiki.
I was using webOS by choice until CM9 came out. I switched to CM9, and have been using it as my daily driver since the very first Alpha. I never video chat, but if I wanted to I know I can just boot webOS.
Don't let people here tell you CM9 (or the Kangs thereof) are unstable. Some people continue to spew that we don't have a stable version of android purely because its called an alpha. I don't think it will graduate past alpha without camera/mic support, and that may never happen. Right now, without trying, I am sitting at 587 hours of up time on my TouchPad. I can't think of a better word to use than "stable."
Sent from my Galaxy S II (i777)

Known Issues that I can think of. I know some were mentioned above, but all in one place is good.
Broken, NO FIX:
1) No Microphone
2) No Camera
Partial Workarounds:
1) Audio gets noisy with screen off. Kinda workaround: Turn volume down, only happens at higher volume levels. Or set screen timeout longer/always on while playing audio. No complete fix.
2) Wi-Fi dies or doesn't reconnect. Some people never have a problem, others do. Workarounds: First, set WiFi to always on so it doesn't turn off with the screen. Second, try changing the channel on your router, or if you have 2.4ghz/5ghz switchable, try using the other. If Wi-Fi still dies, toggle it off and back on.
3) Some people report that if the TouchPad fully discharges to 0% they have trouble getting Android to charge properly. Others report that if you reboot the device with it plugged in, sometimes it won't charge. I've experienced neither problem, but the best advice is, charge before the device shuts off fully, and unplug the charger/usb while booting.
Broken, but Completely Fixable:
1) Random crashes. Install CPU Master and raise minimum CPU speed to 384 or 416 depending on which works for you, and crashes go away. Also, don't overclock too much.
Setup Issues:
1) DPI is at 160dpi stock. This works for most things, except a few tablet apps and games will not work properly. Setting DPI to 120dpi fixes everything, but the display quality is not ideal. 132dpi is ideal, but breaks the market after a day or two. Most people use 160dpi or 120dpi.
2) The default launcher, Trebuchet, is NOT compatible with the 4:3 aspect ratio of the TouchPad's screen if you use any DPI other than 160. Why something so easily fixable has not been fixed escapes me, but you will quickly find you need a new launcher. Go Launcher HD is one of a few that are very friendly to the TouchPad.
App Issues (not really issues but you probably want to know)
1) A few apps really, really, really are picky about the screen size and just won't scale right. (see Trebuchet notes above). One example is Politico HD - it forces 16:9 aspect ratio and thus gets cut off. Some apps simply refuse to run. Contacting the developers rarely works. This is probably less than 1% of the apps on the market, however.
2) Some developers simply are too strict on app compatibility on the market, and whitelist only select devices. Getting compatibility from these guys is a longshot. Best option is to install on another device, grab the APK or use Titanium Backup to move the app to the TouchPad.
3) Some games (notably Gameloft is the worst) enforce device compatibility checks within the program itself and it will refuse to run unless you masquerade as an approved device by hacking your build.prop... which is not normally recommended.
Did I miss anything anyone?

[Q] [WANTED]: Dev Assistance with Captivate Sleep-lock/Charge-lock

I am posting here because I haven't made the requisite 10 posts to get access to post to the development forum. Is there a developer that would be willing to help me here?
Wanted:
Dev assistance with a persistent sleep-lock and/or full-charge lock issue experienced with nearly all non-stock roms on a Samsung i897 with a fresh flash of CM 10. (CM 10 is not the relevant detail, this issue has happened with every non-stock-based rom based on anything newer than and including GB. (so GB/ICS/JB suffer this issue)
What are we calling sleep-lock?
Sleep-lock in this case is being defined as a spontaneous shutdown, lockup (requiring removal of battery to restart), or spontaneous restart of the Android OS. I understand that these three results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to be randomly happening when the phone is in a sleeping state.
What are we calling full-charge lock?
Full-Charge lock in this case is being defined as a spontaneous shutdown or lockup (requiring removal of battery to restart; I do not seem to suffer spontaneous restarts while on the charger). I understand that these two results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to all happen when the device is on the charger, but most often when the phone reaches or is near a full charge.
Troubleshooting done to date:
I have tried various ROMs over a long period of time, some were better than others, but they were all victims of this behavior. It doesn't seem to be device-specific (read as hardware) related but ever since DarkyRom that I tried shortly after I got this device a couple years ago, I have had this behavior. Stock ROMs do not suffer this behavior.
Who are you working with?
I am a Sr. Technical Team Leader for a Fortune 1000 VoIP software company and am well versed in troubleshooting methodology. I am somewhat newbish in the ways of logcat so I would ask for a little patience there, but am well versed in Windows, Linux, and many parts of the Android OS and flashing process including Odin, Hiem. and CWM. I'm seeking developer assistance because I am completely inept at code development.
The device that we're working with is a non-production (not relied upon for daily use) and I have no problem leaving it running with a logcat on it, or flashing any ROM you would ask for troubleshooting purposes. That said, the goal is to get the stable CM10 running without reboots or lockups.
Thank you in advance for your time and assistance.
--ChipSharp(DotCom)

chipsharpdotcom said:
I am posting here because I haven't made the requisite 10 posts to get access to post to the development forum. Is there a developer that would be willing to help me here?
Wanted:
Dev assistance with a persistent sleep-lock and/or full-charge lock issue experienced with nearly all non-stock roms on a Samsung i897 with a fresh flash of CM 10. (CM 10 is not the relevant detail, this issue has happened with every non-stock-based rom based on anything newer than and including GB. (so GB/ICS/JB suffer this issue)
What are we calling sleep-lock?
Sleep-lock in this case is being defined as a spontaneous shutdown, lockup (requiring removal of battery to restart), or spontaneous restart of the Android OS. I understand that these three results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to be randomly happening when the phone is in a sleeping state.
What are we calling full-charge lock?
Full-Charge lock in this case is being defined as a spontaneous shutdown or lockup (requiring removal of battery to restart; I do not seem to suffer spontaneous restarts while on the charger). I understand that these two results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to all happen when the device is on the charger, but most often when the phone reaches or is near a full charge.
Troubleshooting done to date:
I have tried various ROMs over a long period of time, some were better than others, but they were all victims of this behavior. It doesn't seem to be device-specific (read as hardware) related but ever since DarkyRom that I tried shortly after I got this device a couple years ago, I have had this behavior. Stock ROMs do not suffer this behavior.
Who are you working with?
I am a Sr. Technical Team Leader for a Fortune 1000 VoIP software company and am well versed in troubleshooting methodology. I am somewhat newbish in the ways of logcat so I would ask for a little patience there, but am well versed in Windows, Linux, and many parts of the Android OS and flashing process including Odin, Hiem. and CWM. I'm seeking developer assistance because I am completely inept at code development.
The device that we're working with is a non-production (not relied upon for daily use) and I have no problem leaving it running with a logcat on it, or flashing any ROM you would ask for troubleshooting purposes. That said, the goal is to get the stable CM10 running without reboots or lockups.
Thank you in advance for your time and assistance.
--ChipSharp(DotCom)
Click to expand...
Click to collapse
There are many things that can cause what we call SoD (sleep of death). First off, if you have deep idle checked on, remove that (in your ROM options).
What are the changes/mods you made after flashing CM10 (assuming stable version)?
Do you OC/UV?
And finaly, after checking for those things, there's a possible fix. It seems to have work on those who don't have a hardware issue, flashing I9000 bootloaders. The link in my sig guides you through it for the I897. (I9000 being the international version of the captivate)
If you end up going that route, I would do a clean flash. So flash stock software (KK4 no BLs) through Odin or Heimdall, flash the BLs, flash corn kernel to get root and finally flash CM10.
There are no real fix if it's a hardware issue that I'm aware of but hopefully it isn't. Also, I know you want to run CM10 on it but some people reported that running Mosaic 9 fixed their SoD problem. (It is the last I9000 ported ROM)

BWolf56 said:
There are many things that can cause what we call SoD (sleep of death). First off, if you have deep idle checked on, remove that (in your ROM options).
What are the changes/mods you made after flashing CM10 (assuming stable version)?
Do you OC/UV?
And finaly, after checking for those things, there's a possible fix. It seems to have work on those who don't have a hardware issue, flashing I9000 bootloaders. The link in my sig guides you through it for the I897. (I9000 being the international version of the captivate)
If you end up going that route, I would do a clean flash. So flash stock software (KK4 no BLs) through Odin or Heimdall, flash the BLs, flash corn kernel to get root and finally flash CM10.
There are no real fix if it's a hardware issue that I'm aware of but hopefully it isn't. Also, I know you want to run CM10 on it but some people reported that running Mosaic 9 fixed their SoD problem. (It is the last I9000 ported ROM)
Click to expand...
Click to collapse
Thanks for this information. I have read most of this information before, but I appreciate the info nonetheless.
Post install I don't do any customization in terms of OC/UV. So I'm fairly certain that's not it.
I'll run through what you've suggested here in order and see what I get. The specific order is the part that I've found unique. It may take a couple days to get back to you as my test cases involve a couple of charges/discharges, some "normal use" cases etc. I'll let you know my results.
Thank you again for your willingness to help. I'd like to maintain the usefullness of this device and I appreciate your assistance to that end.
--ChipSharp(DotCom)

chipsharpdotcom said:
Thanks for this information. I have read most of this information before, but I appreciate the info nonetheless.
Post install I don't do any customization in terms of OC/UV. So I'm fairly certain that's not it.
I'll run through what you've suggested here in order and see what I get. The specific order is the part that I've found unique. It may take a couple days to get back to you as my test cases involve a couple of charges/discharges, some "normal use" cases etc. I'll let you know my results.
Thank you again for your willingness to help. I'd like to maintain the usefullness of this device and I appreciate your assistance to that end.
--ChipSharp(DotCom)
Click to expand...
Click to collapse
If you tried the other stuff and the I9000 bootloaders don't work, chances are that it's a hardware problem.

BWolf56 said:
If you tried the other stuff and the I9000 bootloaders don't work, chances are that it's a hardware problem.
Click to expand...
Click to collapse
I'm going to give it a try right now....I'm less inclined to buy into the hardware theory though without having these problems on the Stock ROM.

chipsharpdotcom said:
I'm going to give it a try right now....I'm less inclined to buy into the hardware theory though without having these problems on the Stock ROM.
Click to expand...
Click to collapse
Try upping the voltage/minimum clock speed. That worked for me when I was running cm9 with the glitch kernel.
Sent from my Apple IIe

billyjed said:
Try upping the voltage/minimum clock speed. That worked for me when I was running cm9 with the glitch kernel.
Sent from my Apple IIe
Click to expand...
Click to collapse
Thanks for the tip...I'll try that if all of the above doesn't work. At this point, I'm all flashed up and running test cases.

So none of the suggestions here (unfortunately) provided me any different results. That said, I have discovered a couple of different variables that may play a part in this.
1.) This issue only seems to come up when I have the device plugged into power only, not when I have it plugged into a computer.
2.) I think this may be related to trying to sleep while still maintaining the clock application. It seems that when I see this most often, it is when I am plugged into the wall, and I have an alarm set. I was able to be plugged into the wall overnight last week and have no problems without the alarm set, but when I set the alarm, I had the sleep-lock issue (and moreover as you would expect, my alarm did not sound).
Again, I have none of these problems with the stock ROM. I'm going to continue to test on this and hack around on it to see if I can hunt this down, but my concern is that the very things that allow me to troubleshoot are the same things that keep the device from reproducing the error.
You can subscribe to this thread if you care to continue watching the progress, or if you have any similar experiences or potential solutions, but this is one of those issues that if I don't find the root cause, it's going to drive me bat-s%#$-f&@!#%-crazy. I'm aware that even if I get to the root cause I will likely never see a fix for the problem being that this device is so old, but this is caught in my teeth now, and I'm going to have a hard time letting it go.
As always thank you all for your assistance and participation.

chipsharpdotcom said:
So none of the suggestions here (unfortunately) provided me any different results. That said, I have discovered a couple of different variables that may play a part in this.
1.) This issue only seems to come up when I have the device plugged into power only, not when I have it plugged into a computer.
2.) I think this may be related to trying to sleep while still maintaining the clock application. It seems that when I see this most often, it is when I am plugged into the wall, and I have an alarm set. I was able to be plugged into the wall overnight last week and have no problems without the alarm set, but when I set the alarm, I had the sleep-lock issue (and moreover as you would expect, my alarm did not sound).
Again, I have none of these problems with the stock ROM. I'm going to continue to test on this and hack around on it to see if I can hunt this down, but my concern is that the very things that allow me to troubleshoot are the same things that keep the device from reproducing the error.
You can subscribe to this thread if you care to continue watching the progress, or if you have any similar experiences or potential solutions, but this is one of those issues that if I don't find the root cause, it's going to drive me bat-s%#$-f&@!#%-crazy. I'm aware that even if I get to the root cause I will likely never see a fix for the problem being that this device is so old, but this is caught in my teeth now, and I'm going to have a hard time letting it go.
As always thank you all for your assistance and participation.
Click to expand...
Click to collapse
Have you tried it with a different clock app? I mean, if I understand this correctly, it seems to be narrowed down to your current clock apk, which is different than the stock GB one. So I would suggest freezing (or unistalling) your current one with Tibu and trying a different one.

That's actually my next step.
I'm not sure it's accurate to say that I have it narrowed down to the clock app, I simply noted that I reproduced the issue on wall power and with the alarm set. That could all be coincidence. I need to try to reproduce those scenarios more reliably and in a more controlled method.
Do you know of an app I could install that would cause my battery to discharge fairly quickly? It would speed up my troubleshooting.

chipsharpdotcom said:
That's actually my next step.
I'm not sure it's accurate to say that I have it narrowed down to the clock app, I simply noted that I reproduced the issue on wall power and with the alarm set. That could all be coincidence. I need to try to reproduce those scenarios more reliably and in a more controlled method.
Do you know of an app I could install that would cause my battery to discharge fairly quickly? It would speed up my troubleshooting.
Click to expand...
Click to collapse
Haha first time I ever get that question but leaving your camera on should do the job (or video playing)

[Q] Bugs, bugs, bugs

Dear all,
it is my first try to run cyanogenmod (10.1 Rel 7) on my SGS+. But when using it, I immediately found plenty of issues:
- Navigation is only partially working. After a while the maps starts jumping around and dark semi transparent overlay sections appear so that one cannot see the full map. In the forum I found the hint to deactivate Dithering. Done. Only little improvement.
- Alarm clock is not working when the phone is turned off.
- Screen goes off after dialing a number (workaround: lift phone to the ear and lower it back down -> screen is on again).
- No FM radio app (in comparison to the stock rom).
- Skype video is still upside down (as with stock rom).
My colleagues were very enthusiastic about cyanogen mod. In contrast, I haven't really detected the advantages. Are the developpers still working on the issues? Is there anything I can do to support you guys?

To answer your queries:
-Navigation- use the bug reporting method on the CM10.1 forums and submit it as a bug report either in the S CM10.1 thread or on JIRA. More details are given in the CM10.1 thread OP.
-This feature doesn't work even on stock. Its not a bug, and its not just CM10.1. MIUI allows this apparently however.
-This is normal, not a bug either. When you call someone the screen goes off because you're going to lift it to your ear anyway. The 'workaround' is actually the proximity sensor, and a similar thing happens on stock roms. The only solution to this is to press a button when the screen initially turns off.
-FM Radio isn't included in CM builds by default, as the API needed for it needs some intense changes made to it. There's Spirit FM if you want to run the risk. Check out the thread for more information.
-Skype on CM10.x is a known issue
Try CM10.2 and see if that helps the first issue, if not, report it using the methods in the CM threads. Otherwise everything else is as normal/known.
Sent from my GT-P7510 using Tapatalk HD

Irrespective of a few bugs there are definitely a number of advantages to using CM.
Have you noticed how smooth CM10.1 is? For me it's smoother than stock. Definitely a plus.
The pre-installed applications are more polished/work better and you actually have control over them. Don't like one? You can remove it. Unlike stock where you are stuck with a lot of junk (unless you have rooted your phone).
Bugfixes! We're no longer stuck with a 2 year old version of an OS for which we don't receive any bugfixes.
Customizability. CM gives you a lot more features to have your phone just the way you want it.
Overclocking and undervolting.
Not everyone had this problem, but my phone took > 5 minutes to get a GPS fix on stock. It takes < 10 seconds on CM.
And that's just what I came up with in a few minutes. Yes, there will be a few bugs and features which you think are weird (like the screen turning off when you make a call) but you'll find that on any piece of software. If you personally feel CM is a downgrade then it's your right to think so and go back to stock ROM. That doesn't mean the average xda-user is going to agree with you though.
(I think there are also a few ROMs based on the stock 2.3.6 versions, but since I've never used them I wouldn't know which ones are worth trying.)

[Kernels] N4N-2DQI6/I5-[12-19-17]710,715,810,815,817

N4N (Neked 4 Nougat) I6/I5 Kernel for 710,715,810,815,817​There's just nothing like good ol' stock. Everything just works. Even after 2 years they're still selling these Tabs. And they can still compete with newer ones. So on with the show!!!!
You flash this at your own risk. I'm am not responsible for anything that happens!!! There's the discaimer.
MAKE A FULL BACKUP IN TWRP!!!!!
These kernels modify your ROM. So you WILL NOT be able to FLASH/RESTORE the stock kernel only.
A kernel tuner (Synapse) is enabled for V2.0 only - Get Synapse from the Playstore
See post #2 for Synapse info and other stuffs​
Install instructions:
You MUST HAVE TWRP installed to flash this!!
MAKE A FULL BACKUP IN TWRP!!!!! YOU HAVE BEEN WARNED!!!!!!!!!
Flash Kernel- it'll wipe cache, dalvic automatically,
Flash SU v2.82, https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Wipe cache and dalvic when SU asks,
Reboot
Profit!!
So whats in this thing?!
V2.0 Synapse enabled (You should use a tuner (Synapse recommended) for this one as that's all that was added) But will run fine without
All below plus
Under volting
Overclock-big 2.2Ghz LITTLE 1.6Ghz
Underclock-big 500Mhz LITTLE 200Mhz
HMP tweaks and tunables
KSM with tweaks
Enabled all stock govs
V1.3 All below plus
Patched to 108EOL
V1.2 All below plus - Pulled for random issues-Use V1, V1.1 or V1.3
Patched to 3.10.105
817 only has this version
V1.1 All below plus
Patched to 3.10.61
V1
4.9 UBERTC Toolchain
Screen Mirroring built in - Seems to only works with Samsung enabled TV's
CIFS
OTG
TCP's-Cubic is default. Reno, Westwood+ and HTCP added
CDROM support
XPAD game controller support
A few tweaks
Bugs
If you have Synapse installed , make all settings to stock and uninstall. It'll probably still give you a "System UI error". Just move on, and reboot after a couple minutes.
Source
https://github.com/engine95
Thanks to
@andyroidking - for the 715,815, and 810 boot.img's
Donations. Never expected, but much appreciated
@sebmue
@andyroidking
Downloads
V2.0 Synapse enabled and recommended
710-I6 - https://www.androidfilehost.com/?fid=673791459329065685
810-I6 - https://www.androidfilehost.com/?fid=962021903579496837
715-I6 - https://www.androidfilehost.com/?fid=745849072291693169
815-I5 - https://www.androidfilehost.com/?fid=889964283620770516
817-3CQE4 - https://www.androidfilehost.com/?fid=962021903579499361
V1.3
710-I6 - https://www.androidfilehost.com/?fid=889964283620768631
810-I6 - https://www.androidfilehost.com/?fid=745849072291691184
715-I6 - https://www.androidfilehost.com/?fid=962021903579494937
815-I5 - https://www.androidfilehost.com/?fid=962021903579494940
817-3CQE4 - https://www.androidfilehost.com/?fid=889964283620772774
V1.2 Only for 817
817-3CQE4 - https://www.androidfilehost.com/?fid=745849072291694892
V1.1
710-I6 - https://www.androidfilehost.com/?fid=962021903579492239
810-I6 - https://www.androidfilehost.com/?fid=745849072291688529
715-I6 - https://www.androidfilehost.com/?fid=817906626617946405
815-I5 - https://www.androidfilehost.com/?fid=889964283620765858
817w-3CQE4 - https://www.androidfilehost.com/?fid=673791459329067028
V1
710-I6 - https://www.androidfilehost.com/?fid=889964283620763792
810-I6 - https://www.androidfilehost.com/?fid=817906626617944296
715-I6 - https://www.androidfilehost.com/?fid=745849072291686448
815-I5 - https://www.androidfilehost.com/?fid=889964283620763794
I'm just not a fan of the DevDB format anymore. It's difficult to update and modify. So this is what you get.

SYNAPSE Kernel Tuner - Maybe some others stuffs too.....​
Well, because Synapse is built in now, here's some needed info on it:
Synapse is an awesome and custom built kernel tuner. It can do so much more than a lot of other tuners. And because we have Exynos processors, it's about the only one we can use. But it can create a lot of problems getting to work. Hence this post. :silly:
I decided to make this built in instead of a flashable add on. It's actually easier and less invasive to do it this way.
UCI, is what Synapse uses to work. It's built into the ramdisk. I've added a lot of tunables and may add more later.
Now for the fixes and problems you WILL run into:
If you have issues, make sure to check out these threads. As they will probably have better info about Synapse issues. https://forum.xda-developers.com/showthread.php?t=2736986 and https://forum.xda-developers.com/showthread.php?t=3558888
No UCI support detected These are the famous words you WILL run into.
When will this show up?
When Synapse is first installed
On reboot
When you've pushed your Tablet too far
The fixes:
On first install from the Playstore. You will need to go to Settings>Apps>Synapse>Storage. Then select "Clear Cache", THEN "Clear Data. In that order!!
You may have to backout to Settings and do it one or two more times. You want the numbers for cache and data at "0".
On reboot: This usually works unless you've messed up the settings or flash another kernel
On reboot select "Menu" and "Close all".
Open Synapse and hit "CANCEL" to have your last settings applied. (I know it's not normal but it works)
Close synapse, and reopen it to make sure of settings. (If "apply or cancel" don't show up at the top, you're good to go.)
Worst case scenario:
You will need to go to Settings>Apps>Synapse. Select "Force stop". Select "Storage". Then select "Clear Cache", THEN "Clear Data. In that order!!
You may have to backout to Settings and do it one or two more times. You want the numbers for cache and data at "0".
If you follow the above, Synapse will work. It hasn't failed me in over 50 tests, probably more. :silly:

810 good to go. Have to wait til later this week to try mirroring, gave my daughter my sammy tv..
Edit: confirmation #5H0834012J5874316 - Thanks for your hard work!

andyroidking said:
810 good to go. Have to wait til later this week to try mirroring, gave my daughter my sammy tv..
Edit: confirmation #5H0834012J5874316 - Thanks for your hard work!
Click to expand...
Click to collapse
Thank you for the donation!
Hopefully the 810 looks better on the screen. The 710 is a weird screen size and doesn't fill it. But it still comes in handy.
My "Neked Maker Rom" has it built into the build.prop. But i found I could add it to the kernel. It'll still work with both installed, which I have.

engine95 said:
Thank you for the donation!
Hopefully the 810 looks better on the screen. The 710 is a weird screen size and doesn't fill it. But it still comes in handy.
My "Neked Maker Rom" has it built into the build.prop. But i found I could add it to the kernel. It'll still work with both installed, which I have.
Click to expand...
Click to collapse
I posted a couple days ago but apparently it didn't send. Screen is fine! Everything seems good. It is charging good again too, probably not kernel related but take the credit will ya...

andyroidking said:
I posted a couple days ago but apparently it didn't send. Screen is fine! Everything seems good. It is charging good again too, probably not kernel related but take the credit will ya...
Click to expand...
Click to collapse
Ok.
I'm wondering if it is Synapse with the battery. Guess we'll see.
Haven't spent a lot of time with the kernels lately. Trying some different things, but keep coming back to what I've had in the past.
EX kernel managers builder was interviewed on XDA recently. flar2 . Had some interesting things to say about SELinux. Guess that might be why his tuner doesn't have an option for permissive. Just food for thought for us all.

engine95 said:
Ok.
I'm wondering if it is Synapse with the battery. Guess we'll see.
Haven't spent a lot of time with the kernels lately. Trying some different things, but keep coming back to what I've had in the past.
EX kernel managers builder was interviewed on XDA recently. flar2 . Had some interesting things to say about SELinux. Guess that might be why his tuner doesn't have an option for permissive. Just food for thought for us all.
Click to expand...
Click to collapse
I'll read through that later... his kernel is what I use on my nexus9. His dev app is pretty good too, playstore- DevCheck Hardware and System Info. Smart guy.

Just a little update
I have the 710 and 810 kernels done. I should get 715 and 815 shortly. Then I'll get them uploaded
Just patched to 3.10.61. No additions til I get them as far as I can.
The kernel is EOL at 3.10.108

V1.1 for all 4 is in OP Just patched to 3.10.61
I've changed the way I'm doing it so it's faster. And it's easier for others to track.
I'm hoping to get all the way to 3.10.108 for the next version. Then the addons.
We shall see. :fingers-crossed:

Thank you ! Amazing and smooth as expected ??

810 v1.1 A-Okay

V1.2 is in OP!!!!! Just patched to 3.10.105, which is Feb 2017
Not quite sure if I'll go to 108, or do some addons. I'm kinda burned out on the patches.
More than likely I'll patch to 108, but I am dreading it as just the 3 more patches has over 750 fixes.
And seeing as how our Tablets AND our Kernel is at EOL, I might as well finish it out.
Regardless, enjoy.

engine95 said:
V1.2 is in OP!!!!! Just patched to 3.10.105, which is Feb 2017
Not quite sure if I'll go to 108, or do some addons. I'm kinda burned out on the patches.
More than likely I'll patch to 108, but I am dreading it as just the 3 more patches has over 750 fixes.
And seeing as how our Tablets AND our Kernel is at EOL, I might as well finish it out.
Regardless, enjoy.
Click to expand...
Click to collapse
Thank you, thank you. Don't burn out!
---------- Post added at 01:50 PM ---------- Previous post was at 12:56 PM ----------
andyroidking said:
810 v1.1 A-Okay
Click to expand...
Click to collapse
1.2 good to go of course.

Okay, so I don't know what is missing or changed in the kernel but all of a sudden I am getting horrible battery life I can almost watch it drop sometimes. If you're thinking of updating more maybe putting back some of the tweaks that you had? First?
Edit- it literally dropped a percent when I typed the above.

andyroidking said:
Okay, so I don't know what is missing or changed in the kernel but all of a sudden I am getting horrible battery life I can almost watch it drop sometimes. If you're thinking of updating more maybe putting back some of the tweaks that you had? First?
Edit- it literally dropped a percent when I typed the above.
Click to expand...
Click to collapse
Now that's interesting. I used my Tab last night and all was well.
It could be a rogue app. Or maybe you need to shut it off for a minute. Then boot it up again. There were a lot of changes in the kernel and resetting doesn't always fix things. The battery might need to relearn too.
Side note:
Ya know how when climbing you see a peak and you just have to keep going til you can see over it? Yeah, well, I've just about finished the patches to 108. It'll be a couple days. I just barely got it built and need to see how it does.
Here's some pics of battery for me. And I've installed the kernel a few times too. So reboots are included.
Edit
There's an old trick I still do for "Ghosts in the computer".
Power the Tab off, wait for bout 15 sec, then just press the vol down, vol up and power buttons. Just a press. Do it a few times then boot it up.
The old belief is that there is still an electrical charge that can keep things in memory. By doing this, it'll discharge any current that is lurking.
It may be nothing, but I feel better doing it.

engine95 said:
Now that's interesting. I used my Tab last night and all was well.
It could be a rogue app. Or maybe you need to shut it off for a minute. Then boot it up again. There were a lot of changes in the kernel and resetting doesn't always fix things. The battery might need to relearn too.
Side note:
Ya know how when climbing you see a peak and you just have to keep going til you can see over it? Yeah, well, I've just about finished the patches to 108. It'll be a couple days. I just barely got it built and need to see how it does.
Here's some pics of battery for me. And I've installed the kernel a few times too. So reboots are included.
Edit
There's an old trick I still do for "Ghosts in the computer".
Power the Tab off, wait for bout 15 sec, then just press the vol down, vol up and power buttons. Just a press. Do it a few times then boot it up.
The old belief is that there is still an electrical charge that can keep things in memory. By doing this, it'll discharge any current that is lurking.
It may be nothing, but I feel better doing it.
Click to expand...
Click to collapse
I really wish it was ghosts or Rogue app... rebooted 1.2 browsed Reddit for 17 minutes lost 7%. Flashed 1.1 browsed Reddit and as I'm typing this only 2% in 22 minutes.... We will see what 1.3 brings when it is cooked.

HTML:
andyroidking said:
I really wish it was ghosts or Rogue app... rebooted 1.2 browsed Reddit for 17 minutes lost 7%. Flashed 1.1 browsed Reddit and as I'm typing this only 2% in 22 minutes.... We will see what 1.3 brings when it is cooked.
Click to expand...
Click to collapse
So with 1.2 I was getting 3 to 4% at idle an hour battery drain. Installed 1.1 and overnight 8 hours 1%. Could just be something with my tab and that kernel not liking each other, lol.

andyroidking said:
So with 1.2 I was getting 3 to 4% at idle an hour battery drain. Installed 1.1 and overnight 8 hours 1%. Could just be something with my tab and that kernel not liking each other, lol.
Click to expand...
Click to collapse
I think I found the issue. It was very random and hard to find, but I'm pretty sure I have it fixed now. It'll come out when I finish/ release 108.
For now, all the kernels run fine, so if there's no issues with what's installed, then just keep running it till I get 108 up. Like I said, it's a random thing with 105. Hit or miss. I'll pull v1.2(105)when I get v1.3(108) up.
Thanks for making me look into it. Lol

Thank you @engine95 for your amazing effort. You made my tablet super smooth. And really I was about to sell it, but you let me keep it for another year . Thanks ??????

V1.3 is in OP for all 4 kernels Patched to 3.10.108EOL
I've pulled V1.2 as it had random issues and/or isn't needed now with the fixed V1.3
Just a little FYI
Stock 3.10.9, vs Patched 3.10.108 - Stability vs Security
V1 is the mostly stock 3.10.9 kernel. It will be the most stable of all the kernels as Samsung has tailored it to our Tablet
The rest
These should be the most secure as it has all the Linux patches to date. Thing is, Samsung hasn't made adjustments to optimize the kernel to anything past 3.10.9
Patching it can cause some problems. Usually WiFi, Bluetooth, Battery, USB.
Patching it may make more current products useful. Routers, Game Pads, Hard drives etc....
So from here, I'll wait and see if we have more issues with the patched kernels before moving on.
My options?
Keep going with the patched kernel to build on
or
Go back to 3.10.9 for the stability, and leave the patched kernel where its at.
Let me know how V1.3 does so I can start with the addons on one or the other.
Thanks all and enjoy. :good: