Q&A for [KERNEL][G800F][exynos][G800FXXU1*][TW Only]Custom Kernel
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][G800F][exynos][G800FXXU1*][TW Only]Custom Kernel. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Works perfectly on ANL1.
Also, it's compatible with M-Audio Keystation 32 Mini, if anybody was curious about that.
hi! sorry, can you tell me more about "double tap awakening" ? how can i do that on my 800f ?
luckyaceman said:
hi! sorry, can you tell me more about "double tap awakening" ? how can i do that on my 800f ?
Click to expand...
Click to collapse
If you've flashed the kernel image, use the Synapse app to turn the feature on. It is located under the "Extra Features" page.
While the device is in sleep mode(screen off), you can double tap anywhere on the screen to wake it up instead of using the power button or home button. It is meant to be more convenient, but drains extra power whilst active. You should get about 12 hours of average usage with the right settings, as opposed to about 20 hours when the feature is off.
Thx, Curtis! is it use an accel. to awake?
luckyaceman said:
Thx, Curtis! is it use an accel. to awake?
Click to expand...
Click to collapse
No, accelerometer is not used, only the touchscreen, light and proximity sensors.
CurtisMJ said:
No, accelerometer is not used, only the touchscreen, light and proximity sensors.
Click to expand...
Click to collapse
how it may use the light to awake??? i must knocking IN the sensor?
luckyaceman said:
how it may use the light to awake??? i must knocking IN the sensor?
Click to expand...
Click to collapse
The feature makes use of the light and proximity sensors in order to detect whether the device is in a dark enclosed place (eg. A pocket) and disables itself in these situations as well in order to prevent accidental wakes
Click to expand...
Click to collapse
In short: No.
After rebooting, WiFi configuration is deleted and I need to put again the password. This also happens when disabling WiFi and re-enabling it. Is this a bug related to the kernel, or can I solve it I another way?
Also wanted to know if it's possible to add ambient display.
Apart from this, no further problems
---------- Post added at 05:26 PM ---------- Previous post was at 05:25 PM ----------
luckyaceman said:
how it may use the light to awake??? i must knocking IN the sensor?
Click to expand...
Click to collapse
It's just for checking if there is a flip cover or something covering the screen.
Other use of proximity sensor and light sensor are not to wake while on pocket
nico_vo said:
After rebooting, WiFi configuration is deleted and I need to put again the password. This also happens when disabling WiFi and re-enabling it. Is this a bug related to the kernel, or can I solve it I another way?
Also wanted to know if it's possible to add ambient display.
Apart from this, no further problems
Click to expand...
Click to collapse
Explanation:
This is related to the Samsung Secure Storage feature on their ROMs. Basically, for security reasons, any reasonably personal data(eg. Private Mode files, S Health data, Wifi Passwords) are kept in an encrypted container. This container gets invalidated if Knox detects any changes to the system and locks out potential hackers. Flashing a kernel after the system has been setup counts as a change. While this feature's intentions are admirable, it just presents problems for the type of people that use XDA.
Fix:
Luckily, this feature can be disabled with a build.prop tweak, namely
Change
Code:
ro.securestorage.support=true
To
Code:
ro.securestorage.support=false
This will cause the previously mentioned data to be stored in the regular Android manner, but unfortunately, any data that was in secure storage will now be erased.
As far as I know, ambient display is a ROM feature? Never heard of it and the kernel in the same sentence to be honest.
CurtisMJ said:
Explanation:
This is related to the Samsung Secure Storage feature on their ROMs. Basically, for security reasons, any reasonably personal data(eg. Private Mode files, S Health data, Wifi Passwords) are kept in an encrypted container. This container gets invalidated if Knox detects any changes to the system and locks out potential hackers. Flashing a kernel after the system has been setup counts as a change. While this feature's intentions are admirable, it just presents problems for the type of people that use XDA.
Fix:
Luckily, this feature can be disabled with a build.prop tweak, namely
Change
Code:
ro.securestorage.support=true
To
Code:
ro.securestorage.support=false
This will cause the previously mentioned data to be stored in the regular Android manner, but unfortunately, any data that was in secure storage will now be erased.
As far as I know, ambient display is a ROM feature? Never heard of it and the kernel in the same sentence to be honest.
Click to expand...
Click to collapse
Okay thank you
About the ambient display, I'm quite noobish in this, but thank you for explaining
Is double tap in status bar to sleep also ROM related or can it be applied to this kernel?
nico_vo said:
Is double tap in status bar to sleep also ROM related or can it be applied to this kernel?
Click to expand...
Click to collapse
It is indeed ROM based. There's an xposed module to enable it on OEM ROM's though:
http://repo.xposed.info/module/com.zst.xposed.doubletaptosleep
CurtisMJ said:
It is indeed ROM based. There's an xposed module to enable it on OEM ROM's though:
http://repo.xposed.info/module/com.zst.xposed.doubletaptosleep
Click to expand...
Click to collapse
How can I install xposed?
I have android 5.1.1 and tried wanam xposed yesterday, but got bootloop after installing framework.
Got my sd card and downloaded xposed uninstaller on it, to see if I could get out of the bootloop, but this didnt work and I had to flash the stock firmware, root, recovery and custom kernel.
Any suggestions of what could have caused this?
nico_vo said:
How can I install xposed?
I have android 5.1.1 and tried wanam xposed yesterday, but got bootloop after installing framework.
Got my sd card and downloaded xposed uninstaller on it, to see if I could get out of the bootloop, but this didnt work and I had to flash the stock firmware, root, recovery and custom kernel.
Any suggestions of what could have caused this?
Click to expand...
Click to collapse
Sorry. TWRP version seems to matter a lot when flashing xposed
http://forum.xda-developers.com/galaxy-s5-mini/general/touchwiz-5-1-1-xposed-t3324912
Personally, I still use rvr's 2.8.1.0 TWRP
CurtisMJ said:
Sorry. TWRP version seems to matter a lot when flashing xposed
http://forum.xda-developers.com/galaxy-s5-mini/general/touchwiz-5-1-1-xposed-t3324912
Personally, I still use rvr's 2.8.1.0 TWRP
Click to expand...
Click to collapse
So if I use TWRP 2.8.1.0 instead of 3.0 it should work, or do I have to flash it with another custom recovery?
EDIT:
I tried TWRP 2.8.7.0, but it didn't also work.
Instead, I got it to work with an old CWM I found. With it, I came out from the bootloop without erasing (again) all my data :highfive:
Thank you for telling it was the recovery, it made everything for me for looking for an answer a looooooooot quicker
There is still the problem with the audio?
Wifi-Kernel-Bug
CurtisMJ said:
Explanation:
This is related to the Samsung Secure Storage feature on their ROMs. Basically, for security reasons, any reasonably personal data(eg. Private Mode files, S Health data, Wifi Passwords) are kept in an encrypted container. This container gets invalidated if Knox detects any changes to the system and locks out potential hackers. Flashing a kernel after the system has been setup counts as a change. While this feature's intentions are admirable, it just presents problems for the type of people that use XDA.
Fix:
Luckily, this feature can be disabled with a build.prop tweak, namely
Change
Code:
ro.securestorage.support=true
To
Code:
ro.securestorage.support=false
This will cause the previously mentioned data to be stored in the regular Android manner, but unfortunately, any data that was in secure storage will now be erased.
As far as I know, ambient display is a ROM feature? Never heard of it and the kernel in the same sentence to be honest.
Click to expand...
Click to collapse
For me, there is no ro.securestorage.support=true line. I added it with false, but nothing changed.
Zocker1304 said:
For me, there is no ro.securestorage.support=true line. I added it with false, but nothing changed.
Click to expand...
Click to collapse
Sorry for delay. As long as you're running touchwiz, the line should be present. What PDA and CSC are you running?
CurtisMJ said:
Sorry for delay. As long as you're running touchwiz, the line should be present. What PDA and CSC are you running?
Click to expand...
Click to collapse
I think this happened cause I used Barebone Cleaner and removed Knox, but I don't know. When I set up my phone again and didn't flash Barebone Cleaner, the line was still present. Anyway it's set and working now.
Thank you anyway:good:
Related
[Q&A] [ROM][I9305][KK 4.4.2][2014-09-18] **THE GALAXY PROJECT ** [N7105XXUFNE3-v19.0
Q&A for [ROM][I9305][KK 4.4.2][2014-09-18] **THE GALAXY PROJECT ** [N7105XXUFNE3-v19.02]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][I9305][KK 4.4.2][2014-09-18] **THE GALAXY PROJECT ** [N7105XXUFNE3-v19.02]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
thanks
just installed.
thanks to all involved.
have no issues. this is the second day.
s3 gt-i9305t au telstra
batsrule.info
just a couple of questions
third day after install...
s3 gt-i9305t au telstra
- im just a little confused as to why there are issues with youtube.
viewing in app store previews and the youtube app.
- where in this install (rom) can you modify the boot animation and poss the shut down animation?
- whats the reason for the folder on internal sdcard "baidu".
why is it there?
- phone reboots when disconnecting mains power cable.
-app store, google, some apps wont install with error message "Couldn't Install On USB Storage Or SD Card"
thanks.
j_caust said:
third day after install...
s3 gt-i9305t au telstra
- im just a little confused as to why there are issues with youtube.
viewing in app store previews and the youtube app.
- where in this install (rom) can you modify the boot animation and poss the shut down animation?
- whats the reason for the folder on internal sdcard "baidu".
why is it there?
- phone reboots when disconnecting mains power cable.
-app store, google, some apps wont install with error message "Couldn't Install On USB Storage Or SD Card"
thanks.
Click to expand...
Click to collapse
Was this v19? There was known issues with this, and other ROMs based on the Community ROM N7105 Port.
v20 is out now and is based on a proper I9305 based firmware, and doesn't seem to have the known Youtube issues.
The Power disconnect issue is still around I think (unfortunately) but this a kernel-based problem which I can't fix.
At the moment, custom bootanimation doesn't exist in v20 until a hack is done for it.
yes. v19
thanks for answering the rest
got confused - re boot animation " Remove Samsung / Carrier Bootanimation (allow for custom Bootanimations) "
djb77 said:
Was this v19? There was known issues with this, and other ROMs based on the Community ROM N7105 Port.
v20 is out now and is based on a proper I9305 based firmware, and doesn't seem to have the known Youtube issues.
The Power disconnect issue is still around I think (unfortunately) but this a kernel-based problem which I can't fix.
At the moment, custom bootanimation doesn't exist in v20 until a hack is done for it.
Click to expand...
Click to collapse
cheffy11 said:
I can't disable camera shutter noise. I've tried I'm the camera app and in wanam but no luck? Any ideas??
Click to expand...
Click to collapse
Go to
System/media/audio/ui and rename the file shutter.ogg to shutter.ogg.bak
Could we get chromecast screen mirroring enabled or list any market apps that can get screen mirroring working on this build thx
Sent from my GT-I9305 using XDA Free mobile app
serialkillazzs said:
Could we get chromecast screen mirroring enabled or list any market apps that can get screen mirroring working on this build thx
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
I'm researching this at the moment. Hopefully there is a way I can fix the ROM so I don't have to use a third-party app to do it. Worse case scenario I'll search the Play Store and see what I can find.
Doesn't boot
Hey,
I just tried to flash your 20.10 version on my I9305, formerly running TGP 4.3. I'm on TWRP 2.6.3.0 Recovery.
Flashing works fine. But the phone doesn't boot up. I also did the Full wipe (Dalvik, Cache, System, Data, Internal Storage) but all I see when booting up is the "Samsung Galaxy S3 LTE" Screen and then the screen goes and stays black.
Does anyone have an idea what could be the problem here?
Edit: I'm on old bootloader and tried different installation options.
pokkaf said:
Hey,
I just tried to flash your 20.10 version on my I9305, formerly running TGP 4.3. I'm on TWRP 2.6.3.0 Recovery.
Flashing works fine. But the phone doesn't boot up. I also did the Full wipe (Dalvik, Cache, System, Data, Internal Storage) but all I see when booting up is the "Samsung Galaxy S3 LTE" Screen and then the screen goes and stays black.
Does anyone have an idea what could be the problem here?
Click to expand...
Click to collapse
Same here, I'm on new bootloader, philz recovery, I did a full whipe and still nothing
It was fully tested on a old bootloader with a complete wipe using the AGNi Kernel and TWRP Recovery.
djb77 said:
It was fully tested on a old bootloader with a complete wipe using the AGNi Kernel and TWRP Recovery.
Click to expand...
Click to collapse
Aha, I have new bootloader plus philz, I'll try with TWRP
With TWRP 2.6.3.0 it works (2.7.0.0 has some problems with showing aroma files corectly om i9305)
I installed version 20.01 now which works fine. No idea why it doesn't work with 20.10.
Does not connect to the computer
BS"D
Hi. I'm new here Get me beautiful [=
I installed the ROM v20.10 all works very well.
But I connect the phone to a computer to transfer files. It only charges battery. I did not connect memory card or cell phone why?
[I have all the drivers needed + KISS]
A few errors.
Hi all! I flashed this rom a while back and have had a few errors. I did flash the proper modem and all and everything is fairly smooth. I'm not sure if I'm just being too picky, but I'd like to give my feedback and get some opinions...
I really enjoy the standard wanam and exposed installer options!
The errors:
Occasionally, i get repetitive notifications of my text messages. I will view a text message, dismiss the notification and i will get a random notification a few hours later, no new message...
Another problem i have had is with one particular messaging app called line. When i get an onscreen notification (one that pops up even if the display is a sleep), follow the shortcut to view the message, unlock the screen and reply, the keyboard doesn't register text. The predictions will show up but no yext is entered until i exit and re enter the app from the hone screen. This only happens with this app and no other apps that require text input. I have changed the keyboard and reinstalled the app, checked and reset settings... Everything i can think of short of reinstalling the rom. I suppose it could be an incompatibility issue, a bad install of the rom, or the rom has a glitch as far as allowing for this screen off pop-up to app transition.
Beyond that, it's a great development. Thank you!
Feedback and suggestions :
I would love it if there were a few notification bloats removed. For instance, the persistent and annoying earphones connected shortcut notification, the on screen wifi connected notification and the data roaming off (or something to that effect). I have checked and searched for work arounds for these abd couldn't dig anything up. The horrendous touchwiz in this version has seemed to strio away some options that were previously there...
Keep up the good work!
5*
Its working fine the new update !
thx
TGP 20.12 Pin-Lock
Thanks for a great rom. Just flashed 20.12. Unfortunately pin-lock doesn't work
@malsec
djb77 knows this issue and is working on it...
http://forum.xda-developers.com/showthread.php?p=57552303
I just downloaded this ROM.. I have following queries before Install this ROM
1- Please confirm about the battery timings and screen on timings of this ROM
2- Please confirm that this ROM has working blocking mode feature? As I just Installed the Galaxy S5 Project ROM but Blocking Mode is not working in it.. I need this feature
3- I was previously using Amcha ROM 2.0 and having feature of calls/sms blocking like in the screen shot attached.. please confirm that this feature is included in this ROM's settings.. Thanks in Advance..
Sent from my GT-I9305 using XDA Premium 4 mobile app
Uran-235 said:
@malsec
djb77 knows this issue and is working on it...
http://forum.xda-developers.com/showthread.php?p=57552303
Click to expand...
Click to collapse
Thanks, didn't see that
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.
I've been seeing constant complaints around the OnePlus 3's development section of the forums regarding an unusual high CPU usage and massive battery drain on different ROMs. These reports are posted in the custom kernels thread.
flar2's ElementalX kernel thread (now locked unlocked):
[link removed]
eng.stk's blu_spark kernel thread:
[link removed]
The reports mostly state that "(insert kernel name) gives high CPU usage, battery drain, etc." flar2 and eng.stk both say it's not the kernel, yet every custom ROM seems to have issues with this strange "bug". Even stranger, it only affects some users.
So what gives?
To preface, I'll be as verbose as I can about my experience with this: I had this exact issue with the CPU nearly maxing out and massive battery drains on LOS/AOSP-based ROMs. I clean-flashed Resurrection Remix, DU, Citrus, and CypherOS, and I even tried flar2's EX kernel, blu*spark, and stock kernel that ships with the ROMs; every one of them had this problem. On average, I use my phone daily, but not really heavily (I don't play games, but I either web browse, Youtube, or calling/text), so I found it odd that my phone's battery drops from 100% to 72% every time I get up in the morning and down to 15% after only 2 hours of using my phone. I thought this was strange since I never had this problem before. I checked my phone's battery stats (Settings -> Battery) and didn't find anything strange. I blamed CM/LOS and switched to AOSP, same issue. From there was a full day and half of switching ROMs, swearing, and confusion. What I should've done from the start was check the logcat because the solution was literally written all over the logcat.
Something related to the modem was silently crashing in the background.
It would restart again and again, crashing every 5-10 seconds or so. It would comment something about com.phone.android - I forgot to save a screenshot of the message
but nevertheless this error was 5-6 lines long and was scattered all over the logcat. Again, silent crash: no (processes) has stopped, unfortunately, (processes) has stopped, etc). This would explain why my device never entered deep sleep and sky-rocketed the CPU frequency.
To conclude, I firmly believe the high battery drain and CPU usage is actually caused by Oxygen OS's 4.0.x firmware, NOT THE KERNEL. When I switched to 3.2.8 firmware or 3.5.5CE my issue was completely fixed - 10 hours of SOT and very good performance using the EX kernel +AKT combo. I think the reason why some people have this problem and others don't is because they're on different firmwares. Through testing, 4.0.x has these problems whereas 3.5.5CE and 3.2.8 does not.
I want to note that I did not test stock Oxygen OS. The firmware downgrade solution may also not work for you - hence why the thread's title name is "a potential fix". Some users on FreedomOS, Experience, or other custom Oxygen-based ROMs have reported two approaches to fix battery and CPU usage:
The modem/phone errors on firmware 4.0.x could be limited to custom AOSP/LOS ROMs. Using an older firmware may cause Oxygen OS Nougat to not boot anymore, so backup everything and make sure you have a restore point before trying my fix.
TL;DR: This is NOT a kernel issue. Don't blame flar2, eng.stk, or anyone but OnePlus. I believe this is a bug in OnePlus' Nougat firmware. Until OnePlus fix this, I urge everyone to flash either 3.2.8 or 3.5.5 firmware and see if the High CPU usage and battery drains are gone on custom AOSP/LOS ROMs. You can try downgrading firmware on Oxygen OS - but please backup and make a restore point if the ROM does not boot (I did not test stock Oxygen OS). If you're on Oxygen OS, I suggest you try using phhh's root and changing SELinux Policy to permissive first (though SELinux should be enforced) before downgrading firmwares. OnePlus needs to fix their unstable firmwares (and release Camera blobs, etc)!
STEPS:
0. If you're on Oxygen OS, try phhh root and changing SELinux policy to permissive first. If that doesn't work, or if you're not on Oxygen OS, go to the next step.
1. Go to jamal's firmware/modem collection: (link removed)
2. Click the Android 6.x button.
3. Click link to download Firmware + Modem zip 3.2.8 OR 3.5.5CE (I recommend 3.2.8).
4. Flash in TWRP recovery (any recovery version works).
5. Reboot and enjoy better battery life and no high CPU usage
5a. If you set a lockscreen with PIN, chances are that you won't be able to get pass the lockscreen; in that case, reboot back to TWRP recovery, mount /system, use the built-in filemanager to navigate to /data/system, and delete the 5 gatekeeper/lockscreen files.
5b. If your ROM kernel panics after flashing firmwares (screen suddenly goes black, reboots), delete the init.d folder.
UPDATE:
I've been doing some testing with the OOS 4.0.x firmware and I think I found out the issue!
I kept getting the same battery drain on LOS/AOSP-based ROMs. Reading the thread, it seems hardly anybody has this issue on newer firmwares. At first, I thought it was an F2FS issue. I started from scratch by wiping everything (including the internal storage), changed the /data partition to ext4, and upgrading TWRP. When I booted the ROM afterwards and let my phone sit for a few hours, I still had that strange error with the CPU behaving abnormally and battery drain. So I took to the logcat and started searching.
The error that generated heat and battery drain from OOS 4.0.x's firmware is the following:
Code:
Sending non-protected broadcast com.android.imsconnection.DISCONNECTED from system 2019: com.android.phone
com.android.phone? That's familiar....remember how I said in the OP it was a modem issue? But just above the error has this message:
Code:
ImsSenderRxr : Response data: [12, 13, -1, ...
That's Enhanced 4G LTE Mode! All I needed to do was flip the switch OFF and viola! All errors gone, CPU stable and minimal battery drain. Oxygen OS does not error out like this, so I'm certain this "issue" is exclusive to just LOS/AOSP.
Looking at the OP I realize how silly this thread is. I could've just attached the logcat into the Q/A thread and asked for help, done deal. My apologies everyone. If you downgraded the firmware to try this "fix", upgrade back!
For people running Oxygen/Freedom/Experience OS: if you have drain, this fix still applies to you:
Use phh's superuser instead of SuperSU
Using the command:
Code:
su
setenforce 0
or using init.d scripts to change SELinux's policy to permissive
If /data is F2FS, try changing it to EXT4
I'm open to discussion - did this solution work for you? Anyone try this on Oxygen OS? Or perhaps you have a different solution? Comment below, or use the poll! That will help me when I create future OP threads
Instead of complaining appreciate the efforts of eng.stk and flar2. Some are spoonfeed they don't want to search. Thank you for posting this!
madsponge26 said:
Instead of complaining appreciate the efforts of eng.stk and flar2.
Click to expand...
Click to collapse
To the contrary. I really appreciate their work for the OnePlus 3. They're extremely talented developers that I definitely look up to. I just blame OnePlus for the bugs
madsponge26 said:
Some are spoonfeed they don't want to search.
Click to expand...
Click to collapse
I completely agree with this, and it's sad, really. I remember when new XDA members were collaborating with developers and innovating (sorry, Apple). Now it seems like too many members are treating XDA like a technical support site.
madsponge26 said:
Thank you for posting this!
Click to expand...
Click to collapse
You're welcome
I've had this issue as well. I went from Experience Rom to Stock 4.0.2 since when I used Xceed the CPU load didn't go below 60%. But this is not a kernal issue.
I have flashed the 3.2.8 firmware+modem over OB11 and did not experience any bootloops. We'll see how battery fares.
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
peshellas said:
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
Click to expand...
Click to collapse
Well I tried this fix and it doesn't seem to work.. I'm currently on Oos 4.0.2 rooted and bluspark r32 kernel and I still have the hand warmer.. Heat is just reeks from all parts of phone :/
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
sarus_b said:
Well I tried this fix and it doesn't seem to work.. I'm currently on Oos 4.0.2 rooted and bluspark r32 kernel and I still have the hand warmer.. Heat is just reeks from all parts of phone :/
Click to expand...
Click to collapse
When you send the su command did it ask you, and you gave root permissions? Also if you use ARISE you must go to titanium backup and freeze an app called something like arkansysaudio, my spelling might be little off. I clean flashed Experience 10.1 then bluespark r32, then magisk and then phh root for magisk(latest) all was perfect but there was heat etc, after the nevax1 solution that was also gone. Phone is now perfect and passes safetynet security (snapchap, pay, etc)
Edit: In order to use magisk and phh root, you must completely remove supersu(it has an option in the app). So best way should be
0.flash the twrp 3.0.4
1.Flash rom
2.Flash bluspark r32
3.Reboot
4.Extract stock boot.img feom the rom you flash(open it via file Manager, its the first file you see)
5.Go to SuperSU app settings and completely remove it, and say no when it asks to restore boot.img
6.reboot to recovery
7.select install and change to image install, choose the boot.img you extracted and flash it in boot partition when it asks.
8. Flash kernel
9. Flash latest magisk(10.2 at the moment)
10. Flash latest "phh for magisk"
11.reboot
12. Install phh app from play store
13.open magisk and it should ask for root via phh Interface and then show you that magisk a d root are functional (you can test safetynet security on there too with one button)
14. Open terminal and run "su"( it will ask permission), and after that run "setenforce 0"
15. Profit, all should be perfect and you can enjoy it even safetynet free
Optional: download AKT PROFILES 1.2 app(not zip) and install. Run it give it root, and restart it. After that run it choose ballanced or battery saving profile of your choice for even greater battery and smoothness.
peshellas said:
When you send the su command did it ask you, and you gave root permissions? Also if you use ARISE you must go to titanium backup and freeze an app called something like arkansysaudio, my spelling might be little off. I clean flashed Experience 10.1 then bluespark r32, then magisk and then pph for magisk(latest) all was perfect but there was heat etc, after the nevax1 solution that was also gone. Phone is now perfect and passes safetynet security (snapchap, pay, etc)
Click to expand...
Click to collapse
Yes there was a prompt, obviously I won't be using kernel without being rooted..
Anyway I don't use any mods you mentioned yet the problem is still there... It has just decreased now.. Now it depends on my phones mood when to start heating up..
Same here, after the workaround I can't feel that much the heat but the drain is clearly there. Android System was taking 45% of the drain. Using FreedomOS with blu_spark kernel and no mods except Adaway.
peshellas said:
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
Click to expand...
Click to collapse
Yup, I have that in the OP.
lxxs said:
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
Click to expand...
Click to collapse
Like I wrote in the OP, I do not recommend changing the SELinux policy. I also mentioned in the OP that I did not test Oxygen OS, reason being that OOS 4.x seems like a rushed product (so I put no time investing to flash OOS). Since I haven't flashed OOS, I wrote on the bottom of the OP if anyone has modem errors popping up in the logcat. My "fix" is to simply downgrade to a stable firmware (3.2.8 preferably).
Looking at the comments so far, I think Oxygen OS may not be affected by the modem bug. I'll wait and see what people write in the comments and will edit the OP if necessary. Maybe try flashing the firmware, then clean flash the ROM?
EDIT: I just edited the OP so the phhh root workaround is more visible!
lxxs said:
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
Click to expand...
Click to collapse
Yes he doesn't recommend it for safety reasons, but it is far worse to run the phone in a max cores overheating state, it will at some point damage the motherboard and other components. So either this for now or downgrade to another version. Also people with stock op rom have it too, not all though, same with custom roms guys, not all face the issue. And im also suspecting it cam be related yo the kernels not managing selinux properly, but again, some people with custom kernels said ot worked out of the box.
---------- Post added at 10:54 AM ---------- Previous post was at 10:52 AM ----------
sarus_b said:
Yes there was a prompt, obviously I won't be using kernel without being rooted..
Anyway I don't use any mods you mentioned yet the problem is still there... It has just decreased now.. Now it depends on my phones mood when to start heating up..
Click to expand...
Click to collapse
Try all steps, they are not mods, its alternative root. I just did all those as mentioned exactly and problem is gone, I spent hours to come down to this. :fingers-crossed:
After writing:
su
setenroce 0
shall i get any feedback message? or just a new line to write a command?
Hello OP, thanks for getting this point out. I never liked blaming on things which we use for free , plus the devs put a lot of effort.
I have few questions. I'm kind of novice.
I'm on Experience ROM v9.6 with SuperSu 2.78 and modified twrp.
Can I flash the 3.5CE modem over it? I'm kind of scared with Op3.
I don't have anything beside it.
Thanks
AvivEliyahu said:
After writing:
su
setenroce 0
shall i get any feedback message? or just a new line to write a command?
Click to expand...
Click to collapse
There won't be any feedback, but if you go into Settings and to About Phone, then scroll to the bottom, you'll see that SELinux policy changed from "enforcing" to "permissive".
shubhaemk said:
I'm on Experience ROM v9.6 with SuperSu 2.78 and modified twrp.
Can I flash the 3.5CE modem over it? I'm kind of scared with Op3.
Click to expand...
Click to collapse
Try using phh root and changing SELinux first before downgrading the firmware. Don't worry about hard-bricking your OnePlus 3 - I've done bad things like flashing a OnePlus 3t version of custom ROMs (not unified) and I got out of it
Instead of updating old firmware and all, try the following to fix the issue permanently. Will persist across reboots as well -
Extract ElementalX / blu_spark kernel zip
append the following to cmdline parms
Code:
androidboot.selinux=permissive
Repackage and flash from TWRP
File is present at following location in the either zips -
ElementalX - boot/cmdline.sh
blu_spark - kernel/blu_spark_tweaks.sh
Before
Code:
androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237
After
Code:
androidboot.hardware=qcom user_debug=31 androidboot.selinux=permissive msm_rtb.filter=0x237
Its possible swith this with seLinuxModeChanger
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app
Hey @kentexcitebot.
U really saved up many ppl's life with this...
After applying Ur fix my overnight drain is 1-2%, unlike b4 when it was >15%.
It really works , I really appreciate Your work.
Currently my device running Freedom Os 2.2, no kernal, only magisk+phh super su.
and battery is awesome .
Thanks,
Cheers!!!!!!!!!!!!!!!!!
I am using RR build 20170116 and firmware 4.0.2. Never had this problem. It occasionally does not go to deep sleep after screen off. Clear data of Google Play service or reboot always fix the problem.
How can I explain it if there's a problem with firmware 4.0.x?
This rom is OBSELETE PLEASE USE @Linux4 lineage
https://forum.xda-developers.com/ga...om-lineageos-17-1-galaxy-tab-s6-lite-t4167037
What's working or not working?
Thanks for posting this!!
c_86 said:
What's working or not working?
Thanks for posting this!!
Click to expand...
Click to collapse
Everything is working fine from what I know been using it for a week. I think restarting and turning off takes a while though. That's what I've seen
Ok great but the download link doesn't work.
Fixed
Great thanks it's working now..
It doesn't looks like we have the same version of the Galaxy Tab S6 Lite. On my European SM-P910; I already tried both of you roms and it's always a boot loop. I tried different version of the stock rom before flash (XAR) and with blank vbmeta.tar with factory reset or/and cache but it never works for me. Like the other guy for the AOSP I go back to stock.
S Pen Functionality
Hello,
I'm new so please bear with me for this question. Do S Pen functions remain after installing lineageos? I got the device yesterday and I find it to be not as snappy as I'd like.
asiancurry said:
Hello,
I'm new so please bear with me for this question. Do S Pen functions remain after installing lineageos? I got the device yesterday and I find it to be not as snappy as I'd like.
Click to expand...
Click to collapse
You guyz are lucky. There's no development for Tab s6.
Can you make a microg version?
Greetings!
I successfully managed to install the lineage rom on my SM-P610. Initially i faced infinite boot-loop even after doing a factory reset in the recovery. After some experiments, i made it work. Heres what is did to get it work.
1. First, unlock and root your device. Use the method mentioned in the other xda thread. It works.
2. Keep your rooted boot.img safe.
3. Download the lineage os tar from the thread.
4. Using 7-zip, open the tar package and delete the included boot.img fiile,
5. Replace the boot.img with the rooted boot.img obtained from the first step.
6. Flash the modded lineage package with Odin 3.14.1-3b patched under AP (do not check the re-partition in ODIN).
7. After reboot, boot into recovery and do a factory reset.
8. After a couple of reboots, Lineage logo should appear
Will write what works and what doesn't in my next post.
Thanks to @Awesomeslayerg for porting Lineage OS and AOSP to Tab s6 lite. It is really good to see a snappy lineage ROM for the device. Good Work! :highfive:
Here is the list what works and what doesn't.
The ROM is comparatively faster and snappy although the Geekbench results are identical with the stock rom. The reboot time is at par with the stock and the rom is stable. No random reboots or app crashes whatsoever.
Here are the stuff that works
Spen with pressure sensitivity works. Checked with Penup and bamboo paper app.
Can use SD card as primary storage but it is quite buggy. The apps on the SD card always crashes.
Battery backup is way better compared to stock.
Widevine is L1. Netflix HD content playback works.
Dual stereo speakers works.
Double tap to wake works as well
Comes with minimal gapps
All Bluetooth accessories work.
cts profile verification in magisk is "true".
Here is what doesn't work (or might be buggy).
The mouse pointer rather than the dot on the screen. Not sure whether there is a workaround
Magnetic flip cover doesn't work
GPS doesn't seem to work.
Cannot format SD card and use it as a portable media. upon formatting, it always shows "corrupted".
Camera is basic.
Hope you will find this info helpful.
gauthamrgramalingam said:
Thanks to @Awesomeslayerg for porting Lineage OS and AOSP to Tab s6 lite. It is really good to see a snappy lineage ROM for the device. Good Work! :highfive:
Here is the list what works and what doesn't.
The ROM is comparatively faster and snappy although the Geekbench results are identical with the stock rom. The reboot time is at par with the stock and the rom is stable. No random reboots or app crashes whatsoever.
Here are the stuff that works
Spen with pressure sensitivity works. Checked with Penup and bamboo paper app.
Can use SD card as primary storage but it is quite buggy. The apps on the SD card always crashes.
Battery backup is way better compared to stock.
Widevine is L1. Netflix HD content playback works.
Dual stereo speakers works.
Double tap to wake works as well
Comes with minimal gapps
All Bluetooth accessories work.
cts profile verification in magisk is "true".
Here is what doesn't work (or might be buggy).
The mouse pointer rather than the dot on the screen. Not sure whether there is a workaround
Magnetic flip cover doesn't work
GPS doesn't seem to work.
Cannot format SD card and use it as a portable media. upon formatting, it always shows "corrupted".
Camera is basic.
Hope you will find this info helpful.
Click to expand...
Click to collapse
Thanks alot will add this to the list
Thanks again to @Awesomeslayerg for making this rom. Here is a couple of points from my experience.
I flashed from linux using heimdall, which may be why my experience was different than @gauthamrgramalingam.
To flash I just followed the directions and, unlocked the bootloader, went to download mode a flashed. I didn't need to do all the extra steps that @gauthamrgramalingam listed. I did have to factory reset 2 times though, once from the bootloader and once from in lineage. Here are the things I've noticed:
1. Wifi doesn't seem to be working on 5g and seems to have some disconnects, also seems like I can't connect on lower bands of 2.4g, like channel 1.
2. GPS works great for me, no issues
3. Screen brightness, this is hard to confirm, but it at least SEEMS dimmer than stock firmware. I tried adjusting with the treble settings but that didn't seem to do anything.
4. netflix doesn't play videos for me at all. in info, it does show wildvine L1 or w/e and says it'll play HD but when I play a video I just get a generic error and it never plays. I've reset and reinstalled netflix to no avail.
5. SD card is weird, if I format it as portable, I run into the same issues that have been discussed, however if I format it as "phone storage" it seems to work somewhat. Can't seem to move apps to it, but I can put other files on it. Not sure whats going on.
Anyways, thanks again, I thought i would give my feedback to see if it helps.
Zeropoint said:
Thanks again to @Awesomeslayerg for making this rom. Here is a couple of points from my experience.
I flashed from linux using heimdall, which may be why my experience was different than @gauthamrgramalingam.
To flash I just followed the directions and, unlocked the bootloader, went to download mode a flashed. I didn't need to do all the extra steps that @gauthamrgramalingam listed. I did have to factory reset 2 times though, once from the bootloader and once from in lineage. Here are the things I've noticed:
1. Wifi doesn't seem to be working on 5g and seems to have some disconnects, also seems like I can't connect on lower bands of 2.4g, like channel 1.
2. GPS works great for me, no issues
3. Screen brightness, this is hard to confirm, but it at least SEEMS dimmer than stock firmware. I tried adjusting with the treble settings but that didn't seem to do anything.
4. netflix doesn't play videos for me at all. in info, it does show wildvine L1 or w/e and says it'll play HD but when I play a video I just get a generic error and it never plays. I've reset and reinstalled netflix to no avail.
5. SD card is weird, if I format it as portable, I run into the same issues that have been discussed, however if I format it as "phone storage" it seems to work somewhat. Can't seem to move apps to it, but I can put other files on it. Not sure whats going on.
Anyways, thanks again, I thought i would give my feedback to see if it helps.
Click to expand...
Click to collapse
5ghz wifi works fine for me. I wont br able to fix these issues sadly as i dont have time to research and fix. To be honest i just learned how to build a kernel from samsungs sources. But thanks for the feedback
Awesomeslayerg said:
5ghz wifi works fine for me. I wont br able to fix these issues sadly as i dont have time to research and fix. To be honest i just learned how to build a kernel from samsungs sources. But thanks for the feedback
Click to expand...
Click to collapse
I figured you wouldn't, but I thought I'd let you know. again, thanks.
---------- Post added at 07:19 PM ---------- Previous post was at 06:49 PM ----------
Awesomeslayerg said:
5ghz wifi works fine for me. I wont br able to fix these issues sadly as i dont have time to research and fix. To be honest i just learned how to build a kernel from samsungs sources. But thanks for the feedback
Click to expand...
Click to collapse
I forgot to ask, does this have root? because I was trying to do some debugging on the issues but I can't seem to get a root shell in adb.
Messing with it more, couple updates:
1. wifi 5g confirmed working.
2. netflix still not working at least for me.
Magnetic cover, might be due to SELINUX. I see this in the adb debug:
kworker/5:2: type=1400 audit(0.0:2321): avc: denied { open } for path="/sys/devices/virtual/sec/sec_key/hall_detect" dev="sysfs" ino=45321 scontext=u:r:kernel:s0 tcontext=ubject_r:sysfs:s0 tclass=file permissive=0
the magnetic cover might use the hall sensor, but not sure. There is another sensor that is getting AVC denied as well. Worth a look.
Awesomeslayerg said:
If it doesnt boot or bootloops thanks @gauthamrgramalingam
1. First, unlock and root your device. Use the method mentioned in the other xda thread. It works.
Click to expand...
Click to collapse
Which thread? Can someone link it?
Someone and I are working on a TWRP and Lineage nom-gsi version at the moment so stay tuned!!
Awesomeslayerg said:
Someone and I are working on a TWRP and Lineage nom-gsi version at the moment so stay tuned!!
Click to expand...
Click to collapse
awesome, let me know if you need any help.
Which custom rom is best for redmi note 8 in ANDROID 11
Opinions are different from person to person. You should do a research on this subject then choose anything to your taste. Easier this way than asking someone. In this way you'll gain knowledge and you'll be able to provide tips and advises to others.
Anyway, you should stay away from the latest update to A11 from Xiaomi!!! The official update is garbage!!! I regret so much doing this step... lost some useful and basic functions. Looks like their devs are stupid really... or just hate their customers.
Just try whatever you thing is ok for you.
MadK9 said:
Opinions are different from person to person. You should do a research on this subject then choose anything to your taste. Easier this way than asking someone. In this way you'll gain knowledge and you'll be able to provide tips and advises to others.
Anyway, you should stay away from the latest update to A11 from Xiaomi!!! The official update is garbage!!! I regret so much doing this step... lost some useful and basic functions. Looks like their devs are stupid really... or just hate their customers.
Just try whatever you thing is ok for you.
Click to expand...
Click to collapse
You are absolutely right. Android 11 update is like a diseaster
rafat.mym said:
You are absolutely right. Android 11 update is like a diseaster
Click to expand...
Click to collapse
whats the problem? mine works fine and much faster
jjsan said:
whats the problem? mine works fine and much faster
Click to expand...
Click to collapse
There must be something that makes your device smooth... maybe rom variant? Locked bootloader??
Share us more details please.
MadK9 said:
There must be something that makes your device smooth... maybe rom variant? Locked bootloader??
Share us more details please.
Click to expand...
Click to collapse
Unlocked bootlader, rooted (magisk for payment and adaway)
Rom variant is
Miui 12.0.2 RCXEUXM
Full wipe after upading to 11
Thanx.
Well, I also have an unlocked bootloader, but no Magisk and EEA Rom... but did not tried factory reset after update.
I also tried to flash Magisk but had issues with bootloop when I patched boot image and I gave up...
MadK9 said:
Thanx.
Well, I also have an unlocked bootloader, but no Magisk and EEA Rom... but did not tried factory reset after update.
I also tried to flash Magisk but had issues with bootloop when I patched boot image and I gave up...
Click to expand...
Click to collapse
ive installed magisk via twrp (renaming .apk to .zip and flashing)
i've read many posts about wiping data after upgrade
jjsan said:
Unlocked bootlader, rooted (magisk for payment and adaway)
Rom variant is
Miui 12.0.2 RCXEUXM
Full wipe after upading to 11
Click to expand...
Click to collapse
My firend, how did you fix the payment (with magisk)?
Jendrooo said:
My firend, how did you fix the payment (with magisk)?
Click to expand...
Click to collapse
5 days ago something happened and its not working for now. waiting for solution. you can search for cts profile here in forum.
Jendrooo said:
My firend, how did you fix the payment (with magisk)?
Click to expand...
Click to collapse
Android Repository
MagiskHide Props Config v6.0.2-v132 (72) ⚡Magisk Module ⚡Change your device's fingerprint, to pass SafetyNet's CTS Profile check. Set/reset MagiskHide sensitive prop values. Change any prop values easily, and set your own custom props. ⚡️GitHub Repository ⚙Changelog: - Fix problems when trying...
t.me
Remember : A11 sux !
loopypalm said:
Android Repository
MagiskHide Props Config v6.0.2-v132 (72) ⚡Magisk Module ⚡Change your device's fingerprint, to pass SafetyNet's CTS Profile check. Set/reset MagiskHide sensitive prop values. Change any prop values easily, and set your own custom props. ⚡️GitHub Repository ⚙Changelog: - Fix problems when trying...
t.me
Remember : A11 sux !
Click to expand...
Click to collapse
1. In your opinion it is better to install V12.0.4.0 with android 10 or stay on V12.0.2.0 with android 11?
2. After installing MagiskHide Props Config v6.0.2-v132 (72), will I have trouble adding a credit card to gpay? (on android 11)?
Jendrooo said:
1. In your opinion it is better to install V12.0.4.0 with android 10 or stay on V12.0.2.0 with android 11?
2. After installing MagiskHide Props Config v6.0.2-v132 (72), will I have trouble adding a credit card to gpay? (on android 11)?
Click to expand...
Click to collapse
payment is not possible even on android 10 now.
i like 11 more than 10
Jendrooo said:
1. In your opinion it is better to install V12.0.4.0 with android 10 or stay on V12.0.2.0 with android 11?
2. After installing MagiskHide Props Config v6.0.2-v132 (72), will I have trouble adding a credit card to gpay? (on android 11)?
Click to expand...
Click to collapse
1-none , -----> custom rom
2-IDK about payment things
jjsan said:
ive installed magisk via twrp (renaming .apk to .zip and flashing)
i've read many posts about wiping data after upgrade
Click to expand...
Click to collapse
Managed to install Magisk again (older version...), gain root and activated OTA survival on OrangeFox Recovery. So far, no issues but still afraid to try A11 again...
MadK9 said:
Managed to install Magisk again (older version...), gain root and activated OTA survival on OrangeFox Recovery. So far, no issues but still afraid to try A11 again...
Click to expand...
Click to collapse
what were your problems?
best thing for me is setting phone to airplane mode and it lets bt on if was connected before.
and really nice and smooth system
Well, there were several bugs on my device which I was unable to sort them out and decided to go back to 12.0.4.0...
Most annoying one was the impossibility to share a file from file manager by swiping up to a file... A message came on screen telling me there is no app to handle the action on my personal profile or something like that... Whaaat?
Another bug was the 3 fingers screenshot option... Not there... Just not working... Or dynamic icons... This function also was not available anymore...
I had no patience digging for bugs, was pissed and flash the goddamn device with the previous working version of android... Was so angry that I forgot to back up my data and lost all my personal files!!!
But of course, I did not factory reset my device after A11 update... This move, should not exist!!! Why this option is never applied on iphones??? Of course they're not perfect but update after update and never, ever had issues with the device and never had to factory reset it after a major update.... Jesus Christ, this android....
well. i understand that.
3 fingers screenshot can be activated from notifications.
funny thing is possibility to activate new notification centre. its not there. unless you look for it in search. funny thing - your phone has to be in english
i was android developer for 3 years and I like this system just because these possibilities.
im rooted. i can edit hosts file and make adblock perfect and simple.
but for normal people just for using phone there is iPhone. its simple and working.
or also samsung devices are quite good but pricey
About 3 fingers screenshoot: The option was enabled in my device, so even if it was active, the function did not worked!
start camera from lock screen was moved to double volume up but also not working. ist still beta