Regardless of the rom I try, the Mi Mix gets uncomfortably hot. The only versions that stay cool are MIUI 8 and MIUI 9, but everything else (Resurrection, Epic ACiP, AOSIP, Lineage) are usually running the CPU up to between 65° and 75° making the thing uncomfortable to hold. Not with gaming mind you, but simply browsing or switching the sucker on. Any ideas how to fix this behavior?
----------
Solution
I followed the advice of James1089
I wiped everything apart form storage, also the system.
I downloaded the firmware 8.1.4 from the address provided in the post below
I installed the firmware prior to installing the rom
... then the rom ...
... then Magisk...
...then opengapps.
Now the Mi Mix runs cooler. Still warmer than stock but I can't
fry eggs on the back any more. A shame, since they don't
stick to the ceramic back.
Thanks again.:good:
hquant said:
Regardless of the rom I try, the Mi Mix gets uncomfortably hot. The only versions that stay cool are MIUI 8 and MIUI 9, but everything else (Resurrection, Epic ACiP, AOSIP, Lineage) are usually running the CPU up to between 65° and 75° making the thing uncomfortable to hold. Not with gaming mind you, but simply browsing or switching the sucker on. Any ideas how to fix this behavior?
Click to expand...
Click to collapse
Are you flashing the relevant firmware when using custom ROMs with full wipe.
May be best to reapply thermol paste under the cpu
---------- Post added at 10:39 AM ---------- Previous post was at 10:38 AM ----------
james1089 said:
Are you flashing the relevant firmware when using custom ROMs with full wipe.
Click to expand...
Click to collapse
Could you take a look at my mi mix thread really could use some pro help
mr 911 said:
May be best to reapply thermol paste under the cpu
---------- Post added at 10:39 AM ---------- Previous post was at 10:38 AM ----------
Could you take a look at my mi mix thread really could use some pro help
Click to expand...
Click to collapse
What about erasing from fastboot often cures many problems when coming from miui.
Firmware_7.9.21_Mi_Mix.zip
What is the appropriate Firmware?
At one point I installed Firmware_7.9.21_Mi_Mix.zip in combination with Resurrection Remix and I have not changed that since, regardless of the roms i have tested. Is there specific Firmware for each rom?
hquant said:
What is the appropriate Firmware?
At one point I installed Firmware_7.9.21_Mi_Mix.zip in combination with Resurrection Remix and I have not changed that since, regardless of the roms i have tested. Is there specific Firmware for each rom?
Click to expand...
Click to collapse
8.1.4 with all the latest roms
Try AICP latest build with that firmware, wipe system and both caches, reflash gapps and magisk. If it still runs hot wipe from fastboot before ripping phone apart.
Where can I find Firmware 8.1.4?
The Firmware_7.9.21_Mi_Mix.zip was part of the Resurrecgtion download list. Is there a Firmware_8.1.4_Mi_Mix.zip?
hquant said:
The Firmware_7.9.21_Mi_Mix.zip was part of the Resurrecgtion download list. Is there a Firmware_8.1.4_Mi_Mix.zip?
Click to expand...
Click to collapse
https://redirect.viglink.com/?forma...://mega.nz/#F!zlJBQJhJ!BJuv0brw0doTafuLTXJATw
james1089 said:
https://redirect.viglink.com/?forma...://mega.nz/#F!zlJBQJhJ!BJuv0brw0doTafuLTXJATw
Click to expand...
Click to collapse
Hi again, in which order do I flash what?
1. I did a standard Wipe (Data / Cache / Davlink)
- is that correct.? I do not want to wipe my user data where all my roms and backups reside
2. Then I installed AICP
3. Then I flashed the firmware 8.1.4_Mi_Mix
4. Then I flasched Open Gapps
5. Then I flashed Magisk
Still 65° without doing anything...
hquant said:
Hi again, in which order do I flash what?
1. I did a standard Wipe (Data / Cache / Davlink)
- is that correct.? I do not want to wipe my user data where all my roms and backups reside
2. Then I installed AICP
3. Then I flashed the firmware 8.1.4_Mi_Mix
4. Then I flasched Open Gapps
5. Then I flashed Magisk
Still 65° without doing anything...
Click to expand...
Click to collapse
You will have to wipe system as well, from advanced wipe,that will not delete data, that could well be the problem, first flash firmware then ROM and gapps. Last of all magisk, backups never perform well after restore in my opinion. They will remain intact regardless.
hquant said:
Hi again, in which order do I flash what?
1. I did a standard Wipe (Data / Cache / Davlink)
- is that correct.? I do not want to wipe my user data where all my roms and backups reside
2. Then I installed AICP
3. Then I flashed the firmware 8.1.4_Mi_Mix
4. Then I flasched Open Gapps
5. Then I flashed Magisk
Still 65° without doing anything...
Click to expand...
Click to collapse
I see it's marked as solved, care sharing incase someone else has same issue.
james1089 said:
I see it's marked as solved, care sharing incase someone else has same issue.
Click to expand...
Click to collapse
Hi James, I did just that in the first post of this thread. Thanks again...
hquant said:
Hi James, I did just that in the first post of this thread. Thanks again...
Click to expand...
Click to collapse
Yea sorry saw that after I posted.
Installling the 8.1.4 and the latest one messed up the sound so had to go back to 7.9... idling at 70C
justFaisal said:
Installling the 8.1.4 and the latest one messed up the sound so had to go back to 7.9... idling at 70C
Click to expand...
Click to collapse
Well you're the only one, which ROM? Did you wipe system? Try latest AICP with the new firmware.
james1089 said:
Well you're the only one, which ROM? Did you wipe system? Try latest AICP with the new firmware.
Click to expand...
Click to collapse
Started fresh again and it seems to be doing better but now viper4android doesn't work constantly, it keeps cutting off and on every few seconds.
Had to erase everything then flash 8.1.4 > AICP > gapps >
> restart > magisk > restart > viper > restart.
Now idling around 55-60c. Still higher than I'd like.
Gonna try the Psy kernel and see if using a different Governor helps.
justFaisal said:
Started fresh again and it seems to be doing better but now viper4android doesn't work constantly, it keeps cutting off and on every few seconds.
Had to erase everything then flash 8.1.4 > AICP > gapps >
> restart > magisk > restart > viper > restart.
Now idling around 55-60c. Still higher than I'd like.
Gonna try the Psy kernel and see if using a different Governor helps.
Click to expand...
Click to collapse
That's to high, mine reading 37, maybe viper is an issue, although if you have recently installed a new ROM it's normal till it settles down.
james1089 said:
That's to high, mine reading 37, maybe viper is an issue, although if you have recently installed a new ROM it's normal till it settles down.
Click to expand...
Click to collapse
I havent flashed the latest firmware, but I only use ViperOs and it never ever runs hot
Ultraman666 said:
I havent flashed the latest firmware, but I only use ViperOs and it never ever runs hot
Click to expand...
Click to collapse
Yea well viper is an older ROM so probably not good with 8.1.4 firmware, AICP has a weekly update and only works properly with 8.1.4. with the last 2 updates.
james1089 said:
That's to high, mine reading 37, maybe viper is an issue, although if you have recently installed a new ROM it's normal till it settles down.
Click to expand...
Click to collapse
You might be right, it's idling around 45-55 range today after 1 day.
I don't think viper4android is causing it tho.
I'm thinking about dual booting with stock miui 9.
Related
Surprised that I haven't seen a post on XDA yet showing us peeps that have rooted and removed ads how to apply this new update. I still think it's fictitious! haha
Seriously though, what would be the proper procedure here, revert to 100% stock then take the OTA or does anyone have hiding the .img file to flash via fastboot or whatnot? Are we able to even get root back after the B12 update? If not, I'd rather leave the phone as it is with root. It's been a long time since I've even messed with this phone because of lack of B12. I just impulse bought it because I wanted a decent spare phone.
Thanks!
http://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532/
ytsejam1138 said:
http://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532/
Click to expand...
Click to collapse
Your answer was extremely vague, but after reading the OP in that post several times, I took the plunge with 7.4.2 and worked perfectly. Thank you!
So for those that were confused like I was, here's the skinny:
Anyone with a R1 HD running build 6.6 or 6.8 can do what I did:
1. download the 7.4.2 shown in the post above to your SD card
2. boot into twrp (I used whatever version I already had - back when it first came out to rid me of ads)
3. full wipe (I tried dirty flashing, and magical unicorns reached out from my screen and slapped me in the face)
4. booted and waited about 5 minutes.
5. LTE Discovery shows the use of Band 12 without modification (I'm in a burb of Dayton, OH which is fringe Band 4 and excellent Band 12 coverage)
6. VoLTE is shown in Settings --> More --> Cellular Networks --> "Enhanced 4G LTE Mode"
Your answer was extremely vague, but after reading the OP in that post several times, I took the plunge with 7.4.2 and worked perfectly. Thank you!
Yes its not very clear
The last time I flashed something from that page it reset everything I did not care I had my apps backup.
So I have to do a full wipe? then restore with android titanium backup
then root once more from twrp?
Im not sure why I would want to flash this this is has updater enabled. I would lost root if they pushed a new update. I could just disable it like before.
its a good hour to do that. I have to back up the current rom. get a good back up with titanium backup, install the room root it set up the account then restore with titanium backup. Im using tmobel is it worh it? Im on wifi most of the time.
Modified_rom_R1HD_7.4.2.zip (Modified_rom is stock 7.4.2 rom minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img from 7.4.2, as well as amazon apps, no ads, updater enabled, so this rom is safe to use.)
https://www.androidfilehost.com/?fid=313042859668275704
Modified_rom_R1HD_7.4.2.zip (Modified_rom is stock 7.4.2 rom minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img from 7.4.2, as well as amazon apps, no ads, updater enabled, so this rom is safe to use.)
https://www.androidfilehost.com/?fid=313042859668275704
I dirty flashed, no problems. didn't lose any apps. You will lose root but then you just flash supersu and you're rooted again. It's really no problem at all to do.
joesee said:
Your answer was extremely vague, but after reading the OP in that post several times, I took the plunge with 7.4.2 and worked perfectly. Thank you!
So for those that were confused like I was, here's the skinny:
Anyone with a R1 HD running build 6.6 or 6.8 can do what I did:
1. download the 7.4.2 shown in the post above to your SD card
2. boot into twrp (I used whatever version I already had - back when it first came out to rid me of ads)
3. full wipe (I tried dirty flashing, and magical unicorns reached out from my screen and slapped me in the face)
4. booted and waited about 5 minutes.
5. LTE Discovery shows the use of Band 12 without modification (I'm in a burb of Dayton, OH which is fringe Band 4 and excellent Band 12 coverage)
6. VoLTE is shown in Settings --> More --> Cellular Networks --> "Enhanced 4G LTE Mode"
Click to expand...
Click to collapse
I'm still slightly confused. What if we are on the V12 non-Prime (dated 6/27/2016)? Is there an update to the V12?
parkerlreed said:
I'm still slightly confused. What if we are on the V12 non-Prime (dated 6/27/2016)? Is there an update to the V12?
Click to expand...
Click to collapse
The update is Prime only. There are no updates for v12.
cyanix-tech said:
The update is Prime only. There are no updates for v12.
Click to expand...
Click to collapse
So as long as I do a clean flash I can use Modified_rom_R1HD_7.4.2.zip?
parkerlreed said:
So as long as I do a clean flash I can use Modified_rom_R1HD_7.4.2.zip?
Click to expand...
Click to collapse
Yep, dirty works too.
cyanix-tech said:
Yep, dirty works too.
Click to expand...
Click to collapse
Sweet, opted for the clean flash over V12 and it's already booted up and restoring applications. Thanks.
---------- Post added at 10:59 PM ---------- Previous post was at 10:49 PM ----------
raven.warsong said:
Im not sure why I would want to flash this this is has updater enabled. I would lost root if they pushed a new update. I could just disable it like before.
Click to expand...
Click to collapse
This enables Blu's wireless update, not Amazon's. Also the modified stock feels pretty much like the V12 did. No traces of Amazon at all.
parkerlreed said:
Sweet, opted for the clean flash over V12 and it's already booted up and restoring applications. Thanks.
---------- Post added at 10:59 PM ---------- Previous post was at 10:49 PM ----------
This enables Blu's wireless update, not Amazon's. Also the modified stock feels pretty much like the V12 did. No traces of Amazon at all.
Click to expand...
Click to collapse
ya thanks it work great but I dont really want blu wireless update enabled do it? if I update that way I can lose recovery or root right?
raven.warsong said:
ya thanks it work great but I dont really want blu wireless update enabled do it? if I update that way I can lose recovery or root right?
Click to expand...
Click to collapse
I'm not sure.
parkerlreed said:
Sweet, opted for the clean flash over V12 and it's already booted up and restoring applications. Thanks.
---------- Post added at 10:59 PM ---------- Previous post was at 10:49 PM ----------
This enables Blu's wireless update, not Amazon's. Also the modified stock feels pretty much like the V12 did. No traces of Amazon at all.
Click to expand...
Click to collapse
its been my understanding it can so I just have to remember how to turn it off there is a file or a command you have to do. its been a few months. Any one know?
raven.warsong said:
its been my understanding it can so I just have to remember how to turn it off there is a file or a command you have to do. its been a few months. Any one know?
Click to expand...
Click to collapse
Settings > About device > Wireless Update > 3-dot menu > Settings > Check weekly/uncheck auto download
thanks
FyrestoneROM T113The simplicity of TouchWiz system without superfluous
Code:
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
Introduction:
This Rom is the stock samsung without annoying apps and with some tweaks made to make your life easier.
I have a lot to do for make it better, but I hope you appreciate my work, if you don't thanks for giving me a chance.
Features:
Based on T113XXU0ARB1
Debolated - Samsung and Google apps (350 MB of useless apps)
Deodexed
Zipaligned
Faster animation scale
Knox Free
Removed boot sound
Rooted with SuperSu
Busybox
Sony System signature - Feel free to install sony apps from play store!
AOSP Keyboard
Removed Samsung Update
Allow apps access to external storage
Removed Loud volume warning
Cyanogen/LineageOS UI sounds
Tweaks:
Battery Tweaks
Better scrolling
Video acceleration and HW debugging
Better RAM management
Google DNS
Download Link:
DOWNLOADMD5: b7694314c6cfe88f013522b86319210d
Old version [4 Feb 2017]: DOWNLOAD
MD5: 283aa300c00ae227b4362945925db4b4
Old version [4 Jan 2017]: DOWNLOAD
MD5: 6f97e788b0b2571742b256e6fcaf1e86
How to install The Rom:
Update your bootloader and baseband to XXU0ARB1 before flash!
1. Flash TWRP 2.8.7.0.tar with Odin 3.12.10.
2. Flash TWRP 3.0.2-0.img inside the recovery (Select Install image and choose Recovery partition).
3. Reboot into TWRP 3.0.2-0.
4. Copy FyrestoneROM_T113_XXXXX.zip in your SD Card.
5. Wipe: System, Data, Cache and Dalvik.
6. Optional – Wipe Internal Storage.
7. Install FyrestoneROM_T113_XXXXX.
8. Reboot and wait about 10 minutes.
How to install The Firmware:
1. Download and extract a zip file containing your desired firmware.
2. Open Odin Tool.
3. Boot your device in the "Download Mode":
(Press Volume Down, Power and Home buttons at same time for 5-8 seconds until download mode is active.)
4. Connect your device to PC via the USB cable while in download mode.
5. Next, check the "Auto Reboot" and "F. Reset Time" options in Odin Tool.
6. Hit the AP/PDA button then browse and select a tar.md5 file from the extracted folder.
7. Finally press the start button to begin flashing the firmware update on your device.
Credits:
Google for Android OS
Samsung for FW and source
Sony for System signature
Cyanogenmod for File manager
@SuperR for the kitchen
@bravonova for Build.prop Tweaks
@Chainfire for SuperSu
@mrRobinson for AdAway
XDA:DevDB Information
FyrestoneROM, ROM for the Samsung Galaxy Tab 3
Contributors
Jimbus369
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: T113XXU0AQA1
Based On: STOCK Samsung
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2017-02-04
Created 2017-01-04
Last Updated 2018-08-18
Reserved
Changelog:
27 July 2018:
Updated to XXU0ARB1
Fixed all previous issues
Removed Cyanogen File manager and Adawey
Now Thunderoar Kernel v5.0 is fully compatible
Updated Busybox and SuperSu
4 Feb 2017:
Updated to XXU0AQA1
Removed some Bloatware
Deodexed
Zipaligned
Faster animation scale
Allow apps access to external storage
Loud volume warning removed
Cyanogen/LineageOS UI sounds
Battery Tweaks
Increase Quality Of Media Streaming
Fixed Google DNS
Fixed Calendar Sync
Various build.prop changes
Various fix
4 Jan 2017:
Initial release
Known issues:
Calendar doesn't synchronize --> Calendar_sync_fix.zip
Tablet doesn't support vpn functionality --> VPN_FIX.zip
Print spooler does not works --> PrintSpooler_FIX.zip
Fantastic! Finally we've got a rom of our very own, for which you've got my immense thanks. I'm very much looking forward to trying it out.
Unfortunately when I flashed it there was a loooong wait on the Samsung logo, and then... Well, after an hour I booted back to recovery to start over.
I honestly don't think your rom was the problem though, because from some point last night everything I tried - custom rom flashing and nandroid backup restores - wound up the same way. Odin + stock + root got a usable system at least, and today's been too busy to try again. But when I do I'll post back about how it goes.
(Sadly, I can't go back in time to see what order I did things and look for a pattern if this happens again. In case it might be useful to anyone, I know for sure I'd gotten stock set up comfortably and made a complete backup before giving thunderoar's T113 kernel a whirl, and that went swimmingly. Even had mounts2sd properly recognizing external sd set up after a long struggle, though not actually enabled yet. Don't know what else i did between making that backup and trying to flash this, but it's likely I just screwed something up somehow.)
PushyPhoenix said:
Fantastic! Finally we've got a rom of our very own, for which you've got my immense thanks. I'm very much looking forward to trying it out.
Unfortunately when I flashed it there was a loooong wait on the Samsung logo, and then... Well, after an hour I booted back to recovery to start over.
I honestly don't think your rom was the problem though, because from some point last night everything I tried - custom rom flashing and nandroid backup restores - wound up the same way. Odin + stock + root got a usable system at least, and today's been too busy to try again. But when I do I'll post back about how it goes.
(Sadly, I can't go back in time to see what order I did things and look for a pattern if this happens again. In case it might be useful to anyone, I know for sure I'd gotten stock set up comfortably and made a complete backup before giving thunderoar's T113 kernel a whirl, and that went swimmingly. Even had mounts2sd properly recognizing external sd set up after a long struggle, though not actually enabled yet. Don't know what else i did between making that backup and trying to flash this, but it's likely I just screwed something up somehow.)
Click to expand...
Click to collapse
Upgrade your firmware to PH5 before flash and use TWRP 3.0.2-0.
Firmware: http://samsung-updates.com/device/?id=SM-T113
TWRP: https://dl.twrp.me/goyave/
Wipe all partition in TWRP:
System, Cache, Dalvik and if you can internal Storage.
Thunderoar Kernel isn't compatible with PH5 firmware for the moment.
Let me know how it goes
Thanks so much for responding even though I didn't specifically ask.
Pretty much all my knowledge comes from following instructions in these forums and piecing little bits of information together, so I've got a few questions - trying to understand the "why" behind these things in order to be more self-sufficient. Please feel free to point me towards resources where I can learn more!
Jimbus369 said:
Upgrade your firmware to PH5 before flash and use TWRP 3.0.2-0.
Click to expand...
Click to collapse
This is a surprise to me - I'd always thought that when flashing a new ROM, everything gets replaced. I never would have figured this part out on my own!
Firmware: http://samsung-updates.com/device/?id=SM-T113
Click to expand...
Click to collapse
There's no Canadian version - but should I presume that, since this is a Wi-Fi only device, the CSC isn't too important?
How much does this matter even when using a device with a network connection?
TWRP: https://dl.twrp.me/goyave/
Click to expand...
Click to collapse
(Ooops, forgot to do this right off the bat. My bad!)
Does recovery version generally make a big difference?
Wipe all partition in TWRP:
System, Cache, Dalvik and if you can internal Storage.
Click to expand...
Click to collapse
I've been wiping Data as well - is that not necessary?
Does wiping Internal Storage have a big effect? I suppose there's a fair bit of app-specific stuff in there that could cause issues?
Thunderoar Kernel isn't compatible with PH5 firmware for the moment.
Click to expand...
Click to collapse
Ah well, soon enough!
Let me know how it goes
Click to expand...
Click to collapse
Of course! You're investing time in putting this together, and helping out users; the very least I can do is let you know what's going on with that time you've invested!
Okay, about to check on the firmware installation!
PushyPhoenix said:
This is a surprise to me - I'd always thought that when flashing a new ROM, everything gets replaced. I never would have figured this part out on my own!
Click to expand...
Click to collapse
When you install a rom, especially a TW one, in most case you need a specific Bootloader to cause it to start and work smoothly.
Wikipedia:
A boot loader is a computer program that loads an operating system or some other system software for the computer after completion of the power-on self-tests; it is the loader for the operating system itself. Within the hard reboot process, it runs after completion of the self-tests, then loads and runs the software. A boot loader is loaded into main memory from persistent memory, such as a hard disk drive or, in some older computers, from a medium such as punched cards, punched tape, or magnetic tape. The boot loader then loads and executes the processes that finalize the boot. Like POST processes, the boot loader code comes from a "hard-wired" and persistent location; if that location is too limited for some reason, that primary boot loader calls a second-stage boot loader or a secondary program loader.
The bootloader runs your rom with specific instructions, if the rom does not support an older bootloader simply does not boot. My rom does not support the older bootloader. A zip flash in this case cannot upgrade a delicate part like the bootloader. You need to flash the newer one with Odin.
There's no Canadian version - but should I presume that, since this is a Wi-Fi only device, the CSC isn't too important?
How much does this matter even when using a device with a network connection?
Click to expand...
Click to collapse
The latest update for your country is PA5. Try with THIS.
Your country code is XAC.
The CSC (Sale Country Code) Is that part of the firmware that contains all the telephone operator customizations (e.g. WAP, MMS) for the intended country. As far as i know, It is not important for us.
(Ooops, forgot to do this right off the bat. My bad!)
Does recovery version generally make a big difference?
Click to expand...
Click to collapse
Yes, the Recovery can make the difference.
I've been wiping Data as well - is that not necessary?
Does wiping Internal Storage have a big effect? I suppose there's a fair bit of app-specific stuff in there that could cause issues?
Click to expand...
Click to collapse
I forgot to write data, my bad! But i wrote it in the instructions in the first topic. For personal experience i had different issues when I didn't formatted the Internal Storage. The Android folder, .thumbnails and others, can create issues.
Ah well, soon enough!
Click to expand...
Click to collapse
I hope that in the next update we could use this kernel. :fingers-crossed:
Of course! You're investing time in putting this together, and helping out users; the very least I can do is let you know what's going on with that time you've invested!
Okay, about to check on the firmware installation!
Click to expand...
Click to collapse
I want to give my best support at all users in difficulty, if you have a problem just ask. :good: :good:
Sorry for my english
Jimbus369 said:
Sorry for my english
Click to expand...
Click to collapse
You're doing just fine!
I'll reply more later, but wanted to report that it's installed and running very smoothly! Haven't played around much but will do at home later.
If you've got any tips for getting mounts2sd up and running I'd really appreciate it!
PushyPhoenix said:
You're doing just fine!
I'll reply more later, but wanted to report that it's installed and running very smoothly! Haven't played around much but will do at home later.
If you've got any tips for getting mounts2sd up and running I'd really appreciate it!
Click to expand...
Click to collapse
I'm happy to hear it. Anyway, I don't know how mounts2sd works. Have you already tried HERE?
Jimbus369 said:
I'm happy to hear it. Anyway, I don't know how mounts2sd works. Have you already tried HERE?
Click to expand...
Click to collapse
Yup, that's the app I'm using, but haven't been able to get my external partition mounted properly. I did manage it once, think it was with thunderoar's kernel though.
Sent from my SM-G900W8 using XDA Labs
Jimbus369 said:
I'm happy to hear it.
Click to expand...
Click to collapse
Life has gotten in the way of playing around with this, but thought I'd send you an update as I said I would...
Your rom is running really nicely on my tablet as I use it daily. It's smooth and small, with no unexpected reboots or fc's on installed apps. Didn't wipe internal SD but it hasn't given me any issues with existing data (probably because there wasn't much to start with).
One thing that has caused a problem is calendar sync. It looks like you've taken out the actual syncing service, so when I try to access my calendars through any app I'm asked to add a new Google account, even though everything's already set up in "Accounts" under Settings. I haven't tried running the "calendars.providers.apk" from my other phone, that should fix the problem - but I don't want to use the wrong version and break something!
Also, I've confirmed that the only time I got mounts2sd working, it was with thunderoar's kernel. So guess that's going to have to wait.
A few adjustments I made to the setup were to uninstall all "unnecessary" system apps (not needed to run the device), and re-install them from the store. This way I've got 676mb free on /system and still over 1.5GB free on internal storage.
I've also added a multi-reboot menu to make getting into recovery or download mode simpler, and this is loading more quickly on your rom than stock. I've also had to modify permissions.xml to allow apps to access external storage by default, and made another tweak to disable the "loud volume warning" (don't remember quite what it was offhand).
Would you consider adding these to a future version?
Again, thanks SO much for putting this together, answering questions, and doing your thing. It's greatly appreciated!
PushyPhoenix said:
Life has gotten in the way of playing around with this, but thought I'd send you an update as I said I would...
Your rom is running really nicely on my tablet as I use it daily. It's smooth and small, with no unexpected reboots or fc's on installed apps. Didn't wipe internal SD but it hasn't given me any issues with existing data (probably because there wasn't much to start with).
One thing that has caused a problem is calendar sync. It looks like you've taken out the actual syncing service, so when I try to access my calendars through any app I'm asked to add a new Google account, even though everything's already set up in "Accounts" under Settings. I haven't tried running the "calendars.providers.apk" from my other phone, that should fix the problem - but I don't want to use the wrong version and break something!
Also, I've confirmed that the only time I got mounts2sd working, it was with thunderoar's kernel. So guess that's going to have to wait.
A few adjustments I made to the setup were to uninstall all "unnecessary" system apps (not needed to run the device), and re-install them from the store. This way I've got 676mb free on /system and still over 1.5GB free on internal storage.
I've also added a multi-reboot menu to make getting into recovery or download mode simpler, and this is loading more quickly on your rom than stock. I've also had to modify permissions.xml to allow apps to access external storage by default, and made another tweak to disable the "loud volume warning" (don't remember quite what it was offhand).
Would you consider adding these to a future version?
Again, thanks SO much for putting this together, answering questions, and doing your thing. It's greatly appreciated!
Click to expand...
Click to collapse
The calendar sync issue should be fixed in the next update.
Anyway, If I have enough time, the next update should contain a lot of new features. Your suggestions are already planned :good:
Jimbus369 said:
When you install a rom, especially a TW one, in most case you need a specific Bootloader to cause it to start and work smoothly.
....
The bootloader runs your rom with specific instructions, if the rom does not support an older bootloader simply does not boot. My rom does not support the older bootloader. A zip flash in this case cannot upgrade a delicate part like the bootloader. You need to flash the newer one with Odin.
Click to expand...
Click to collapse
One more question about this: The way you've worded the second paragraph seems to imply only that older bootloaders don't work with newer roms, so are newer bootloaders backwards compatible? Say I've got the PH5 bootloader installed and I want to restore a backup of the previous firmware, do I have to flash that firmware first?
Sorry if it seems obvious, this is how we learn!
Sent from my SM-G900W8 using XDA Labs
PushyPhoenix said:
One more question about this: The way you've worded the second paragraph seems to imply only that older bootloaders don't work with newer roms, so are newer bootloaders backwards compatible? Say I've got the PH5 bootloader installed and I want to restore a backup of the previous firmware, do I have to flash that firmware first?
Sorry if it seems obvious, this is how we learn!
Sent from my SM-G900W8 using XDA Labs
Click to expand...
Click to collapse
Absolutely it isn't obvious, don't worry . The Bootloader, for my personal experience, are backwards compatible. I don't have a scientific knowledge about this, but for what I did with other device it can work. Just try :fingers-crossed:, don't forget a full backup.
Calendar_sync_fix.zip
Here is a fix for calendar sync.
@PushyPhoenix Thanks for reporting this issue
Jimbus369 said:
Calendar_sync_fix.zip
Here is a fix for calendar sync.
@PushyPhoenix Thanks for reporting this issue
Click to expand...
Click to collapse
This is a huge help, as one reason for getting this tablet was to use the calendar on a bigger screen.... Thanks so much!
---------- Post added at 10:58 PM ---------- Previous post was at 10:50 PM ----------
Jimbus369 said:
The Bootloader, for my personal experience, are backwards compatible. I don't have a scientific knowledge about this, but for what I did with other device it can work. Just try :fingers-crossed:
Click to expand...
Click to collapse
Fantastic - it worked on my S5 (had to restore a backup to retrieve some data).
don't forget a full backup.
Click to expand...
Click to collapse
Never! The most important thing, along with wiping.
When is coming to FyrestoneROM V2 ?
And thank you very much. So love...
Does this work on sm-t116ny ?
Because no development for sm-t116ny .
dhruvpatel_9880 said:
Does this work on sm-t116ny ?
Because no development for sm-t116ny .
Click to expand...
Click to collapse
I don't think it can work. If your device codename is Goyave you can try. Let me know if it works
Jimbus369 said:
I don't think it can work. If your device codename is Goyave you can try. Let me know if it works
Click to expand...
Click to collapse
First of all thanks for replying
My device codename is Goyave3g5m probably .
Can you please tell me which all models have same codename "Goyave"?
And cm 11 for sm-t116 works well on my sm-t116ny.
I will try and let you know does it boots .
---------- Post added at 01:55 PM ---------- Previous post was at 01:40 PM ----------
It is working on sm-t116ny
But wifi hotspot not working
Please help
dhruvpatel_9880 said:
First of all thanks for replying
My device codename is Goyave3g5m probably .
Can you please tell me which all models have same codename "Goyave"?
And cm 11 for sm-t116 works well on my sm-t116ny.
I will try and let you know does it boots .
---------- Post added at 01:55 PM ---------- Previous post was at 01:40 PM ----------
It is working on sm-t116ny
But wifi hotspot not working
Click to expand...
Click to collapse
T113/T113nu and T116/T116ny have a similar codename and hardware (The recovery have goyave codename, therefore any rom with goyave codename can be flashed). For the hotspot, maybe some missing libraries, a different driver or a different kernel makes hotspot broken. Try to restore your kernel from a previous backup.
Are there any oreo ROMs out here that don't make the phone reboot out of nowhere. I've tried a couple with no luck but thankfully they reboot quickly but wanted to see if there was a Rom without that problem thanks
jmcandrews83 said:
Are there any oreo ROMs out here that don't make the phone reboot out of nowhere. I've tried a couple with no luck but thankfully they reboot quickly but wanted to see if there was a Rom without that problem thanks
Click to expand...
Click to collapse
RR Neo
And u need to start a new topic for this? We have an q&a section
@dramalicious: Simply report the post and let the mods move it. There's no need to get all dramatic about it.
I reported the post, so it will be moved shortly.
Strephon Alkhalikoi said:
@dramalicious: Simply report the post and let the mods move it. There's no need to get all dramatic about it.
I reported the post, so it will be moved shortly.
Click to expand...
Click to collapse
Yep, moved.
Indeed, nothing dramatic here
Wood Man
jmcandrews83 said:
Are there any oreo ROMs out here that don't make the phone reboot out of nowhere. I've tried a couple with no luck but thankfully they reboot quickly but wanted to see if there was a Rom without that problem thanks
Click to expand...
Click to collapse
I'm running Beltz and after getting my battery replaced a couple of weeks ago I haven't gotten any random restarts plus my phone doesn't die around 30% anymore.
jmcandrews83 said:
Are there any oreo ROMs out here that don't make the phone reboot out of nowhere. I've tried a couple with no luck but thankfully they reboot quickly but wanted to see if there was a Rom without that problem thanks
Click to expand...
Click to collapse
Nephilim Renown ROM maker Frankie T (R3Ds)
owner
Nephilim Renown google+ community
14 february 2018 г. wrote:
Reboot Fix for 8.0.0 OREO
1 - Download the latest Google OTA image [external link censured for new users]
2 - Use adb or wufresh tools to restore back to stock
3 - Once on stock, install TWRP and ROOT
4 - Reboot to TWRP and format everything, including storage
5 - Now Add the OREO ROM, Gapps, and Root zips to device storage
6 - Flash ROM, Gapps, and Root...NOW FORMAT data, cache, dalvik-cache, and storage (DONT WIPE SYSTEM)
7 - Reboot, PROFIT!!!
Screw'd no reboots.ever
For some weeks now my Redmi Note 10 Pro has been facing severe lags. The lags appear regularly about each 5 sec. Then the video and audio or the UI freezes completly for about 1 sec, making it impossible to watch videos or making phone calls. I flashed several roms but it's the same issue everywhere. I even put back the phone in factory condition fashing MIUI and relocking the bootloader, but with no success. At the moment I am coming to the conclusion that I must have damaged my hardware somehow.
mi-girl said:
For some weeks now my Redmi Note 10 Pro has been facing severe lags. The lags appear regularly about each 5 sec. Then the video and audio or the UI freezes completly for about 1 sec, making it impossible to watch videos or making phone calls. I flashed several roms but it's the same issue everywhere. I even put back the phone in factory condition fashing MIUI and relocking the bootloader, but with no success. At the moment I am coming to the conclusion that I must have damaged my hardware somehow.
Click to expand...
Click to collapse
Try really clean flash with fw and formating data in TWRP with yes.
For example Los 19.1
mi-girl said:
For some weeks now my Redmi Note 10 Pro has been facing severe lags. The lags appear regularly about each 5 sec. Then the video and audio or the UI freezes completly for about 1 sec, making it impossible to watch videos or making phone calls. I flashed several roms but it's the same issue everywhere. I even put back the phone in factory condition fashing MIUI and relocking the bootloader, but with no success. At the moment I am coming to the conclusion that I must have damaged my hardware somehow.
Click to expand...
Click to collapse
Try stress testing to see where the issue is
Eg: https://github.com/aystshen/AndroidStressTest
Laptapper said:
Try really clean flash with fw and formating data in TWRP with yes.
For example Los 19.1
Click to expand...
Click to collapse
I did already many clean flashes. And as mentioned I even put the phone back to factory condition by flashing MIUI with Xiaomi Flash Tool.
mi-girl said:
I did already many clean flashes. And as mentioned I even put the phone back to factory condition by flashing MIUI with Xiaomi Flash Tool.
Click to expand...
Click to collapse
Factory reset won't help if fw is broken and and and....
Formating by manually typing yes in TWRP and firmware first then ROM and then formating is mandatory
RAMBO29 said:
Try stress testing to see where the issue is
Eg: https://github.com/aystshen/AndroidStressTest
Click to expand...
Click to collapse
Good idea! I have trouble installing the apk. It says "App not installed as package conflicts with an existing package." Not sure what package to delete. I have vanilla MIUI on my device. Unrooted and locked bootloader.
Laptapper said:
Factory reset won't help if fw is broken and and and....
Formating by manually typing yes in TWRP and firmware first then ROM and then formating is mandatory
Click to expand...
Click to collapse
I think you misunderstand me. As stated above I went through several ROMs and when reverting back to MIUI I used MIUI Flash Tool. It formates/wipes everything and installs the latest firmware/rom completely new. Besides that I did a "format data" after every custom rom installation.
mi-girl said:
I think you misunderstand me. As stated above I went through several ROMs and when reverting back to MIUI I used MIUI Flash Tool. It formates/wipes everything and installs the latest firmware/rom completely new. Besides that I did a "format data" after every custom rom installation.
Click to expand...
Click to collapse
Hmmm , did you've flashed manually the firmware in front of a custom ROM and the right one? I've destroyed my sweetin with wrong fw and now I've got a new sweet.
If here also your answer is yes then your phone can be repaired perhaps in a Xiaomi store....
Yes. I even tried several different firmwares. In the meantime I also did a CPU stress test it shows no problems.
mi-girl said:
Yes. I even tried several different firmwares. In the meantime I also did a CPU stress test it shows no problems.
Click to expand...
Click to collapse
Which Phone Modell you've got exactly?
Laptapper said:
Which Phone Modell you've got exactly?
Click to expand...
Click to collapse
sweet
mi-girl said:
sweet
Click to expand...
Click to collapse
Mee too
May you wanna try at last my actually running perfect config and exactly my steps....
Flash ofox 12.1_3
Format data with yes
Reboot twrp
Flash fw
Flash ROM (take screenshots of flashing progress for analysis)
Format data with yes
Reboot system
Fw, ofox attached
ROM
👍 [SHARED][ROM] [ANDROID 13] [OSS] PULKITS lineage os 20 19.02.23/ checked by myself
Update on page 14 Update latest los 20 on page 7 I'm on pulkits android 13 for testing. Quiet good! Soon you'll get a beta! Thanks a lot to @Pulkit Agarwal Please donate him, thanks Update see post Post in thread '👍 [SHARED][ROM] [ANDROID...
forum.xda-developers.com
If this is not working too, your phone has a hardware prob....
Is it lagging when you are in airplane mode(WIFI scan issues) ? Or stressing CPU(IT'S not stuck in low frequency) ? Clear data from Gapps?
If this is clear and above steps are still same, as @Laptapper said suspect hardware.
I flashed back to custom ROM as described by @Laptapper. The problem still persists. Also with a downloaded 1080p video and airplane mode on. CPU Stress Tests shows no abnormalities.
Thanks for all the good ideas and the input. I will give this phone up. I probably screwed the hardware. Anyhow it was a nice time with this phone, the great community and custom rom support.
I have misplaced the solution for this problem. I am on A13 crDroid 9.3 so no ability to dump Dalvik or cache in the limited recovery. Here is a screenshot. (Plus, Mobile Network is almost always the top app despite not using mobile data)
It's exactly the same for me. I am also with crdroid 9.3.
The excessive battery consumption problem happens because for some strange reason there is a wakelock related to the mobile data network, which causes the phone not to go into deepsleep when it is idle. In fact to me it literally marks 0% deepsleep. And perfectly in one night I can go 30% of the battery without doing absolutely nothing.
PinguiNUX said:
It's exactly the same for me. I am also with crdroid 9.3.
The excessive battery consumption problem happens because for some strange reason there is a wakelock related to the mobile data network, which causes the phone not to go into deepsleep when it is idle. In fact to me it literally marks 0% deepsleep. And perfectly in one night I can go 30% of the battery without doing absolutely nothing.
Click to expand...
Click to collapse
Oddly, I always (and I mean always) see Mobile Network on A13 (or Cell Standby on A12) as the top battery app, and no suggestions worked for me. Saw in multiple custom ROMs, but not everyone sees it. I do not even use mobile data, only wifi. This "thousands" bug is sometimes part of it. Even putting the phone in airplane mode for a day does not change the battery stats at all for me.
I already found out what is the wakelock that causes this thanks to betterbatterystats. And the culprit seems to be IPA_WS or any other of the IPA family. These wakelocks indeed seem to be related to the mobile data network.
I just flashed crdroid build 9.5 on my phone. Despite being a nightly (beta) version, it fixes many bugs present in crdroid 9.3.
According to the developer the next stable version will be released soon. But in the meantime, I'm going to try a few days the 9.5 to see how it goes. And so check if they have corrected the failure of battery consumption.
In fact I have already checked that they have fixed some small bugs that were present in version 9.3. So so far so good.
UPDATE: the latest MIUI firmware update seems to have helped me. I was on the .08, and this stable is .12. My battery percents are back in the tens. Good, since there is no known optional kernel yet.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Is there a way to flash just the kernel from the latest firmware? I don't want to reinstall everything again..
mierdaseca said:
Is there a way to flash just the kernel from the latest firmware? I don't want to reinstall everything again..
Click to expand...
Click to collapse
SPES Global: https://xiaomifirmwareupdater.com/firmware/spes/stable/V14.0.2.0.TGCMIXM/
SPESN Global: https://xiaomifirmwareupdater.com/firmware/spesn/stable/V14.0.2.0.TGKMIXM/
flash via TWRP/Orangefox > done.
gentano said:
SPES Global: https://xiaomifirmwareupdater.com/firmware/spes/stable/V14.0.2.0.TGCMIXM/
SPESN Global: https://xiaomifirmwareupdater.com/firmware/spesn/stable/V14.0.2.0.TGKMIXM/
flash via TWRP/Orangefox > done.
Click to expand...
Click to collapse
That is firmware, not kernel. There are no kernel install options for spes yet. It even says "firmware" in the links.
I see the official crDroid site (https://crdroid.net/spes/9) now links to the A13 V14, which has updated in the last few days from the A12 V13 version. I'll install it myself.
My deep sleep has returned to the 90's again.
Oh lol, I misread your question.... but why you need to install everything again if You install the firmware only? the firmware is just the firmware and has nothing to do with data.. or do I miss something here?
gentano said:
Oh lol, I misread your question.... but why you need to install everything again if You install the firmware only? the firmware is just the firmware and has nothing to do with data.. or do I miss something here?
Click to expand...
Click to collapse
I just flashed the firmware. You thought I rebuilt everything else from scratch too?
I am installing the A13 firmware that just came out on the 6th of June now.
Hm, I still dont get you.
Why You need/ask for seperate kernel to flash when there is the firmware, which doesnt change any of your userdata?
Sheist! said:
I am installing the A13 firmware that just came out on the 6th of June now.
Click to expand...
Click to collapse
Ye, thats what I linked and installing that firmware wont mess with Your userdata. So there is no need to reinstall any apps or whatever. Its the just the firmware (contains drivers and boot stuff) and not the whole rom image.
gentano said:
Hm, I still dont get you.
Why You need/ask for seperate kernel to flash when there is the firmware, which doesnt change any of your userdata?
Ye, thats what I linked and installing that firmware wont mess with Your userdata. So there is no need to reinstall any apps or whatever. Its the just the firmware (contains drivers and boot stuff) and not the whole rom image.
Click to expand...
Click to collapse
RN10P has kernel downloads available to fix battery issues, etc like this, in ADDITION to firmware provided by MIUI. There are no kernels for the RN11 as of today. The RN11 firmware from MIUI just updated to A13 as of June 6, but had only the A12 version from April of this year before that on their "firmware" download link. Both files are just 1 zip files that get installed via recovery. I hope that clears it up.
Ignore any suggestions about removing/reinstalling anything else; I never asked about any of that.
(added P to RN10 to correct error and not confuse with any RN10 users)
gentano said:
SPES Global: https://xiaomifirmwareupdater.com/firmware/spes/stable/V14.0.2.0.TGCMIXM/
SPESN Global: https://xiaomifirmwareupdater.com/firmware/spesn/stable/V14.0.2.0.TGKMIXM/
flash via TWRP/Orangefox > done.
Click to expand...
Click to collapse
So I can flash this, and I won't lose any data? For the naming of the firmware, I thought it was just a word for "official rom"
mierdaseca said:
So I can flash this, and I won't lose any data? For the naming of the firmware, I thought it was just a word for "official rom"
Click to expand...
Click to collapse
Just firmware. Firmware size is extremely small, while ROM size is extremely large. ROM and firmware are 2 different things. You could say the ROM is the house and the firmware is the land, but post-updatable land. No loss of data, except when something borks and the firmware has issues within it, causing you phone headaches.
Sheist! said:
Just firmware. Firmware size is extremely small, while ROM size is extremely large. ROM and firmware are 2 different things. You could say the ROM is the house and the firmware is the land, but post-updateable land. No loss of data, except when something borks and the firmware has issues within it, causing you phone headaches.
Click to expand...
Click to collapse
Thanks I just flashed it. But I still see the battery in thousands. How can I check the firmware version on phone?
BTW where can I download the nightly?
On https://crdroid.net/spes/9 I don't see anything besides the April b uild
mierdaseca said:
Thanks I just flashed it. But I still see the battery in thousands. How can I check the firmware version on phone?
BTW where can I download the nightly?
On https://crdroid.net/spes/9 I don't see anything besides the April b uild
Click to expand...
Click to collapse
Really? Hunh. Mine popped back to normal, but I did fully charge it and reboot it too. The deep sleep number (look under About Phone) jumped back into the upper 90's as well (good), and it had been stuck at 0.
I use Device Info HW which SHOULD (but does not even with root enabled on it!) show it on the 3rd tab, System, for the value of Description, but mine keeps showing just a dash! You'll have to locate an app that reveals the installed firmware.
Are you in India?
Sheist! said:
Really? Hunh. Mine popped back to normal, but I did fully charge it and reboot it too. The deep sleep number (look under About Phone) jumped back into the upper 90's as well (good), and it had been stuck at 0.
I use Device Info HW which SHOULD (but does not even with root enabled on it!) show it on the 3rd tab, System, for the value of Description, but mine keeps showing just a dash! You'll have to locate an app that reveals the installed firmware.
Are you in India?
Click to expand...
Click to collapse
I just checked on about phone, and deep sleep still at 0%.
I also fully charged it, and rebooted and wiped battery usage data, but still shows thousands.
I also get a dash in that app.
No, I'm not from India.
mierdaseca said:
I just checked on about phone, and deep sleep still at 0%.
I also fully charged it, and rebooted and wiped battery usage data, but still shows thousands.
I also get a dash in that app.
No, I'm not from India.
Click to expand...
Click to collapse
Look at the firmware link on crDroid again and try the A13 MIUI V14 firmware released on June 6. I installed it via adb sideload since my phone temporarily won't read my external SD card. I do not recall anything else to try. Good luck.
Sheist! said:
Look at the firmware link on crDroid again and try the A13 MIUI V14 firmware released on June 6. I installed it via adb sideload since my phone temporarily won't read my external SD card. I do not recall anything else to try. Good luck.
Click to expand...
Click to collapse
I flashed again via adb sideload, but still nothing. I even updated to the latest crdroid 9.5 build and still nothing
mierdaseca said:
I flashed again via adb sideload, but still nothing. I even updated to the latest crdroid 9.5 build and still nothing
Click to expand...
Click to collapse
Then you are not speaking about the RN11 spes. There is no 9.5 update for this phone. This forum is for RN11 spes. Look at Device Info HW again and find out what phone you are actually using.