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

[KERNEL][AOSP][2.6.38.2] - Savaged-Zen v1.0.0 [HAVS+CFS/BFS]!

ALL SOURCE CAN BE FOUND HERE
Concerns about XDA rules:
We will never charge for our forum. Our forum is read only to anyone without registering... you must register to post. Getting downloads of the advertised kernels will be listed on both XDA and forum.savage-zen.org. Savaged-zen's download site will always be publicly accessible, and nothing we have will ever be closed source or have any fees. This meets XDA's rules.
Our team consists of 5 guys. (in order of Name(real name))
NyghtGT (Anthony) Website, Graphics
Bbedward (Brandon) Kernel
Jsseidel1 (Josh) ROM/Kernel
Luisrcastillo (Luis) Kernel
mwielgosz (Mike) ROM/nonSBC Builds
Credits
Cyanogen and team --> various code bits
toastcfh --> various commits from .35 version of CM-Kernel
#teamwin --> wimax drivers in kernel and HDMI changes in kernel for full HDMI mirror (using the HDMwIn app)
erasmus --> smartass gov
intersectRaven --> HAVS
ms79723 --> SBC Mod
Zen-Kernel team --> various modifications
If we forgot anyone or you think you should be added to credits please PM us
(credits are given to the dev's where we got some code from, may no be original designer)
Please visit http://mirror.savaged-zen.com for the download.
you can give the progress of the builds @ http://buildbot.savaged-zen.org/builders one there all green you will see them on the mirrors.
Changelog is listed on the homepage: http://www.savaged-zen.org/?page_id=57
We request that you look for updates on our forum. We will post links to download there, as well as updates to the changelog.
Keep note : We will still update OP title, and answer questions on XDA, but as we all have admin rights on the forum we dont have to depend on one person to keep updated, and it will also make it easier for us to create a WIKI
our forum is located at
http://forum.savaged-zen.org
Check out our homepage at http://www.savaged-zen.org
If you like our kernel and want to support us... donate (supports the homepage payments and then beer!!)
nonSBC Versions can be found here
SBC WARNING:The Savaged-Zen team takes no responsibly for any issues to your phone or battery, including but not limited to, battery derogation or failure. SBC has been rumored to have caused issues with battery's and claims have been made that it actually causes physical damage to your phone. It is the users responsibility to review any opinions or warnings about such claims, and by flashing kernels that include the SBC mod, the user is taking the responsibility for any issues or failures to their phone. Please research this Modification, review the code, and come to your own decision before using such modification.

reservedaaaaaaaaaa

Sweeeet! Bringing the inc out of the dark ages. We'll finally be on par with the nexus one and supersonic
Sent from my ADR6300 using XDA App

I'd love to test. Just PMed you

Just pm'd you. Im so excited!
Sent from my DROOOOOID Incredible using XDA App

running GB cm7... I will test it out!

Just responded to all the PMs, once a couple people report back i'll just make it available to the public
All i heard so far was that it booted, the first build i forgot the atmel touch screen driver, but the test2 build (the one i just sent out in the masses) includes it, so hopefully most everything works.
*EDIT*
Everyone who PM'd got a build, i'm going to wait to hear back before sending out anymore so please don't PM, if the results are good i'm going to update the OP with both test builds.

Didnt work for me. It splash looped for me.
Sent from my full_inc using XDA App

flashing now. will report back

did not work for me either, I got stuck at the incredible screen, pulled battery it got past that, the screen went black and then I noticed green/red/blue bars running vertical down my screen

dang, i was too late

I got it to boot but no touch capabilities

Updated the OP
The builds there fix the touch screen issue and probably the wifi and BT issues, although as a tendency in the newest bcm4329 drivers wifi sleep policy should probably be set to never
The people who can't boot I suspect cache/dalvik arent being wiped properly (depending on recovery, usually clockworkmod is the one with the issues). Other than that all I can think of is there's some difference between incredible and incrediblec (but i don't think it necessarily matters?)
Anyway, as I don't have an incredible i'm relying on the testers

bbedward said:
Updated the OP
The builds there fix the touch screen issue and probably the wifi and BT issues, although as a tendency in the newest bcm4329 drivers wifi sleep policy should probably be set to never
The people who can't boot I suspect cache/dalvik arent being wiped properly (depending on recovery, usually clockworkmod is the one with the issues). Other than that all I can think of is there's some difference between incredible and incrediblec (but i don't think it necessarily matters?)
Anyway, as I don't have an incredible i'm relying on the testers
Click to expand...
Click to collapse
I got a newer incredible with SLCD screen

Touchscreen works now, way to go! Now for things that don't work:
- Wifi attempts to turn on, but fails
- Bluetooth also attempts to turn on, but fails
- LED notification light doesn't seem to function for alerts, charging, or anything
Other things that work:
- GPS locks on in about 5 seconds (sitting inside of a house)
- 3G data
- Voice calls
- SMS/MMS
- Still camera
- Camcorder
- Battery charge counter

neur0tk said:
I got a newer incredible with SLCD screen
Click to expand...
Click to collapse
Could be just a missing driver then, should be easily rectified, i suspect the same with LEDs, and wifi is strange unless for some reason the module isn't probing, maybe the module goes in a different place for the incredible who knows

bbedward said:
Could be just a missing driver then, should be easily rectified, i suspect the same with LEDs, and wifi is strange unless for some reason the module isn't probing, maybe the module goes in a different place for the incredible who knows
Click to expand...
Click to collapse
Want me to modprobe for the wifi? I'll need the module name.

jonesh said:
Want me to modprobe for the wifi? I'll need the module name.
Click to expand...
Click to collapse
it's bcm4329, it's built and in there, unless something funky in the makefile is changed it should work fine.

bbedward said:
it's bcm4329, it's built and in there, unless something funky in the makefile is changed it should work fine.
Click to expand...
Click to collapse
$ su
# modprobe bcm4329
modprobe: chdir(2.6.37-Savaged-Zen-INC-0.0.1-alpha+): No such file or directory
#

Something else peculiar... I'm not sure if the phone's charging. I have it plugged into a wall outlet, and while the LED is not lit as reported before, my charge percentage is dropping. That said, the battery icon is displaying the 'animating' charge. Thoughts?

[KERNEL][2.6.27]Midnight's kernel and Midnight's Bundle

Hi all!
After being for a long time a neopeek.com thread only,i've choosen to post the kernel here too..
Please note that i'm using codesourcery's toolchain 9-2010
If the kernel fails at booting
Please check this startup and this haret
Please change
Code:
set INITRD_OFFSET 0xSOMETHING
to
Code:
set INITRD_OFFSET 0xA00000
in startup.txt
If you don't have the line in startup,add it,it must be anywhere before "boot"
DOWNLOADS
V12
http://dl.dropbox.com/u/27345952/2.6.27/2.6.27.46_EXT3-01377-g404dbe9.7z
V11
http://dl.dropbox.com/u/27345952/2.6.27/2.6.27.46_EXT3-01375-g6079b24.7z
V10
http://www.mediafire.com/?282q7didmlm4hsg
V9
http://www.mediafire.com/?vsqy8i8l2ft6lt7
V8
http://www.multiupload.com/Y1OY44WA4H
CREDITS
Alex[sp3dev] for the gpu overclock,for the charger and for many X1 fixes..
Blackra1n for help with the overclocking part
Xdandroid team for the kernel source
Caliban2 for testing everything I uploaded
Everyone who has helped me improving this kernel with reviews and tips
Everyone who has bundled this kernel in the builds
SOURCES
Kernel
CHANGELOG
V12
642200 MHz now runs with 200 Mhz AXI and AHB clocks
Fixed a small issue with AXI and AHB clocks,them weren't set properly
PLL clock is now mantained after panel blank-unblank
V11
Added some scaling steps,642200 MHz and 100800 MHz
Last frequence(642200) runs off PLL3,making a small speed bost
AXI and AHB are clocked at 160 MHz for PLL3,when making it higher the phone became unresponsive and slow
Default governor is On demand if you don't use my new rootfs
Kernel uses now 642200 as default max frequency
CIFS is back
V(R) is now default I/O scheduler,however you can always go back to No-op
Worked a bit on Kovksy battery meter,should be a bit more responsive now
V10
EXPERIMENTAL,Topaz should boot now
Kovsky battery fix,now is being more precise
Reverted to the old way to handle clock,doesn't bring more performance,could make the battery last a bit more
V9
EXPERIMENTAL,EXT4 support
Kovsky battery fix,now is being read properly
CIFS is being built as a module
No-Op I/O scheduler
Small but useful change in the way cpu handles clock
V8
Partially fixed kovsky battery meter
Now battery discharges and charges,is just bad calibrated
DISCLAIMER:
If your phone(or SD-CARD) burns,explodes,or does unexpected things when using my kernel i take no responsability.
BUG LIST
Camera not working on X1,that's a common issue,pheraps it's time to backport from alex's .35
Class 6 and above sd-cards don't work well on blackstone

Bundle
Since ext3 is bringing good results and since everyone is saying good things about it
I've decided to make it more noob friendly.
DOWNLOADS
V9[BUNDLE]
V8
V7
V6
V5[BUNDLE]
V4[BUNDLE]
INSTRUCTIONS:
Please read carefully README.txt
If you can't extract it,please download latest 7zip..
NOTES FOR DEVELOPERS/CHEFS:
You need to update /META-INF/com/google/android/updater-script to make the build working with ext3
Change all the format and mount lines to ext3 instead of ext2.
Example
Code:
format("ext2", "EMMC", "/dev/block/mmcblk0p2");
has to be
Code:
format("ext3", "EMMC", "/dev/block/mmcblk0p2");
CHANGELOG:
V9
ROOTFS: Rel_path fixed
ROOTFS: Removed some hardcoded /sdcard/npkboot,now system can run from any folder
ROOTFS: Added some checks for the existance of CSV files in root of the SD-Card
ROOTFS: Boot will now fail if no CSV are found to avoid missing audio
ROOTFS: Updated Gingerbread's init.rc
KERNEL: New Acoustic code,improves audio in all the system,allows more tweaks to be performed by editing manually CSV files
KERNEL: Fixed static sound with data enabled
KERNEL: Brought back wlan.ko
KERNEL: Kexec working
BUILD : New GBX0B build included
BUILD : This build contains the new acoustic code
BUILD : Completely based on latest Gingerbread release by XDANDROID team,with some small tweaks for speed and working with CWM
V8
KERNEL:642200 MHz now runs with 200 Mhz AXI and AHB clocks
KERNEL:Fixed a small issue with AXI and AHB clocks,them weren't set properly
KERNELLL clock is now mantained after panel blank-unblank
ROOTFS:New RIL and new Lights.ko for froyo
ROOTFS:Updated init.rc's
V7
KERNEL:Added some scaling steps,642200 MHz and 100800 MHz
KERNEL:Last frequence(642200) runs off PLL3,making a small speed bost
KERNEL:AXI and AHB are clocked at 160 MHz for PLL3,when making it higher the phone became unresponsive and slow
KERNEL:Kernel uses now 642200 as default max frequency
KERNEL:CIFS is back
KERNEL:V(R) is now default I/O scheduler,however you can always go back to No-op
KERNEL:Worked a bit on Kovsky battery meter,should be a bit more responsive now
ROOTFS:"Performance" is now the default governor
ROOTFS:Fixed init.d support
V6
KERNEL:Reverted the screen on/off frequencies
KERNEL:Kovsky battery should be more precise
ROOTFS:init.d support
V5
KERNEL:Kovsky battery working
KERNEL:EXT4 is back
KERNEL:No-Op is the I/O scheduler now
ROOTFS:XDANDROID partition layout can be used now
Read readme please
V4
KERNEL:Some small clocks changes
ROOTFS:Things that needs an explanation,please read readme
V3
KERNEL:Reverted some changes to Epson panel (Kovsky,Blackstone and RAPH800)
KERNEL:Added JB's audio stuttering fix/hack for Diamond and Blackstone
V2
KERNEL:Reverted turbo to 960 MHz
ROOTFS:Enabled fail,this is going to stop boot process when no partitions are made.
ROOTFS:Readahead back to 1024
V1
Initial Release
Sources:
KERNEL
ROOTFS
INITRD
CREDITS TO:
Neopeek for Neofroyo and CWM
Xdandroid team for the kernel,rootfs source and inird
Turbolapin/lapin for the inird repacking trick,really really thank you!

well, I've tested your V10 Rom with an EXT2 rom which is SenseDroid V9 and it's amazing
but two issues:
1. Wifi doesn't seem to work for some reason even when turned on in winmo
2. There is this weird sound that comes from the speaker every few seconds
Other than that ... The kernel is great and fast and I love it ...
I hope I have helped and I'm sorry I'm new to all of this and I'm trying to learn as much as I can ... I hope I don't bother you with my questions and reports

Hello Midnight,
nice to see this kind of topic here, I think many X1 users didn't find it at neopeek's site in Blackstone, Topaz (etc) section. Hope you will get better X1 feedback here.
I've tested V9 and V10 kernels on Jerrytan's Honeydroid with EXT3. I think both have slightly higher battery consumption than old Ygge's Turbo kernel.
Battery reading is still in both kernels literally "jumping" around the right value and it is changing several times per minute. But in V10 it seems a little bit better.
And as it was already said there is a strange sound comming from phone speaker in V10, when phone network is used, like when you put phone near some speaker.
I didn't tested wifi.
Thanks for your work and good luck in further development.

frybend said:
Hello Midnight,
nice to see this kind of topic here, I think many X1 users didn't find it at neopeek's site in Blackstone, Topaz (etc) section. Hope you will get better X1 feedback here.
I've tested V9 and V10 kernels on Jerrytan's Honeydroid with EXT3. I think both have slightly higher battery consumption than old Ygge's Turbo kernel.
Battery reading is still in both kernels literally "jumping" around the right value and it is changing several times per minute. But in V10 it seems a little bit better.
And as it was already said there is a strange sound comming from phone speaker in V10, when phone network is used, like when you put phone near some speaker.
I didn't tested wifi.
Thanks for your work and good luck in further development.
Click to expand...
Click to collapse
izzyk said:
well, I've tested your V10 Rom with an EXT2 rom which is SenseDroid V9 and it's amazing
but two issues:
1. Wifi doesn't seem to work for some reason even when turned on in winmo
2. There is this weird sound that comes from the speaker every few seconds
Other than that ... The kernel is great and fast and I love it ...
I hope I have helped and I'm sorry I'm new to all of this and I'm trying to learn as much as I can ... I hope I don't bother you with my questions and reports
Click to expand...
Click to collapse
Is the speaker bug present with xdandroid kernels?
Wi-fi worked with V9,so something is wrong build side..

I dunno about the Xdandroid kernel as I have never used it ... I just downloaded the files and over wrote them on a Turbo kernel and changed the start-up file to yours ...
The speaker just does a sound close to the one when u put ur phone next to the speakers like it was said ... but it's coming from the speaker of the phone itself ...
Well, I'm gonna wait for Jerrytan's new EXT3 Rom ... hopefully this week and I'll further test your kernel and give u more feedback ... thanks for your efforts

I've never used xdandroid kernels too. But the speaker sound is messy only in V10, in my case V9 was fine in this matter.
And I forgot to mention that the phone speaker is always on...

WOW!!!Tnx dear Midnight for this awesome release.........
I'll replace it with V9 ASAP
and one question.....randomly,when I press my X1's power button to check the clock or sth,My device screen get back and it dies,I forced to reset my device by pressing the reset key to make this issue solved..........
Is it solved in this Kernel??

reza3310 said:
WOW!!!Tnx dear Midnight for this awesome release.........
I'll replace it with V9 ASAP
and one question.....randomly,when I press my X1's power button to check the clock or sth,My device screen get back and it dies,I forced to reset my device by pressing the reset key to make this issue solved..........
Is it solved in this Kernel??
Click to expand...
Click to collapse
I've not seen any SODs recently..

I don't know if this helps, but:
The sound is active when data connection (EDGE/GPRS) is used. It stops right after a phone call and the speaker is off for a while. But it starts again after a while, maybe 2-3 minutes and the speaker is on again.
I don't know if this is kernel related, but i can't recieve mms messages. The truth is, that I didn't test this with other kernels cause I don't usually use MMS.

I've also tried V9 ... the hizzing sound is less frequent but it's always on when I'm using internet mobile as mentioned before ... V9 is very fast and stable. with an EXT3 rom it was working amazing ... I think it uses a bit more battery than the Turbo kernel but with the option to charge from Android itself ... I don't mind that as I mostly carry a charger around if I'm going out for long ...
also, there's a second of black screen after you press the power button ... the hizzing sounds stops once the screen is off ...
The other only problem I see so far the battery meter but u are already working on that in V10 ... Thanks so much for the great efforts

izzyk said:
I've also tried V9 ... the hizzing sound is less frequent but it's always on when I'm using internet mobile as mentioned before ... V9 is very fast and stable. with an EXT3 rom it was working amazing ... I think it uses a bit more battery than the Turbo kernel but with the option to charge from Android itself ... I don't mind that as I mostly carry a charger around if I'm going out for long ...
also, there's a second of black screen after you press the power button ... the hizzing sounds stops once the screen is off ...
The other only problem I see so far the battery meter but u are already working on that in V10 ... Thanks so much for the great efforts
Click to expand...
Click to collapse
Hey dear friend,tnx for ur reports....
But I hear hizzing when I'm not using internet too!!
I have pressed the power button several time to sleep and wake up my device to check the hizzing....no changes!
I say tnx dear Midnight again
super fast and stable.....But the battery drains so fast for me,maybe 5 6 hours(in less uses than normal use)
speaker hizzing,and still I have to turn speaker on for incoming call to hear my friend voice[I don't know how this issue is solved for somebodies]

frybend said:
I don't know if this helps, but:
The sound is active when data connection (EDGE/GPRS) is used. It stops right after a phone call and the speaker is off for a while. But it starts again after a while, maybe 2-3 minutes and the speaker is on again.
I don't know if this is kernel related, but i can't recieve mms messages. The truth is, that I didn't test this with other kernels cause I don't usually use MMS.
Click to expand...
Click to collapse
izzyk said:
I've also tried V9 ... the hizzing sound is less frequent but it's always on when I'm using internet mobile as mentioned before ... V9 is very fast and stable. with an EXT3 rom it was working amazing ... I think it uses a bit more battery than the Turbo kernel but with the option to charge from Android itself ... I don't mind that as I mostly carry a charger around if I'm going out for long ...
also, there's a second of black screen after you press the power button ... the hizzing sounds stops once the screen is off ...
The other only problem I see so far the battery meter but u are already working on that in V10 ... Thanks so much for the great efforts
Click to expand...
Click to collapse
reza3310 said:
Hey dear friend,tnx for ur reports....
But I hear hizzing when I'm not using internet too!!
I have pressed the power button several time to sleep and wake up my device to check the hizzing....no changes!
I say tnx dear Midnight again
super fast and stable.....But the battery drains so fast for me,maybe 5 6 hours(in less uses than normal use)
speaker hizzing,and still I have to turn speaker on for incoming call to hear my friend voice[I don't know how this issue is solved for somebodies]
Click to expand...
Click to collapse
I don't have data connection,so i can't test this..
I can't see why this bug is present..
about battery drain,uhm..,trying to fix it..

I get an incoming call....that was OK....strange..
seems that it sometime happens.....
tnx Mr boss

Thanks so much for replying ... I hope all these issues I report don't bother you ... I'm just trying to help improve this kernel
another issue I realized is that sometimes when the screen sleep for about an hour, it doesn't seem to wake up and when I slide the keyboard I see the lights when means it's working but the screen never wakes up ... is there a way to solve this? this testing with an EXT3 rom and V9 of your kernel

izzyk said:
Thanks so much for replying ... I hope all these issues I report don't bother you ... I'm just trying to help improve this kernel
another issue I realized is that sometimes when the screen sleep for about an hour, it doesn't seem to wake up and when I slide the keyboard I see the lights when means it's working but the screen never wakes up ... is there a way to solve this? this testing with an EXT3 rom and V9 of your kernel
Click to expand...
Click to collapse
Panel collapse doesn't work as it should,and i guess that the CPU throttling isn't working well either
Can anyone tell me if this battery life is nice?
15 seconds of Wi-Fi,1 hour of games,3 or 4 10 minutes calls,30 texts made the battery go from more or less 80(Can't remember the exact value from wm) to 50 in android in 4 hours?
EDIT:Can anyone with the speaker bug provide me dmesg and logcat when you hear that sound?

I recharge my phone after about 7 hours[78% to 20% and then It got off]
that was not bad for an android ROM for me,But u lost just 30% for 4 hours of hard working :-o ......I mean gaming and voice calling and texting....But my phone was just in standby and I seldom used it.......maybe about 30Mins

well, this battery usage sounds good ... 4 hours with using the phone and 30% only sounds good ... this means the phone can last for about 12 hours when fully charged ... but could u please test it with more wifi usage as this will test the battery more as u know how android likes to be connected to the internet all the time whether wifi or 3G ... but 1 hour of games should also test the battery ... so, I guess that sounds good ... great job man
about the dmesg and logcat ... I hope someone with experience can help with that ... perhaps we will get more feedback when Jerrytan tests it or makes his SenseDroid an EXT3 Rom, cuz many people use that Rom which will provide more testing for the kernel ... I probably can't help cuz I don't even know what these mean, let alone get them I'm sorry ... also, I'm gonna be using winmo more for the time being with an old EXT2 Rom sometimes as I have too much studying to do ... so, I wish I can help, I'm sorry ...
but in 3 weeks time, I'll be done and hopefully do my best to help with everything ... Thanks so much for the great efforts

izzyk said:
well, this battery usage sounds good ... 4 hours with using the phone and 30% only sounds good ... this means the phone can last for about 12 hours when fully charged ... but could u please test it with more wifi usage as this will test the battery more as u know how android likes to be connected to the internet all the time whether wifi or 3G ... but 1 hour of games should also test the battery ... so, I guess that sounds good ... great job man
about the dmesg and logcat ... I hope someone with experience can help with that ... perhaps we will get more feedback when Jerrytan tests it or makes his SenseDroid an EXT3 Rom, cuz many people use that Rom which will provide more testing for the kernel ... I probably can't help cuz I don't even know what these mean, let alone get them I'm sorry ... also, I'm gonna be using winmo more for the time being with an old EXT2 Rom sometimes as I have too much studying to do ... so, I wish I can help, I'm sorry ...
but in 3 weeks time, I'll be done and hopefully do my best to help with everything ... Thanks so much for the great efforts
Click to expand...
Click to collapse
I don't have 3G,wifi still uses a lot of battery,I don't think it will last more than 2h with wifi on..
I'm going to upload the kernel..

my wifi was off today,except that for 10 mins that I would check something on internet........
BTW,If my wifi be turn on and I don't use it[just it be connected to my modem]it will drain my battery so fast??
u meant a new kernel,ha?

Custom ROM breaking serious GPS bug. Help needed.

My Original Post:
Phone runs hot. No deep sleep. High cpu usage from AndroidSystem app. Sometimes screen doesn't turn off after pressing power button. Phone runs slow.
All of this happen after any GPS data request from any app that can use device only gps data.
When GPS is off with a fresh boot, there is no problem.
When gps is turned on but not any data requested from it, there is no problem.
If you turn on device only gps and start using a gps app. CPU usage goes abnormally high and never falls down even after force closing the gps app and gps itself. Only a reboot turns the phone to normal.
Another thread I've found describing the same problem without solution:
http://forum.cyanogenmod.org/topic/94185-gps-bug-phone-unstable/
I've tested:
cm-11-20140916-SNAPSHOT-M10-p880
cm-11-20150517-NIGHTLY-p880
cm-11-20150524-NIGHTLY-p880
Euphoria-OS-1.1-p880-UNOFFICIAL-20150516
Euphoria-OS-1.1-p880-UNOFFICIAL-20150529
aosplp-20150423-p880
MK44.4-p880-150131-HISTORY (Mokee History)
LS-KK-v3.2-2014-10-14-p880 (Mourta Ed. with kernel 3.4)
LS-LP-v4.0-2015-03-27-liquid_p880 (Mourta Hybrid Kernel 3.4)
BeanStalk-4.4.4050-20140905-p880CMAD
Kernels:
Optimus_Prime_CM11-V3.0
iodakX3_v10_CM
WWJB_v009_anykernel-20140429
WWJB_v010_anykernel-2014-12-24_1303
I've tried listed roms and kernels with required wipe operations switching between them.
I've rebooted several times after installation and didn't give up in first boot.
I have CWM Official v6.0.4.5 as recovery.
Tried different governors and schedulers. No luck.
I'm using the phone with CM 10.1.3 Stable & WWJB_v009_anykernel-20140429 and I don't have this problem with it.
GPS apps never use high amount of CPU and when you turn off GPS apps, CPU usage falls to idle levels.
I've flashed same WWJB_v009_anykernel-20140429 kernel over a fresh CM11 M10 install and gps bug is still there.
I think this is not about kernel or rom but something different. I can't move forward from Jellybean.
Any idea what's causing this?
Any clues, ideas or suggestions are appreciated.
Click to expand...
Click to collapse
Update: I still have this annoying problem and I'm trying to solve this.
I need you to test this on your devices and tell me the result. Please.
How to reproduce the bug
1- Prepare your SD card with the custom Rom(Kitkat or later preferably with built-in file manager to install apks) to flash and apk files of F-Droid Satstat, CPU-Z for monitoring the cpu load.
2- Before flashing the rom, REMOVE your SIM card. The important thing is, do not let the phone go online after the fist boot. I will download the Agps data immediately and it may work without problem.
3- Flash X-cm12_1_1-20161131-ufoFILES-p880 or any other Rom which is 4.4+ or later. I've tried many and all of them have this problem.
4- After the first boot,(ignore the no "sim card inserted restart" notification just touch some where out of that box) install satstat and cpu-z.
5- Turn on your GPS if it is off.
6- Launch the GPS test app satstat. It will try to connect to GPS and Glonass satellites (if you have a v20 baseband) It is not important to keep the app running until you get a lock just wait for 15 seconds.
7- Close the gps app.
8- At this point you should be seeing a serious lag. Pushing the power button won't response. The phone won't go the sleep. If it does, it won't wake up easily. You will be pushing the power button several times to make it work. Battery will be drained fast.
7- Launch the CPUZ and watch the CPU load and frequency. One or two cores will spike up and down constantly and the cpu will stay at 1000-1500mhz forever.
8- There is nothing to do but restarting the phone. Sometimes my phone gets totally frozen before I'm able to restart it from the power menu. After the restart it will work normally. Provided if you keep the gps closed and not requesting info from it.
Could you test this please?

Problem solved. Temporary solution.
My description from CM11 Official thread:
Finally, I'm happy to clarify that both assisted and device only gps is working excellent!
After many sleepless nights, I've found what's causing the problem in my device. I've gone over 15+ custom roms and different kernels. I've changed baseband and custom recovery to only get despair.
The last thing I did before abandoning everything.... has worked.
Assisted GPS has to go on-line at least one time.
I'm not sure about the logic behind this but I can't believe how such a simple thing caused this trouble for me...
I don't have a data plan right now so no there is no data from cellular. I generally use device only gps outside. I've never used this rom with assisted gps when outside. I didn't get a chance.
When at home, I flashed roms with "device-only gps" testing in mind so I didn't bother connecting to wireless.
I tried this just with 20150524 and nothing else. (gapps, kernel etc.)
Enabled high accuracy mode on gps and connected to wifi.
Launched GPS Status & Toolbox app and at first, cpu usage was high but after the first fix, it's reduced to normal. I exited the app and cpu usage fell to idle as it should.
Switched off wireless and switched gps to device-only. Rebooted. Launched the GPS Status & Toolbox again and now it's working normally under device only mode. Other applications also working good.
Click to expand...
Click to collapse
Fused Location Provider, responsible for managing different data sources for providing geolocation data, manages the assisted or device-only gps itself. When you enable GPS, it switches the gps mode to high accuracy itself but if you hadn't gone online before with using assisted gps, gps is always stuck at device-only. I think that creates the high CPU usage.

THANK YOU THANK YOU THANK YOU!!!! I wanted to change custom ROM because of this, and you saved me from doing it! So, if I understood correctly, all I need is to enable High accuracy mode, launch "GPS status & toolbox" app (or can it be any other gps app?) and restart after the app gets a fix?

terirem said:
THANK YOU THANK YOU THANK YOU!!!! I wanted to change custom ROM because of this, and you saved me from doing it! So, if I understood correctly, all I need is to enable High accuracy mode, launch "GPS status & toolbox" app (or can it be any other gps app?) and restart after the app gets a fix?
Click to expand...
Click to collapse
You need to let the device to download A-GPS data from internet. GPS status & toolbox does this easily and you can see the "a-gps age" at the app screen as how old your data is.
Once you get a fresh a-gps data, the phone won't stuck at high cpu frequency when gps is enabled.
I 've found out that after "a-gps age" goes over 20+ days, something happens to the gps, and gps usage starts to cause high cpu usage and frequency stuck again. You have to re-download a-gps data to solve this.
I don't know why but gps in this device is not a true offline gps.

I've already described a temporary solution to my GPS bug.
I'm still trying to find a lasting solution.
Here is what I did in various posts:
http://forum.xda-developers.com/showthread.php?p=69893311#post69893311
http://forum.xda-developers.com/showthread.php?p=69970358#post69970358
http://forum.xda-developers.com/showthread.php?p=69988910#post69988910
http://forum.xda-developers.com/showthread.php?p=70066931#post70066931
http://forum.xda-developers.com/showthread.php?p=70067876#post70067876
http://forum.xda-developers.com/showthread.php?p=70068250#post70068250
http://forum.xda-developers.com/showthread.php?p=70071380#post70071380
http://forum.xda-developers.com/showthread.php?p=70084342#post70084342
I also tried
- replacing fusedlocation.apk from /priv-app folder with CM10.1.3 stable's fusedlocation.apk
- another fusedlocation.apk from Atrix 4g (wiped dalvik cache after priv-app change)
- μg v1.3.2 from >HERE<
New roms:
Near all versions after cm-11-20150524-NIGHTLY-p880 up to the FINAL cm-11-20160815-NIGHTLY-p880
omni-4.4.4-20150520-p880-FINAL
X-cm12_1_1-20161016-ufoFILES-p880
X-cm12_1_1-20161131-ufoFILES-p880
Kernels:
CyodakX3_v11_CM
cyospak12
Cyospak6-7
I also upgraded my V20D baseband to V20c-EUR-XXX-OCT-07-2014 and trying ROM/Kernel combinations with this.
So far I've only tried
cm-11-20160815-NIGHTLY-p880
omni-4.4.4-20150520-p880-FINAL
X-cm12_1_1-20161016-ufoFILES-p880
X-cm12_1_1-20161131-ufoFILES-p880
Nothing works for me so far.
Thanks to @oF2pks , I think this may be ril/baseband problem.
Here is another thing:
When I check the "Settings/AboutPhone baseband" it shows L6260_modem_sic_02.1233.00 but If I disable SIM PIN lock and restart the phone it shows LGP880AT-00-V20C-EUR-XXX-OCT-07-2014.
According to oF2pks, a healthy phone should always have only one baseband reading under Settings/AboutPhone baseband.

Sorry for the late answer. I didn't give up and still working on my issue.
For easy describing, lets say State X to the the high cpu state which is causing general slowdown, stuttering, lag and freezes for my device, which occurs after GPS usage, without any data connection after fresh rom install and that kicks in again any time if you are not online with the phone frequently.
After many flashes and tests I found some interesting things.
- In State X, the phone actually goes to deep sleep BUT you have to wait for the 1 minute screen timer and don't push the power button to send it to sleep. After waking it up, cpu is still stuck.
- p880-ota-eng.nmf26qz never displays L6260_modem_sic_02.1233.00 but still falling to the State X.
Only custom rom working without State X problem for me is the cm-10.1.3-p880 stable.
I tried:
Switching cm-11-20160815-NIGHTLY-p880's com.android.location.provider.jar with cm-10.1.3-p880 stable's. → Result: State X
Switching cm-11-20160815-NIGHTLY-p880's telephony-common.jar with cm-10.1.3-p880 stable's. → Result: Error at start-up
add line to getprop file: ro.ril.def.agps.mode = 0
→ Result: State X
Switching cm-11-20160815-NIGHTLY-p880's lge-ril.so with cm-10.1.3-p880 stable's. → Result: State X
oF2pks said:
So do you have right baseband v20C when you boot with sim-on, or still firmware number?
Click to expand...
Click to collapse
This is where the things are getting interesting...
- With CM10.1.3-stable, first boot after the rom flash(without sim card) baseband shows L6260_modem_sic_02.1233.00 but in the second boot with sim card, after the very first initialization with gsm tower, it shows LGP880AT-00-V20c-EUR-XXX-OCT-07-2014 and stays like this.
- With my current daily drive cm-11-20160424-NIGHTLY-p880 + WerewolfJB kernel V10
Without sim-> LGP880AT-00-V20c-EUR-XXX-OCT-07-2014
With sim-> LGP880AT-00-V20c-EUR-XXX-OCT-07-2014
Sim with sim pin lock-> L6260_modem_sic_02.1233.00
With different roms, sometimes baseband switches from LGP880AT-00-V20c-EUR-XXX-OCT-07-2014 to L6260_modem_sic_02.1233.00 after gsm initialization.
In one situation, after all the tampering, I flashed CM10.1.3-stable again and this time it was stuck with
L6260_modem_sic_02.1233.00 and never showed the LGP880AT-00-V20c-EUR-XXX-OCT-07-2014 but no State X
With my daily drive, I also checked both states with sibor's Getril. md5sums are the same.
I'm adding screenshots for them.
I think, maybe baseband display is irrelevant with my issue.
Also did format via recovery cleared your previous rom specific settings?
Click to expand...
Click to collapse
All settings clear but I'm not sure abut default gps switch behaviour. Maybe it's irrelevant too.
Somehow gps switch remembers it's old positions.
Today on single(/primary_multirom) rom I have same kdz designation v20D while booting airplane or sim-on.
But on 2nd/multirom I have the difference (due to primary fake transition via kexec ?), AND the gps is working fine : airplane boot (+FasterGps) + Satstat OK and deep sleep after OK.
Click to expand...
Click to collapse
My current daily drive does not have the State X rgiht now. It will stay like this for a while without internet connection, but after some time, something will trigger the State X again and there are two solutions:
1- Don't enable GPS
2- Connect to internet and update the A-GPS data.
Did you check CPU usage after GPS use?
Mine stays at 1000-1400mhz with one or two cores.
IMHO you should pm @Demetris about V20C because he was the one who did cover v20c-2014 :http://forum.xda-developers.com/show...postcount=2727 ; also he's OP for alternative http://forum.xda-developers.com/opti...grade-t2919195 (and many more...)
Click to expand...
Click to collapse
I did the CSE flash method of Demetris for the V20C 2014.
I'll ask him about this gps issue. Thanks for the suggestion.
I'm also adding my getprop result for you. From fresh CM10.1.3 stable.
The biggest deal breaker for me with this phone was the "temp_throttle_skin" (around 40°C) temp limit. It's a real pain to have and the main reason of general slowdown.
At least I can deal with this GPS issue from time to time when it needs correction.
My aim here is to create some consciousness about this elusive issue for the fellow O4X users, so some unexplained battery drain issues may be resolved or dealt with by the user.
I wish everyone a Merry Xmas and a happy new year.

@KSH2014 , can you check few more:
-is imei/software = printed imei under battery
-is GPS OK with cm10's original kernel
-is GPS OK with lg JB v20c
Within hidden menu in lg JB, I remember bunch of options (GPS ?), and you problem could be somewhere in it, maybe @RuedasLocas could help you to re-settle this hidden menu
http://www.lg-phones.org/lg-optimus-4x-hd-hidden-menu.html

oF2pks said:
@KSH2014 , can you check few more:
-is imei/software = printed imei under battery
-is GPS OK with cm10's original kernel
-is GPS OK with lg JB v20c
Within hidden menu in lg JB, I remember bunch of options (GPS ?), and you problem could be somewhere in it, maybe @RuedasLocas could help you to re-settle this hidden menu
http://www.lg-phones.org/lg-optimus-4x-hd-hidden-menu.html
Click to expand...
Click to collapse
I've been busy lately.
- imei matches.
- GPS is OK with CM 10.1.3 Stable release with it's own kernel.
- GPS was OK or I think so with JB V20. I have to check it again.
I'm planning to record and upload a video to show the problem.

Here is the solution to eMMC error

Hello everyone,
I was pretty tired of the eMMC error, and I created a script that completely annihilate this error.
This error is due to the phone heating up, and the fact that custom kernels (maybe even the original kernel) don't read the sensors correctly and throttle the phone correctly. This script monitors the battery and all the CPU sensors and when it is higher than 82°C, throttle the phone.
It was tested on AEL Kernel that supports « Hard limit » command, but this script can be adapted on any other kernel. You may need busy box. You must root to run this script.
Must be placed in init.d folder.
You simply copy each script, and for example with Kernel Audiutor, create a new init.d and paste the script with the correct title.
script called cpu_temperature_daemon :
Bash:
#!/system/bin/sh
argu=$1
sleeptime=15
if ! [[ $argu = start ]] then exit ; fi
lock=0
while true;
do
maxnumb=0
cpuiscool=0
temp=$(cat /sys/class/thermal/thermal_zone*/temp)
tempbat=$(cat /sys/class/power_supply/battery/batt_temp)
if ((tempbat>410)) then if [[ $lock = 0 ]] then lock=1 ; sleeptime=7 ; chmod 644 /sys/devices/system/cpu/cpu1/online ; echo 1 > /sys/devices/system/cpu/cpu1/online ;chmod 444 /sys/devices/system/cpu/cpu1/online ; echo 65 > /sys/module/msm_thermal/parameters/core_limit_temp_degC ; echo 65 > /sys/module/msm_thermal/parameters/limit_temp_degC ; fi ; fi
for line in $temp; do if ((line>78)) then if ((line<120)) then if [[ $lock = 0 ]] then lock=1 ; sleeptime=7 ; chmod 644 /sys/devices/system/cpu/cpu1/online ; echo 1 > /sys/devices/system/cpu/cpu1/online ;chmod 444 /sys/devices/system/cpu/cpu1/online ; echo 65 > /sys/module/msm_thermal/parameters/core_limit_temp_degC ; echo 65 > /sys/module/msm_thermal/parameters/limit_temp_degC ; fi ; fi ; fi ; if ((line>10)) then if ((line<110)) then maxnumb=$(($maxnumb+1)) ; fi ; fi ; if ((line>10)) then if ((line<75)) then cpuiscool=$(($cpuiscool+1)) ; fi ; fi ; done
if [[ $maxnumb = $cpuiscool ]] then if ((tempbat<411)) then if [[ $lock = 1 ]] then lock=0 ; sleeptime=15 ; chmod 644 /sys/devices/system/cpu/cpu1/online ; echo 1 > /sys/devices/system/cpu/cpu1/online ;chmod 444 /sys/devices/system/cpu/cpu1/online ; echo 82 > /sys/module/msm_thermal/parameters/limit_temp_degC ; echo 82 > /sys/module/msm_thermal/parameters/core_limit_temp_degC ; fi ; fi ; fi
sleep $sleeptime ;
done
script called cpu_temperature_daemon_start to place in the same directory /system/etc/init.d/ :
Bash:
#!/system/bin/sh
numb=$(pgrep -lf cpu_temperature_daemon | wc -l) ; if [[ $numb = 1 ]] then exit ; fi
echo 75 > /sys/module/msm_thermal/parameters/core_limit_temp_degC ; echo 75 > /sys/module/msm_thermal/parameters/limit_temp_degC
nohup /system/etc/init.d/cpu_temperature_daemon start &
There is absolutely no more eMmc errors on the Note 4 that I tested. Of course, if you already have the error, script will not fix it. It will simply prevent a clean phone from having it by preventing overheat in monitoring all sensors. No big battery hog (insignificant). The script works by monitoring the all the sensors and reducing slightly CPU performance when the phone CPU is to hot (CPU > 82°C), or battery temp > 41°C.

If you don't game then the emmc thing won't happen right?

It will happen eventually, it is due to the phone overheating (it is not just heating, it is overheating due to the sensors not correctly reporting temperatures) so even opening Facebook will make it overheat

juandante said:
It will happen eventually, it is due to the phone overheating (it is not just heating, it is overheating due to the sensors not correctly reporting temperatures) so even opening Facebook will make it overheat
Click to expand...
Click to collapse
How do i fix a phone that has it? The "put cardboard under EMMC" fix lasted for like a week, my phone still works thanks to that Fix by using WakeLock (already it's been 8 months i think), but i don't want to use WakeLock anymore because it drains the battery a lot, plus since the eMMC is faulty the writing speeds are like 40MB/S so the phone is significantly slower.
I heard that this error was caused by Android 6 and immediately after i got the phone i flashed Android 5 stock, still i got like 6 months of use before this error (mostly only using Youtube and Discord).
Can i get the eMMC replaced to fix this? or i need an entire new motherboard? this phone is still really fast and usable even in 2023 with Android 5, but this error is really annoying and it makes the phone almost unusable, thanks.

juandante said:
It will happen eventually, it is due to the phone overheating (it is not just heating, it is overheating due to the sensors not correctly reporting temperatures) so even opening Facebook will make it overheat
Click to expand...
Click to collapse
If i end up getting another used Note 4 i will downgrade to LL and immediately apply your script

jonnyprogamer said:
If i end up getting another used Note 4 i will downgrade to LL and immediately apply your script
Click to expand...
Click to collapse
Yes, you simply have to copy paste each script in the /system/etc/init.d/ directory
I have put the correct tags and the script is now correctly highlited in my first post so you can easily see what it does.
Maybe for some kernels, you will need to adapt it.
Anyway, I can confirm to you that this limits dramatically the eMMC errors because the phone doesn't anymore overheat.

juandante said:
Yes, you simply have to copy paste each script in the /system/etc/init.d/ directory
I have put the correct tags and the script is now correctly highlited in my first post so you can easily see what it does.
Maybe for some kernels, you will need to adapt it.
Anyway, I can confirm to you that this limits dramatically the eMMC errors because the phone doesn't anymore overheat.
Click to expand...
Click to collapse
Ok thanks, but is there anyway to fix this error on a Note 4 that already had it? maybe reballing the eMMC?
I don't think it's worth to me to get another used Note 4, because i don't know what the previous owner might have done with it and it might already be dead to be honest.
I think that reballing the eMMC / swap the motherboard is the only way to truly fix this (and then use your script or downclock the CPU to keep the phone safe)

jonnyprogamer said:
Ok thanks, but is there anyway to fix this error on a Note 4 that already had it? maybe reballing the eMMC?
I don't think it's worth to me to get another used Note 4, because i don't know what the previous owner might have done with it and it might already be dead to be honest.
I think that reballing the eMMC / swap the motherboard is the only way to truly fix this (and then use your script or downclock the CPU to keep the phone safe)
Click to expand...
Click to collapse
You must have high end specialized soldering tools to fix the problem. Anything less than that will just fix the issue couple of weeks only if you are very lucky. You will be more lucky to buy a second hand Note 4 because most people generally speaking sell it because they bought a new phone, not because of the eMMC error due to heavy phone usage... If you really want to save money, just buy a new motherboard (it's somewhat cheap today).
Also, I think I had a eMMC symptom once (slow phone and the Note 4 was hardly booting), I managed with luck to boot the phone then applied the script, waited 1 day with the phone keeped on, and next the phone stayed somewhat fully usable for 12 months (with some random reboots now and then). So I think if you apply the script enough early when you get the first bad eMMC sign it is somewhat enough early to "revert" the issue if I could say so. I. E. The soldering is somewhat damaged and provoke random reboots but the script will prevent the phone from heating and damage even more the soldering.

juandante said:
You must have high end specialized soldering tools to fix the problem. Anything less than that will just fix the issue couple of weeks only if you are very lucky. You will be more lucky to buy a second hand Note 4 because most people generally speaking sell it because they bought a new phone, not because of the eMMC error due to heavy phone usage... If you really want to save money, just buy a new motherboard (it's somewhat cheap today).
Click to expand...
Click to collapse
Thanks, i guess i will try to find another Note 4, i might know someone that knows how to do BGA reballs, but even then i think that the issue are not the solder balls under the E-MMC.
Because it doesn't make sense, un-leaded solder melts at about 215C, and the EMMC isn't a big chip (so it's not like a GPU which can ""stress"" the solder balls when it gets hot and then cold).
For this reason alone it can't cause any cracks in the balls (unless you drop the phone but then again it's pretty unlickely to happen), what im thinking is that the EMMC chip just dies, it's not the solder beneath it, it's either a fault in the chip itself or a bug which gets triggered by something (like the Note 1 Superbrick).
Maybe we should take apart our phones with the issue, check the model number and report it here, probably those will be the fauly chips (this issue happened on the 360 and PS3 as well, everyone saying "it's the solder" and instead it was the GPU itself which dies because of the heat-cooling cycles).

You have a video tutorial on how to do this ?

Also the stock rom doesn't have init.d support.

dave678 said:
Also the stock rom doesn't have init.d support.
Click to expand...
Click to collapse
I know that PimpMyRom adds init.d support (tested on old chinese Android ICS tablet), i don't know if it works with Lollipop tough.
I just got my emmc reballed, when i get my phone back im gonna reflash latest 5.1.1 Or CM and use this script.

We will see if it lasts since the reball has been done with leaded solder, if it does not then it means that the fault was (and still is) the EMMC chip all along :=>

jonnyprogamer said:
I know that PimpMyRom adds init.d support (tested on old chinese Android ICS tablet), i don't know if it works with Lollipop tough.
I just got my emmc reballed, when i get my phone back im gonna reflash latest 5.1.1 Or CM and use this script.
Click to expand...
Click to collapse
Oh I have a brand new Sprint Note 4 running Kitkat and a Tmobile Note Edge running Kitkat

dave678 said:
Oh I have a brand new Sprint Note 4 running Kitkat and a Tmobile Note Edge running Kitkat
Click to expand...
Click to collapse
I have the unlocked international Europe version (SM-N910F) from italy (ITV CSC)

Android 4.4 stock uses the less resources of all but it's not smoother / faster than LL
Android 5.0.1 IS faster / smoother than 4.4, but uses more resources and it isn't optimized + very bad battery usage
Android 5.1.1 is the best stock from what i tested, less resources than 5.0 and good battery usage, also compatible with most apps from today.
Android 6.0.1 stock runs the worst (and according to a lot of people it was making the Emmc quickly because of the new hibernation when you turn off the display)
My reccomendation would be to either use stock Samsung 5.1.1 ROM or a Custom ROM (Cyanogenmod, Lineage, etc...)

jonnyprogamer said:
Android 4.4 stock uses the less resources of all but it's not smoother / faster than LL
Android 5.0.1 IS faster / smoother than 4.4, but uses more resources and it isn't optimized + very bad battery usage
Android 5.1.1 is the best stock from what i tested, less resources than 5.0 and good battery usage, also compatible with most apps from today.
Android 6.0.1 stock runs the worst (and according to a lot of people it was making the Emmc quickly because of the new hibernation when you turn off the display)
My reccomendation would be to either use stock Samsung 5.1.1 ROM or a Custom ROM (Cyanogenmod, Lineage, etc...)
Click to expand...
Click to collapse
You have the F model which is hard to find on Ebay and you can yo yo between different firmware. The closest model to the F would be the W model which can also yo yo between different firmware. My model cannot do that as once you go up to 5.1.1 you can kiss goodbye the ablity to downgrade to Kitkat. I have it as a collector's item basically. It's not my daily driver as it wouldn't work on my carrier anyways.

dave678 said:
You have the F model which is hard to find on Ebay and you can yo yo between different firmware. The closest model to the F would be the W model which can also yo yo between different firmware. My model cannot do that as once you go up to 5.1.1 you can kiss goodbye the ablity to downgrade to Kitkat. I have it as a collector's item basically. It's not my daily driver as it wouldn't work on my carrier anyways.
Click to expand...
Click to collapse
Ah i see, well i got mine from a local online marketplace here in Italy (Subito), before i bough it on Ebay and it was "brand new", but it turns out it was just the SM-N910V version with the F firmware (found out quickly because US bands aren't the same in Italy, so i had connection issues) so i did a refund.
If you're in US yea i think it's going to be pretty hard to find an Europe model.
I use mine as daily driver, SD card, removable battery, IR blaster, easy to take apart, it's still a really good phone.

jonnyprogamer said:
Ah i see, well i got mine from a local online marketplace here in Italy (Subito), before i bough it on Ebay and it was "brand new", but it turns out it was just the SM-N910V version with the F firmware (found out quickly because US bands aren't the same in Italy, so i had connection issues) so i did a refund.
If you're in US yea i think it's going to be pretty hard to find an Europe model.
I use mine as daily driver, SD card, removable battery, IR blaster, easy to take apart, it's still a really good phone.
Click to expand...
Click to collapse
I'm curious as to why the S5 doesn't suffer from the emmc issues as the Note 4 Snapdragon models since it also uses Emmc 5.0 like the Note 4.

dave678 said:
I'm curious as to why the S5 doesn't suffer from the emmc issues as the Note 4 Snapdragon models since it also uses Emmc 5.0 like the Note 4.
Click to expand...
Click to collapse
No idea, either it's actually the solder (doubt it, unleaded solder is more prone to cracks and breaking but melting temp is much higher than what the phone will allow) or buggy firmware / bios from samsung (already happened with Samsung Galaxy Note 1 with the Superbrick bug)