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)
Related
Given that the samsung froyo update has been delayed another month from what i have heard, i've decided that i might as well use a lagfix until froyo comes along.
Given that there are so many lagfixes, some old some new, and i have no idea which is good and which is new.
Could someone tell me which lagfix works the best?
and if possible also point me to a guide here or out there in the www.
thanks
Voodoo if you are on Eclair. OCLF if you are on Froyo.
But I am not running any from yesterday on my JPH. So far so good. Quadrant 1008.
Trust no one of them fixes... <insert mysterious music>
All the so called Lag Fixes do really work, BUT you might ruin your internal SD card in the process.
If you are willing to take the chance, then by all means go ahead and DO iT the speed increase is really amazing
However... expect your internal SD to die quickly as a result of that.
It's like a drug you know, just the same stuff some athretes takes to get an energy boost at the cost of their health.
AllGamer said:
Trust no one of them fixes...
All the so called Lag Fixes do really work, BUT you might ruin your internal SD card in the process.
If you are willing to take the chance, then by all means go ahead and DO iT the speed increase is really amazing
However... expect your internal SD to die quickly as a result of that.
It's like a drug you know, just the same stuff some athretes takes to get an energy boost at the cost of their health.
Click to expand...
Click to collapse
How is it destroying internal sd card ?
Sent from my GT-I9000M
if you search for SD problem here in the forum, all the topics that comes back states they were either using lag fix for a while, installing lag fix, or something else to do with lag fix
So you're trying to say that rfs file system which is reading and writing on sd also isn't destroy the internal sd?
Sent from my GT-I9000 using Tapatalk
what ever it's the slow rfs used by Samsung is at least less invasive than the methods we are currently using for the Lag Fixes
i'm not a developer, but if i were to fix what is wrong right now, i'll go with a virtual RAM drive solution.
that's how i configured old win2k servers and Win9x/XP machines
by avoiding write to a real disk it prevented delay, and that improved speed drastically even on low end machines
back in the SGS phone we are stuck with 512 RAM, so wasting more ram on a virtual drive might not be a good idea, but if we even setup a "cache" drive of 128 MB RAM instead of writing to the partitioned internal SD, that will kill 2 birds at once
improve speed and prevent SD write exhaustion
I'm still not yet at the point of being annoyed by the lag, else it would have been a big motivation to implement the idea mentioned above.
the only time i get lag is when i install 2 ore more Android Apps from Market simultaneously, like when there are updates for 5 or more products and you click OK on all of them.
normal daily operations has not shown any delay at all.
my only trick is i prevent any unwanted background services from starting with the phone.
i use the original lag fix that adds a logical link from /data/data to /dbdata.. have not read this causing any problems with corrupt sd cards as it is not changing partition type or anything.. the only drawback is the size is limited.. but as long as you dont install huge games i have over 100 apps with no problems ie..
not as high benchmarks as some of the others (but i belive they are artificial anyway) and the phone is fast and hardly ever lags..
try running k9-mail without it and it takes about 5 minutes to go through all my mailboxes versus about 30 sec.
C:\galaxy>cat speedtweak.sh
#!/system/bin/sh
## this script is made by deckcard##
## clean up csc folder
echo
echo Speed tweaks that move data from mmc to nand
echo
echo busybox cp -rp /data/data /dbdata >> /sdcard/1.sh
echo mv /data/data /data/data.bak >> /sdcard/1.sh
echo ln -s /dbdata/data /data/data >> /sdcard/1.sh
echo reboot >> /sdcard/1.sh
su</sdcard/1.sh
rm /sdcard/1.sh
theres tons of different fixes, some are better than others, but its all personal preference...and also, some of them just improve your quadrant score and not real life performance.
Hello,
I'm using my N7000 with CM 10.2-20131214 for about third month and it got pretty slow and laggy. This is becouse of leftovers from previous data.
Using AndroBench random write score is 0.28 MB/s 73.3 IOPS which is dramatically slow.
There is an app for cleaning this mess called LagFix but N7000 is not supported.
I was also trying to TRIM using Terminal Emulator with no resault.
Code:
[email protected]:/ $ su
[email protected]:/ # fstrim -v /system
fstrim -v /system
fstrim:FITRIM: Operation not supported on transport endpoint
Is there any kind of solution for this issue, or I just need to do formatting internal storage from time to time?
No, there is no way to enable trim on the device.
It could cause a superbrick if you did manage to activate it.
Azeazezar said:
No, there is no way to enable trim on the device.
It could cause a superbrick if you did manage to activate it.
Click to expand...
Click to collapse
Thanks for reply
Good that i didn't :<
Can formatting may be threat also?
Is it possible that this will be fixed in future?
Well, the fix is to disable what would cause a superbrick. (Which is why it failed in your case)
Completely fixing it, as far as i understand it, would requiring updating the EMMC firmware, which is risky, if not impossible.
You will just have to use the old garbage collection the chip has been using quite successfully. It seems to be doing fine.
No need for trim, or any special action on your part.
P.S.
Your random write speed is normal and identical to my own note.
Now, how often do you think random writing is bottle-necking your note?
It is likely something else that is the bottleneck.
My guess is that those guys at cyanogen are still using gpu clock speeds from the S2. I have not used that rom in a while, but i remember overclocking my lowest gpu step to 160 (from 100(CM), or 130(Stock) still nowhere near the top step that is 266) to give it a little boost.
I am not a developer, And i have not messed with that stuff for a while. So do your own research to what the problem is.
Azeazezar said:
My guess is that those guys at cyanogen are still using gpu clock speeds from the S2. I have not used that rom in a while, but i remember overclocking my lowest gpu step to 160 (from 100(CM), or 130(Stock) still nowhere near the top step that is 266) to give it a little boost.
I am not a developer, And i have not messed with that stuff for a while. So do your own research to what the problem is.
Click to expand...
Click to collapse
CyanogenMod uses 133MHz as the first GPU step for our note
yes, you can trim the n7000...
http://forum.xda-developers.com/gal...kernel-trim-speed-cyanogenmod-galaxy-t2875730
Hi all.
Have been modding and playing around with Note 4 and the emmc fault is a bi*ch. If it works, you never know when the damn thing will stop functioning. And the phone itself is always a bit buggy with custom roms. I noticed that several people here compare it to Note 3 and mean that Note 3 overall has certain advantages, easier to modd, less buggy, and of course, is not plagued with emmc fault. Don't get me wrong, i have several units and i really like the damn thing.
So i would like to ask all you who actually HAVE experience of both, write here a line or two, and compare those two. Which one is actually more thankfull for modding? N4 being of course newer, but does it make that big of a dirfference?
Hi, i don't have an note 3, i have and use a note 4, very happy with the phone running android 6.01 heavy customized and with the best kernel (ram Kernel v8.1 never had any issues with emmc or any other for that matter, it runs very smooth with no problems, battery last for a week, standby 0.4% per hour.
Ok. Difficult to make comparison then since you have no experience with Note 3, but thanx anyway.
Sounds good tho. May I ask then how your setup looks like, since having a battery last for a week is really an achievment?
System:
I Installed stock PHN DRI2 Build with ram Kernel v8.1 removed a lot of user apps that i don't need and also a lot of system apps that drain your battery, i use magisk for root and have two modules in use GPU Turbo Boost (not sure if this does anything but i leave it anyway installed) and Swap Torpedo (no swap file that saves battery) i use for tweaks the L Speed app and some build.prop tweaks most of them are from goldeneye rom.
Apps:
I use Ungoogled Chromium, this browser is memory and battery friendly as it does not call home all the time and i don't use social media apps as they are all battery hogs, i have about 50 apps installed and i use afwall for firewall and as email i use exchange push email with stock email client.
I tried almost every rom available for the note 4 910F but all suck in battery or the pen is not working, with a lot of trial and error in debloating the rom i stick with the one i have now, i am running it for 3 years and i am a happy camper. I love this phone with the pen the screen size and the exchangeable battery, it runs for a week with one charge 7 days with 3 hours and 43 minutes screen on, the onscreen time (backlight slider at 1/3 and dark color wallpaper) is about 7 hours in one go and it uses 0.4 battery per hour in standby (measured with GSam Battery Monitor since 1 year). I had newer phone they are all made of glass, no battery exchange and no earphone connector. Long story short, great phone . If you like to have the build.prop tweaks i can give them to you. The L speed app you can download from XDA https://forum.xda-developers.com/f/l-speed.6156/ .
Cheers
Qosmio- said:
System:
I Installed stock PHN DRI2 Build with ram Kernel v8.1 removed a lot of user apps that i don't need and also a lot of system apps that drain your battery, i use magisk for root and have two modules in use GPU Turbo Boost (not sure if this does anything but i leave it anyway installed) and Swap Torpedo (no swap file that saves battery) i use for tweaks the L Speed app and some build.prop tweaks most of them are from goldeneye rom.
Apps:
I use Ungoogled Chromium, this browser is memory and battery friendly as it does not call home all the time and i don't use social media apps as they are all battery hogs, i have about 50 apps installed and i use afwall for firewall and as email i use exchange push email with stock email client.
I tried almost every rom available for the note 4 910F but all suck in battery or the pen is not working, with a lot of trial and error in debloating the rom i stick with the one i have now, i am running it for 3 years and i am a happy camper. I love this phone with the pen the screen size and the exchangeable battery, it runs for a week with one charge 7 days with 3 hours and 43 minutes screen on, the onscreen time (backlight slider at 1/3 and dark color wallpaper) is about 7 hours in one go and it uses 0.4 battery per hour in standby (measured with GSam Battery Monitor since 1 year). I had newer phone they are all made of glass, no battery exchange and no earphone connector. Long story short, great phone . If you like to have the build.prop tweaks i can give them to you. The L speed app you can download from XDA https://forum.xda-developers.com/f/l-speed.6156/ .
Cheers
Click to expand...
Click to collapse
Thank you very much for the offer, but build props are way over my experience level, i think.
Btw, love the phone for the same reason as you do.
Besides, i am quite happy customer also, running @AnonVendetta s version of really bareboned stock 6.01. No Google, microG instead. No root. Not many apps. I probably could get a week out of a battery also with light use that i usually do. But i use Signal, and i just yesterday discovered that the damn thing just chugs battery like mad if you don't have Play Service installed. So with it installed i get at best a days use, with very light using of the phone.
I am currently rocking a Note 3 on Sprint and running Android 10 (Superior OS) and works great. All the convencience of Android with my removable battery and IR blaster (yes I use it for multiple TV's in multiple buildings I control). I use the S-Pen on Squid to take notes and jot down info and even mark up pictures so don't need Air Command. I sync with my FitBit Versa and run multiple smart home devices from the phone (including my whole home entertainment with the PEEL app).
The only 'complaint' I have is the bluetooth. There was a major problem past Android 7 of geting the thing to work. It does now. Voice and music work good. But occassionally it will just drop the device it connects to. I will re esablsih about 10 seconds later but still, that loses the lock on my Jeep radio and therefore keeps allowing the screen to lock. This is a minor annoyance but does need to be mentioned.
I JUST bought a Note 4 so thinking of loading LOS 17 on it and see how it goes. However I see most people here just kept stock Marshmellow. I dunno aobut that... isnt the UI buggy and limiting?
I look forward to any advice I can get!
Hi Dave,
I also use the IR remote for all my home appliance (dvbviewer TV on my pc, living room and bedroom tv and Bose audio system, i use the ir plus app great remote control app and it still gets updates, about the roms available for the note 4 i have the snapdragon version and i have tried all roms but i stay on stock 6.01 the MM version is not buggy at all, it never have problems, hangs crashes or reboots, i use the stock launcher smooth and fast, the UI interface is not important, the apps i use are all in dark mode, for me it's important i can use it the way i like it and it does. NOTE 4 still rocks like a champ with all the advantage it has. If this one breaks i will look for a other note 4, no newer phone for me. I dont know what version you have but try some rome you will see you will go back to 6.01 mm, its rock solid and battery friendly. Bluetooth on the note 4 sucks for battery use but does not crash or breaks anything, i have a gear fit2 pro but i dont connect it with the phone all the time just to sync .
Cheers
Unidave199 said:
I am currently rocking a Note 3 on Sprint and running Android 10 (Superior OS) and works great. All the convencience of Android with my removable battery and IR blaster (yes I use it for multiple TV's in multiple buildings I control). I use the S-Pen on Squid to take notes and jot down info and even mark up pictures so don't need Air Command. I sync with my FitBit Versa and run multiple smart home devices from the phone (including my whole home entertainment with the PEEL app).
The only 'complaint' I have is the bluetooth. There was a major problem past Android 7 of geting the thing to work. It does now. Voice and music work good. But occassionally it will just drop the device it connects to. I will re esablsih about 10 seconds later but still, that loses the lock on my Jeep radio and therefore keeps allowing the screen to lock. This is a minor annoyance but does need to be mentioned.
I JUST bought a Note 4 so thinking of loading LOS 17 on it and see how it goes. However I see most people here just kept stock Marshmellow. I dunno aobut that... isnt the UI buggy and limiting?
I look forward to any advice I can get!
Click to expand...
Click to collapse
For me LOS17 was a no go because of the SIM issue and lack of encryption. I saw other having other issues. If i were you and needed something newer than marshmallow, then i would try LOS16. I found that one to be very stable, no issues so far for my use. Will perhaps migrate to that one with my daily driver in a while, when stock starts failing.
As for stock 6.0.1, not sure where you heard it was buggy?! I read that marshmallow was if not the least buggy Android OS ever and that is also my experience, at least on Note 4. I totally agree with @Qosmio-. It is the most rock solid rom i have ever had on a device. NEVER had any bugs, issues or anything. Battery friendly. I find launcher smooth, and run UI in 'easy mode', which i find the most appealing, colorwise and all. The perfect OS basically, if there ever was one. I have heard people starting to find apps that are no longer supported, but all apps that are important to me still work.
but wait - you use PEEL app as remote?
Wasn't that completely hidious advertisment-prone bloatware that was utterly unpleasant to use?
prkfsz said:
but wait - you use PEEL app as remote?
Wasn't that completely hidious advertisment-prone bloatware that was utterly unpleasant to use?
Click to expand...
Click to collapse
I only meant 'buggy' as outdated and unable to use the full Google Assistant features etc... Thats why I moved to newer ROMS Not as smooth and primitive features. I should try myself before I speak the negative about it!
So let's talk about PEEL.
The magic is to use this with Titanium Backup. I must say, PEEL can be set up to use and manage "scenarios" (Home, Work, Friend's House etc). If you set it up..
1.go in and click to NOT auto detect WiFi connections
2.disable advertising and lock screen and persistant notifications for 30 days.
3. Set up a Custom Remote Scenario
4. Create a Widget for the App to default on Custom Remote
3. Do a TB of the app!
I have found, on the newer ROM's it stays Ad Free.. but if it gets weird to annoying just do a TB restore "data only" and then you are golden!
Ive tried lots of other 3rd party apps but I keep going back to PEEL. It stays ad free and as a remote (not as a channel guide) it works exremely well, is desined well and functions well.
Hit me up if you want more specifics! Maybe I should start a 'how to' thread..
Dave
Qosmio- said:
i stay on stock 6.01 the MM version is not buggy at all, it never have problems
Click to expand...
Click to collapse
Arent you worried about Security Updates?
Unidave199 said:
Arent you worried about Security Updates?
Click to expand...
Click to collapse
No not at all, i protect my use of internet at home and phone ( i am system engineer for 35 years so i know what i can and can't do), if you look what still need to be patched for android Exploits vulnerability-list , every new or old version of android user is @ risk. When connected with my phone to internet via my provider it will change the phones ip address every 15 minutes, i use a firewall (afwall) on my phone and disabled ipv6, i am connected to my home with openvpn to pfsense firewall for internet access and i use my own MS exchange mail server and dns server resolver with ad and privacy telemetry filter with pfblocker. There are things you don't do with old version of android and that is visite websites that are shady, porn websites and browse without a strong ad blocker or privacy filter.
Qosmio- said:
System:
I Installed stock PHN DRI2 Build with ram Kernel v8.1
Click to expand...
Click to collapse
So I did it! I made the jump. I am using the Q15 Plus Tidbits VB3 Rom. And udated firmware. Do you have a link to the ROM you are using?
Unidave199 said:
So I did it! I made the jump. I am using the Q15 Plus Tidbits VB3 Rom. And udated firmware. Do you have a link to the ROM you are using?
Click to expand...
Click to collapse
Wel since 2 weeks some government (tax/digi id ect) apps we use in nl does not support android 6 anymore and i use them often so i had to jump to android 10 and using this rom Crdroid
If you like to try don't download from first page but from here Mega
I use it for a week now (with some tweaks) and this is the only android 10 rom that works and looks great, battery is not as good as with android 6 but i have to accept that, i am not ready yet to dump the note 4.
Cheers
Qosmio- said:
Wel since 2 weeks some government (tax/digi id ect) apps we use in nl does not support android 6 anymore and i use them often so i had to jump to android 10 and using this rom Crdroid
Click to expand...
Click to collapse
I had tried using some Liniage Versions but on the Sprint Variant they woulnt make phone calls or text so I had to ditch them. I am downloading now so will give it a flash and see! Thank you for the heads up!
Dave
EDIT
Ok.. loaded up the Crdroid ROM. Working well, but with my SM 910P I am having bluetooth problems keeping sync with my Fitbit, Lack of LTE (but works on 3G) and a few other bugs but am managing. What carrier are you with? I would appreciate any tweeks you have found to help out.
Dave
Unidave199 said:
I had tried using some Liniage Versions but on the Sprint Variant they woulnt make phone calls or text so I had to ditch them. I am downloading now so will give it a flash and see! Thank you for the heads up!
Dave
EDIT
Ok.. loaded up the Crdroid ROM. Working well, but with my SM 910P I am having bluetooth problems keeping sync with my Fitbit, Lack of LTE (but works on 3G) and a few other bugs but am managing. What carrier are you with? I would appreciate any tweeks you have found to help out.
Dave
Click to expand...
Click to collapse
Hi Dave,
Sorry for the late reply, i just read your post in the cdroid section, i am with simpel carrier i dont have any problems using LTE and have no problem with sms (i dont use mms) , the only tweaks is with the L speed app and kernel auditor to lower the idle frequentie of the GPU and set it to 166 instead of 240 to save battery. My gear fit2 pro on bluetooth works fine to so i am a happy camper. What you could try is other modems from other stock roms if you did not try that already maybe that helps with you LTE problem.
Cheers
Qosmio- said:
Hi Dave,
Sorry for the late reply, i just read your post in the cdroid section, i am with simpel carrier i dont have any problems using LTE and have no problem with sms (i dont use mms) , the only tweaks is with the L speed app and kernel auditor to lower the idle frequentie of the GPU and set it to 166 instead of 240 to save battery. My gear fit2 pro on bluetooth works fine to so i am a happy camper. What you could try is other modems from other stock roms if you did not try that already maybe that helps with you LTE problem.
Cheers
Click to expand...
Click to collapse
Sorry for all the bouncing around in the forums. Trying to play Note 4 catchup...
Well that is an interesting thought. As a CDMA carrier customer (Sprint) I feel I am locked into my own island.
Can I just do a stock modem restore in TWRP onto my CRDroid ROM ? I am not at all sure why my Bluetooth is having such a problem with my Versa 2.. Maybe it is the versa problem?
Anyways, I can see a bit where the Note 4 gets laggy with camera use and running a few other commands at once. I know this is older but my Note 3 did not seem to hesatate this much. I like the idea of considering lowering my GPU.
Let me know if you have any other thoughts?
Dave
Np Dave there is so much information to take in that i can't blame you when bouncing aroubnd in the forum , You can and must make a backup with twrp of your modem in use and then fiddle around with different versions, its very easy to rip modems with 7zip from different original roms and zip (7zip) them to flash it with twrp. As for bluetooth it can be a pain in the ass with custom roms especially with asop roms, do some searches in the forum maybe someone has the same issue as you have.
Cheers
Qosmio- said:
. As for bluetooth it can be a pain in the ass with custom roms especially with asop roms, do some searches in the forum maybe someone has the same issue as you have.
Cheers
Click to expand...
Click to collapse
I found a forum that says to go into the application and wipe data and cache and then I went into TWRP and wiped ART/Cache. That seems to help with the 'Bluetooth Keeps Stopping" error. I have tried to load several other ROM's but they wont install due to Error 7 codes. I supsect becuase I updated to the Q15 version and these older ROMS arent being updated. So I will keep trying to nurse the CrDroid 10 version and see if it can be improved..
I'm not an expert but for me.. note 3 is more stabLe than note 4 when it comes to custom rom. Easier to mod, and Less buggy. ( thanks to aLL deveLopers at kay Lodi @jprimero15 )
TiLL now stiLL Looking for a rom that can fit note 4 for daiLy usage.
Thanks
I am using Emotion Kernel, and Xposed. I will just to Android 12 at the moment it will be available.
I never used the Note 3, but i wonder is it faster than the Note 4 in daily usage. The Note 4 Snapdragon CPU is a frying pan and it can strongly reduce its performance when it gets hot.
My phone will in consequence randomly reboot, but i have a simple script that detects overheating and lower the CPU freq (works good)
Is the Note 3 quick and doesn't overheat when browsing internet?
Hello. I recently stupidly flashed RC29 on my phone. That's how I got out of there.
How to:
1. You realized that you are on RC29. Do not worry. Let's start the escape.
2. Start phone without sim card. Type on the keyboard <ENTER button>setprop persist.service.adb.enable 1<ENTER button>. Reboot with a SIM card (any, not even a valid one)
3. Connect your phone to PC, download ADB and type command: adb shell am start -a android.intent.action.MAIN -n com.android.launcher/.Launcher
4. Download and install telnet: adb install telnet.apk
4.1 Once at the Home screen, open the keyboard and press the Enter key twice.
4.2 Type telnetd & press Enter. The Contacts screen will come up, just ignore it. There will be no indication that you did it right.
4.3 Open Android Telnet Client; type localhost in the large text box and 23 in the smaller text box on the right.
5. Download the recovery to a memory card and type the command in telnet:
flash_image recovery /sdcard/<your recovery>.img
Just type reboot recovery! Now you have a complete Recovery!
6. WARNING! Install 2.22.19.26I and reboot into recovery 2-3 times. Check the radio version in HBOOT. If version 2.22.19.26I install the HBOOT package. Reboot 2-3 times.
7. It's all. Install roms.
Pay attention! Clockworkmod is not recommended by Cyanogen developers. Use AmonRa. (cwm recovery left in the post in case of emergency)
The story of how I installed CyanogenMod 7:
1. Download CyanogenMod 7 build (DM me if rom not downloading)
2. Install HBOOT 1.33.0013d
3. Install ROM. Download the kernel (ezgb_2636_v1.5.1_S.zip). Install kernel.
4. Just restart and wait. Now you have working system!
Notes:
Restart in recovery - HOME + POWER
Restart in HBOOT - PHOTO + POWER
Reset - CALL + MENU + POWER
Safe mode - hold MENU while booting
# sites (not all)
HTC Dream: Rooting - CyanogenMod Wiki
web.archive.org
Google Code Archive - Long-term storage for Google Code Project Hosting.
code.google.com
Please buy the HTC Sensation
I alone am bored in the forum Sensation
It can be found for 500 rubles
Ulumia said:
Please buy the HTC Sensation
I alone am bored in the forum Sensation
It can be found for 500 rubles
Click to expand...
Click to collapse
sorry, even though it costs 500rub, I spent everything on MiPad 2. I don’t have money for it. Sorry((
PS. and notice. I am now trying to bypass android and make my firmware on android 1.0 for dream.
I quote the article on rooting G1 from Cyanogen Wiki "ClockworkMod is not recommended for Dream due to memory shortage and file corruption."
That's why I think it's better to use Amon_RA's
On my Desire Amon_RA 2.0.1 seems better than CWM 2.5.0.7
Below you can find CyanogenMod themed version of Recovery
By the way the new Telnet version is already on Mod edit: 4pda link removed
@russanandres Thanks a lot for the tutorial, you are a real lifesaver! Exactly what I needed to get a custom rom on my G1.
Although now I'm wondering, is android 2.3 perhaps too much for this phone? I was shocked to see that the actual usable ram out of the 192mb is just 96 and out of them ~30mb free. The device itself seems to be somewhat sluggish on 2.3, the default browser can't even load google without crashing. Although I noticed it's kinda inconsistent, sometimes it speeds up a bit and gets pretty close to 1.6 speed. On the stock 1.6 the phone was fairly snappy for what it could do, although it had terrible idle battery drain. The battery on 2.3 seems better from my first impressions.
For daily driver usage in 2022 what would make most sense, if you have experience with more roms on this device? 2.3 just really seems pointless to me, as the device doesn't have enough power to run properly apps that require android 2.3 as minimum, pretty much all apps that I have installed run on 1.5/1.6+. For example, I have my music library in .opus format, tried foobar2000 and gonemad music player(they supposedly support opus) versions that are 2.3+ and they both straight up crashed on startup, perhaps due to the low ram/lack of instructions.
The speed itself doesn't annoy me as much as the soft reboots that happen from time to time when the phone gets too ''tired'', especially after reboot, for me in about 50% of the time the phone just soft reboots again like a half minute after the first reboot.
Edit: The reboots after the bootup happen if I just don't let it idle for 2 minutes or so white it's reading my sdcard, which has quite a lot of files. I doubt it's from the actual speed of the sdcard as it's a 16gb sandisk ultra, should be sufficient for this phone.
A slight overclock option seems to be present in the performance settings but I won't dare to use it, two days ago I had to do a somewhat professional solder reflow+SoC heat revive on 400C for 30 seconds with a bga soldering station and some flux, that brought it back to life, previously it would work only for about an hour after I heated it with a hairdryer. My point is that the processors in these devices haven't aged too well, in terms of wearing out mine is pretty much done for and who knows when it's gonna die again. I also managed to put a copper heat plate over the soc(with thermal paste) to absorb some of the heat in addition to the metal plating and hopefully to increase the remaining lifespan of the silicon.
Back on the topic, maybe android 2.1/2.2 would be more suitable and still with good features(mostly looking at the quick settings), although I have no idea honestly, I haven't played around with android versions this old to know which ones are lighter and heavier. 2.3 definitely seems heavier than 1.6, that is for sure.
Availability in terms of links is another issue but with research and some use of the web archive I suppose we would be able to find at least one rom per android version.
MaRtYy01 said:
@russanandres Thanks a lot for the tutorial, you are a real lifesaver! Exactly what I needed to get a custom rom on my G1.
Although now I'm wondering, is android 2.3 perhaps too much for this phone? I was shocked to see that the actual usable ram out of the 192mb is just 96 and out of them ~30mb free. The device itself seems to be somewhat sluggish on 2.3, the default browser can't even load google without crashing. Although I noticed it's kinda inconsistent, sometimes it speeds up a bit and gets pretty close to 1.6 speed. On the stock 1.6 the phone was fairly snappy for what it could do, although it had terrible idle battery drain. The battery on 2.3 seems better from my first impressions.
For daily driver usage in 2022 what would make most sense, if you have experience with more roms on this device? 2.3 just really seems pointless to me, as the device doesn't have enough power to run properly apps that require android 2.3 as minimum, pretty much all apps that I have installed run on 1.5/1.6+. For example, I have my music library in .opus format, tried foobar2000 and gonemad music player(they supposedly support opus) versions that are 2.3+ and they both straight up crashed on startup, perhaps due to the low ram/lack of instructions.
The speed itself doesn't annoy me as much as the soft reboots that happen from time to time when the phone gets too ''tired'', especially after reboot, for me in about 50% of the time the phone just soft reboots again like a half minute after the first reboot.
Edit: The reboots after the bootup happen if I just don't let it idle for 2 minutes or so white it's reading my sdcard, which has quite a lot of files. I doubt it's from the actual speed of the sdcard as it's a 16gb sandisk ultra, should be sufficient for this phone.
A slight overclock option seems to be present in the performance settings but I won't dare to use it, two days ago I had to do a somewhat professional solder reflow+SoC heat revive on 400C for 30 seconds with a bga soldering station and some flux, that brought it back to life, previously it would work only for about an hour after I heated it with a hairdryer. My point is that the processors in these devices haven't aged too well, in terms of wearing out mine is pretty much done for and who knows when it's gonna die again. I also managed to put a copper heat plate over the soc(with thermal paste) to absorb some of the heat in addition to the metal plating and hopefully to increase the remaining lifespan of the silicon.
Back on the topic, maybe android 2.1/2.2 would be more suitable and still with good features(mostly looking at the quick settings), although I have no idea honestly, I haven't played around with android versions this old to know which ones are lighter and heavier. 2.3 definitely seems heavier than 1.6, that is for sure.
Availability in terms of links is another issue but with research and some use of the web archive I suppose we would be able to find at least one rom per android version.
Click to expand...
Click to collapse
I think a swap of 256 MB or more will save your G1 on 2.3.7
So if 2.3.7 was slow, then any Android 2.x.x will be slow
Within 2.x.x the system showed more and more performance with each version
Ulumia said:
I think a swap of 256 MB or more will save your G1 on 2.3.7
So if 2.3.7 was slow, then any Android 2.x.x will be slow
Within 2.x.x the system showed more and more performance with each version
Click to expand...
Click to collapse
That's a great idea. I have to look into it, as far as I know I have to make a partition for the swap on the sdcard then enable it on boot with some sort of a script. Is that correct?
Guess that's what I'm gonna be doing today after work, apart from transcoding my music library to mp3 unless the music players decide to work with the swap enabled.
Another thing I wanted to mention, is it normal to have such high idle drain on this phone? Even on cm7 in airplane mode it seems to drain ~4-5% per hour or so. Perhaps my battery calibration is off, I charged it overnight and wiped the battery stats hoping to resolve this issue but it seems to persist. I got a nearly brand new vhbw aftermarket battery which should be about 900-950mah capacity from my measurements, so it's not due to an aging battery.
In comparision I also have a galaxy s1 on cm7.2 with a 12 year old battery on ~70% capacity and that phone lasts like 10 days idle with a sim card.
MaRtYy01 said:
That's a great idea. I have to look into it, as far as I know I have to make a partition for the swap on the sdcard then enable it on boot with some sort of a script. Is that correct?
Guess that's what I'm gonna be doing today after work, apart from transcoding my music library to mp3 unless the music players decide to work with the swap enabled.
Another thing I wanted to mention, is it normal to have such high idle drain on this phone? Even on cm7 in airplane mode it seems to drain ~4-5% per hour or so. Perhaps my battery calibration is off, I charged it overnight and wiped the battery stats hoping to resolve this issue but it seems to persist. I got a nearly brand new vhbw aftermarket battery which should be about 900-950mah capacity from my measurements, so it's not due to an aging battery.
In comparision I also have a galaxy s1 on cm7.2 with a 12 year old battery on ~70% capacity and that phone lasts like 10 days idle with a sim card.
Click to expand...
Click to collapse
Swap partition can be done directly in CWM
You need to find Partion SDcard!!! ALL DATA ON THE SD WILL BE REMOVED!!!
For swap you can use this script
Code:
busybox mkswap /dev/block/mmcblk0p3
busybox swapon /dev/block/mmcblk0p3
echo 100 > /proc/sys/vm/swappiness
And about the battery: on all the HTC smartphones that I had (Sensation XE, Desire A8181, Wildfire S) it has been bad since
So try to replace it.
Ulumia said:
Swap partition can be done directly in CWM
You need to find Partion SDcard!!! ALL DATA ON THE SD WILL BE REMOVED!!!
For swap you can use this script
Code:
busybox mkswap /dev/block/mmcblk0p3
busybox swapon /dev/block/mmcblk0p3
echo 100 > /proc/sys/vm/swappiness
And about the battery: on all the HTC smartphones that I had (Sensation XE, Desire A8181, Wildfire S) it has been bad since
So try to replace it.
Click to expand...
Click to collapse
I see, thanks for the explanation.
I'll hold off from getting a new battery for now, hoping that this battery will get better calibrated. I'm also not certain that the problem is in the battery, if I use the device non-stop from full charge it seems to hold on for about 1h45mins SoT before going flat, which for a device with a tiny battert and a 65nm soc doesn't seem unusual.
But I was also wondering about your experience with the battery, do you also get this high idle drain or is it just my unit?
Lastly, I was wondering if multitouch can be enabled somehow. From my quick search it appears that the G1 screen supports it but its purposely disabled, although some people show it off being enabled.
MaRtYy01 said:
I see, thanks for the explanation.
I'll hold off from getting a new battery for now, hoping that this battery will get better calibrated. I'm also not certain that the problem is in the battery, if I use the device non-stop from full charge it seems to hold on for about 1h45mins SoT before going flat, which for a device with a tiny battert and a 65nm soc doesn't seem unusual.
But I was also wondering about your experience with the battery, do you also get this high idle drain or is it just my unit?
Lastly, I was wondering if multitouch can be enabled somehow. From my quick search it appears that the G1 screen supports it but its purposely disabled, although some people show it off being enabled.
Click to expand...
Click to collapse
The G1 supports multi-touch
It's very strange why it's not in CM7
Xperia X8 has multitouch on the custom ROM but no multitouch on the stock ROM
I found a better opmitized gingerbread rom, that still has a working link.
The system runs much smoother than on cm7.
I have to add, something missed in the tutorial is updating the radio to an even newer version that expands the available ram by 15mb. That is like 50%, considering that the phone has 30mb ram free otherwise.
Link for the radio- here
I directly updated to 2.22.28.25_S via recovery and faced no issues. It is recommended to use superwipe first, with a custom configuration file in the root of the sdcard, that will do a full wipe except for the sdcard. (Source) (Source 2)
In the custom config set:
Wipe_Sd_Secure=no
Wipe_Sd_Ext=no
I received a new sdcard that I will use for the phone, a 64gb Patriot EP series that I got for 5€, these are very fast and dirt cheap. Probably faster than the phone's sdcard reader can candle but that is fine. Point is, I ran the partition sdcard option in the recovery, I noticed it doesn't only ask for swap but it also asks for ext2 partition, what capacity should I select for that? Can't find much info for the ext2 parititions other than they are used for moving apps to the sdcard, although I have no clue how to enable that ability in the android os.
As for my battery issues, I'm certain that the culpit isn't software related but rather a failure of the Qualcomm PM7540 power management ic. The easiest way to test that, which I did, turn off the phone and wait, if the chip is fautly it will drain the battery while it is off, which it does for me(there is nearly no difference in discharge speed between the phone being on and off). I actually remember a year ago when the phone was still just sitting as a decoration on my shelf and just turned on with the hairdryer from time to time, that I had to pull out the battery or it would drain it completely while off, so the power ic failure isn't related to the processor failure at all. I don't know what is my luck, to have 2 dying important chips on one board
Perhaps I will try to remedy it the same way I did with the processor, clean it, place some flux and heat it for 30 secs at 400C. Or maybe a bit lower temperature this time. Technically both chips can be replaced and finding a donor isn't hard(especially for the power management ic, it appears that HTC HD2, Touch HD, Nexus One, Touch Pro, Diamond 2, Desire, SE Xperia X10, X10 Mini, BlackBerry Storm are only part of the devices that use this same power ic. But replacing such chips is extremely difficult and beyond my current abilities, giving it to a professional is not worth it either, the entire phone costs 40-50€(as collector's value) so with the cost of such repair I can instead purchase another G1.
Thank, it work fine
MaRtYy01 said:
I found a better opmitized gingerbread rom, that still has a working link.
The system runs much smoother than on cm7.
I have to add, something missed in the tutorial is updating the radio to an even newer version that expands the available ram by 15mb. That is like 50%, considering that the phone has 30mb ram free otherwise.
Link for the radio- here
I directly updated to 2.22.28.25_S via recovery and faced no issues. It is recommended to use superwipe first, with a custom configuration file in the root of the sdcard, that will do a full wipe except for the sdcard. (Source) (Source 2)
In the custom config set:
Wipe_Sd_Secure=no
Wipe_Sd_Ext=no
Click to expand...
Click to collapse
To flash That radio do i need to install the SPL "1.33.0013d"?
or i can keep using Danger SPL (1.33.2005)?
@Ulumia you know anything about this? is the "RAM Hack" SPL required?
jonnyprogamer said:
To flash That radio do i need to install the SPL "1.33.0013d"?
or i can keep using Danger SPL (1.33.2005)?
Click to expand...
Click to collapse
I don't know anything about Dream because I don't have this device.
I think if you need that file, you know what to do to install it.
jonnyprogamer said:
To flash That radio do i need to install the SPL "1.33.0013d"?
or i can keep using Danger SPL (1.33.2005)?
Click to expand...
Click to collapse
Hey sorry for my late response, I just fired up my G1 which to my surprise(or not) failed to cold boot yet again so I had to give it the hair dryer treatment. Guess the hot air station fix worn out at some point after I stopped using the phone 2 weeks after applying it.
I have 1.33.0013d on mine, which appears to be the recommended version. looking at the description of the rom. I would avoid using another one if possible. Unfortunately I don't remember anything specific, so I can't give you more feedback.
MaRtYy01 said:
Hey sorry for my late response, I just fired up my G1 which to my surprise(or not) failed to cold boot yet again so I had to give it the hair dryer treatment. Guess the hot air station fix worn out at some point after I stopped using the phone 2 weeks after applying it.
I have 1.33.0013d on mine, which appears to be the recommended version. looking at the description of the rom. I would avoid using another one if possible. Unfortunately I don't remember anything specific, so I can't give you more feedback.
Click to expand...
Click to collapse
As i found out you need that SPL to get the extra 15MB of Ram, but be aware that SPL is pretty dangerous, because it doesn't support Fastboot flash (and fastboot boot doesn't work, gets stuck when i try to boot recovery), so if you accidentally brick your phone and do not have a custom recovery it's RIP.
hello
i've never downgraded/flashed any firmware on this device before, so before i do something that might be fatal/result in bricking my phone i would like to ask is it possible to downgrade a S20 FE android 13 to android 11? while my one ui version is 5.1 i haven't updated the security patch to the april one (the one that changes your binary) it's currently the 1 march 2023 one
i've already checked & downloaded a firmware with the correct binary number so now all i need to do is flash it
Welcome to XDA.
You're limited by the bootloader version to how far you can roll it back. If the bootloader was upgraded too, you're boned. The 5th digit from the rear is the significant digit that determines that. If the rom's 5th digit is the same or higher value you can flash it. If lower, no go.
kiyan_ said:
hello
i've never downgraded/flashed any firmware on this device before, so before i do something that might be fatal/result in bricking my phone i would like to ask is it possible to downgrade a S20 FE android 13 to android 11? while my one ui version is 5.1 i haven't updated the security patch to the april one (the one that changes your binary) it's currently the 1 march 2023 one
i've already checked & downloaded a firmware with the correct binary number so now all i need to do is flash it
Click to expand...
Click to collapse
Hi, I downgraded my S20 FE several times from 13 to 12 with the same binary (obviously) with no issues at all, so you can downgrade easily.
In my experience on samsung devices (literally I flashed a hundred times on different devices) it's very unlikely that you brick your device with odin, even if you use a wrong firmware for your device....the only thing that it may brick a device is because it has a hardware damage
rgrapow said:
Hi, I downgraded my S20 FE several times from 13 to 12 with the same binary (obviously) with no issues at all, so you can downgrade easily.
In my experience on samsung devices (literally I flashed a hundred times on different devices) it's very unlikely that you brick your device with odin, even if you use a wrong firmware for your device....the only thing that it may brick a device is because it has a hardware damage
Click to expand...
Click to collapse
Hello
This will depend on your variant.
on the G780G (binary 3) and G781B (binary 4)
You can download to android 11.
since it has the same binary.
Of course, you should do it from 0.
do not install via CSC_HOME.
The installation must be clean.
before all make backup.
blackhawk said:
Welcome to XDA.
You're limited by the bootloader version to how far you can roll it back. If the bootloader was upgraded too, you're boned. The 5th digit from the rear is the significant digit that determines that. If the rom's 5th digit is the same or higher value you can flash it. If lower, no go.
Click to expand...
Click to collapse
yes it is the same value
mine G780GXXU3EWB2
the firmware i downloaded G780GXXU3AUH5
which would make both binaries '3' right? would this be okay?
rgrapow said:
Hi, I downgraded my S20 FE several times from 13 to 12 with the same binary (obviously) with no issues at all, so you can downgrade easily.
In my experience on samsung devices (literally I flashed a hundred times on different devices) it's very unlikely that you brick your device with odin, even if you use a wrong firmware for your device....the only thing that it may brick a device is because it has a hardware damage
Click to expand...
Click to collapse
thank you for your answer & sharing your experience, this is what i've been looking for
kiyan_ said:
yes it is the same value
mine G780GXXU3EWB2
the firmware i downloaded G780GXXU3AUH5
which would make both binaries '3' right? would this be okay?
Click to expand...
Click to collapse
since it has the same binary.
Of course, you should do it from 0.
do not install via CSC_HOME.
The installation must be clean.
before all make backup.
rgrapow said:
the only thing that it may brick a device is because it has a hardware damage
Click to expand...
Click to collapse
Or if the battery has insufficient charge or capacity. Any time you flash a device you take some level of risk. A power outage with no or insufficient battery backup for the PC would also end badly.
The risk is also greater with Androids because it's not a small couple dozen MB flash that's done in seconds. Lots more time and data for things to go wrong. If my Canon pro cam had a bad flash, Canon would likely repair for free or a reasonable charge. Samsung will do neither of these... repair cost plus a new mobo loaded with the latest firmware. perfect.
mezacorleehone said:
on the G780G (binary 3)
Click to expand...
Click to collapse
yes that is my phone variant
mezacorleehone said:
do not install via CSC_HOME.
Click to expand...
Click to collapse
may i ask why is that?
kiyan_ said:
yes that is my phone variant
may i ask why is that?
Click to expand...
Click to collapse
the CSC_HOME file
comes in the software you just downloaded.
unlike normal CSC.
The CSC_HOME is used to only update the system, without deleting anything.
in your case you are going to downgrade, use the normal CSC without _home.
thank you everyone for the help & answers
kiyan_ said:
thank you everyone for the help & answers
Click to expand...
Click to collapse
You are welcome.
where possible we collaborate.
blackhawk said:
Or if the battery has insufficient charge or capacity. Any time you flash a device you take some level of risk. A power outage with no or insufficient battery backup for the PC would also end badly.
The risk is also greater with Androids because it's not a small couple dozen MB flash that's done in seconds. Lots more time and data for things to go wrong. If my Canon pro cam had a bad flash, Canon would likely repair for free or a reasonable charge. Samsung will do neither of these... repair cost plus a new mobo loaded with the latest firmware. perfect.
Click to expand...
Click to collapse
I'm referring about samsung devices based on my experience (trial and error), I had a lot of bricks, soft bricks and I was able to solve it with odin.
kiyan_ said:
yes it is the same value
mine G780GXXU3EWB2
the firmware i downloaded G780GXXU3AUH5
which would make both binaries '3' right? would this be okay?
Click to expand...
Click to collapse
Yes, exactly. Why do you want to roll it back?
If it's a specific issue finding a work around may be easier.
Android 11 is no picnic either. I prefer Pie, Android 10 is ok; I'm running both and will likely never upgrade them.
Regardless you will need to lock it down so it can't do OTA upgrades/updates. That's the first thing I do on my Samsung's... once bitten, twice shy Upgrades and updates can and do break Samsung's... then you have find work arounds and fixes.
blackhawk said:
Yes, exactly. Why do you want to roll it back?
If it's a specific issue finding a work around may be easier.
Android 11 is no picnic either. I prefer Pie, Android 10 is ok; I'm running both and will likely never upgrade them.
Regardless you will need to lock it down so it can't do OTA upgrades/updates. That's the first thing I do on my Samsung's... once bitten, twice shy Upgrades and updates can and do break Samsung's... then you have find work arounds and fixes.
Click to expand...
Click to collapse
other than battery run out faster & the phone feeling a bit sluggish nothing specific....it's just i've already debloated my phone & disabled many features of the phone that i dont use and dont plan on updating my phone anymore and while that does help improve things quite significantly i just thought at this point why dont i just might aswell downgrade the phone
before i had this phone i was fine staying years with a phone that stopped receiving updates after android 6 lol just that it eventually ran its course and after several hardware problems & the phone giving up by itself (every 3 weeks or so it'll get stuck on bootloop for no reason) i assume it was time for me to buy a new one...too bad
rgrapow said:
I'm referring about samsung devices based on my experience (trial and error), I had a lot of bricks, soft bricks and I was able to solve it with odin.
Click to expand...
Click to collapse
I'm glad that's working well for you. I use to always be playing with my PC's like that. With Androids I took a more conservative approach; less down time, more play time.
I leave the firmware be on my 2 stock N10+'s. They run very good, fulfill their mission and it's simply not worth the risk or time. I don't allow firmware upgrades or updates. This N10+ in my hand is still running on Pie, firmware is 3.5 yo, and the current load will be 3 yo this June. No malware in all that time; security isn't an issue. Still fast, very stable with minimal maintenance. It's also heavily optimized and running well; I have zero incentive to change the playing field by altering the firmware.
My SQlite scores are lower than they should be in spite of my fast disk r/w scores so eventually I may do a factory reset to try to resolve that. Lol, that's the full extent of my ambition at the moment.
blackhawk said:
Upgrades and updates can and do break Samsung's... then you have find work arounds and fixes.
Click to expand...
Click to collapse
yep. i learned the hard way
i'm quite green at this stuff and at first i just thought "more upgrades & updates means good! i should get the most out of this device" but alas after some serious overheating & battery draining problems over loads of features i dont even use.....
kiyan_ said:
other than battery run out faster & the phone feeling a bit sluggish nothing specific....it's just i've already debloated my phone & disabled many features of the phone that i dont use and dont plan on updating my phone anymore and while that does help improve things quite significantly i just thought at this point why dont i just might aswell downgrade the phone
before i had this phone i was fine staying years with a phone that stopped receiving updates after android 6 lol just that it eventually ran its course and after several hardware problems & the phone giving up by itself (every 3 weeks or so it'll get stuck on bootloop for no reason) i assume it was time for me to buy a new one...too bad
Click to expand...
Click to collapse
Anything below Android 9 is suspectable to partition worming nasties like Xhelper. Run Android 9 or higher. Android 9 is relatively secure unless you do stupid things.
All Samsung's should be optimized. You will still have scoped storage running on Android 11 anyway. If you don't mind the UI of Android 13 I would try to find what's causing the issues.
Disable global power management then go after the power hogs on an individual case by case basis. A logging firewall is useful in finding them. Cloud, and social media apps are prime offenders. Try temporarily disabling Google play Services and see if this helps; Google backup Transport, Gmail and Playstore are dependencies of it. Enable as needed. 5G can also suck a lot of power and is inefficient when doing small bandwidth transfers. Wifi isn't needed if you have an unlimited data plan. Use Package Disabler or abd/ladb edits to take out the really problem apps that can't be resolved in settings. Don't go too nuts though; target the hogs and totally worthless apps like Digital Wellbeing. Most of the dozens a small Samsung system apps are best left alone as many modify the UI and consume very little resources. Understand what the app does and it's dependencies if any before disabling whenever possible.
Play with it...
blackhawk said:
Anything below Android 9 is suspectable to partition worming nasties like Xhelper. Run Android 9 or higher. Android 9 is relatively secure unless you do stupid things.
All Samsung's should be optimized. You will still have scoped storage running on Android 11 anyway. If you don't mind the UI of Android 13 I would try to find what's causing the issues.
Disable global power management then go after the power hogs on an individual case by case basis. A logging firewall is useful in finding them. Cloud, and social media apps are prime offenders. Try temporarily disabling Google play Services and see if this helps; Google backup Transport, Gmail and Playstore are dependencies of it. Enable as needed. 5G can also suck a lot of power and is inefficient when doing small bandwidth transfers. Wifi isn't needed if you have an unlimited data plan. Use Package Disabler or abd/ladb edits to take out the really problem apps that can't be resolved in settings. Don't go too nuts though; target the hogs and totally worthless apps like Digital Wellbeing. Most of the dozens a small Samsung system apps are best left alone as many modify the UI and consume very little resources. Understand what the app does and it's dependencies if any before disabling whenever possible.
Play with it...
Click to expand...
Click to collapse
i've done all that hahahah
other than youtube i don't have any other social media apps installed and i've already got rid of chrome & switched to a lighter browser
yep i like to experiment, i suppose the flashing stuff is the next step after all of that (yes have tried factory reset several times too, i don't mind as there aren't any important data in my phone but still, possibly getting a priceful item bricked over my messing around isn't something i'm too excited about, that's why i still like to ask around)
also what got me the idea was that i've also read from several people with the same device saying that with every android updates the phone gets even more sluggish
kiyan_ said:
yep. i learned the hard way
i'm quite green at this stuff and at first i just thought "more upgrades & updates means good! i should get the most out of this device" but alas after some serious overheating & battery draining problems over loads of features i dont even use.....
Click to expand...
Click to collapse
I learned the hard way with Samsung's too.
After the upgrade to 13 did you do a factory reset? If not, now is the time. Don't use SmartSwitch; do a clean load by importing all the critic data yourself.
At the very least clear the system cache.
I use Package Disabler to disable about 70 apps. It's not as bad as it first seems. Android 10 literally has about 100 more new system apps than 9. Most of those new ones should be left alone. My disable list for the Android 9 N10+ vs the Android 10 one is almost identical though.
Samsung's do lots of cool things so don't be too concerned until you learn more about the features. Bixby got killed right out of the gate; it's a hog and it's EULA is one of the worst I've ever read.