I solved status bar installing xposed and gravity box.Any tips to increase performance , it's laggy
And why is status bar black ?
Bro from where did you flash your ROM from? External SD card or Internal Storage..I will now try Installing ROM from external SD card after wiping the whole device(including internal storage)
Sorry lol..I forgot to add dmesg..
I have given the LATEST logcat and Dmesg file in the link below..pls see it..
https://drive.google.com/folderview?id=1-8xJgzLeSE8TJxv5gh_ZXTLyXbB-0IcK
---------- Post added at 05:24 AM ---------- Previous post was at 05:21 AM ----------
Bro I tried your method but still It's Bootlooping(stuck on Lineage OS boot animation)
P.s: I have already installed Twrp version (3.0.2)..
/dev/block/platform/sprd-sdhci.3/by-name/misc
dd if=/dev/zero /dev/block/platform/sprd-sdhci.3/by-name/misc count=1 bs=32
THANKS I'll try this and update you..and Don't worry..If I brick my device I'll just flash my Stock firmware using Odin..Maybe this helps (althrough is a different device)
https://github.com/TeamWin/android_device_zuk_Z1/issues/5
You could check if you have this partition/device (or something similar to this):
If you have it and want to try it AT YOUR OWN RISK, *after* flashing the img and *before* booting, try executing this on TWRP terminal:
Again, it's up to you getting the risk....
THANKS I'll try this and update you..and Don't worry..If I brick my device I'll just flash my Stock firmware using Odin..
Did you check dmesg& logcat? Did you get any Idea of what's happening?
Edit: I DON'T have the Misc file in /Dev/block/platform/sprd-sdhci.3/by-name
Edit2:After executing the code given by you The Terminal says Not a directory..
adb shell find /dev > device_list.txt
Yes,I had typed Small 'd' in Terminal.It didn't work..Yes, I checked dmesg and logcat, but didn't find any clue...
Just to confirm: Are you using /dev and not /Dev (capitalized) right?
Other questions:
Is there any tombstone file? I use to look it when playing with Android-x86
While stucked trying to boot the custom img, are you able to connect using adb?
can you generate a list of available devices inside /dev? From your pc, connect through adb and type this:
Regards,
Pstglia
Going to fix camera gimme sources
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
Also pm me on Telegram @sasi2006166
Yes,I had typed Small 'd' in Terminal.It didn't work..
Answers:
1)There is a Tombstones folder in /data but that Tombstones Folder is Empty.
2)Yes,My Pc can connect to the device during the Booting of Lineage OS.
3)I have given the link of device_link.txt pls check it..
https://drive.google.com/file/d/1-9kQ6mkShYxP5i2Z5RHP87jcEHvvnGnr/view?usp=drivesdk
P.s: i)Out of curiosity I flashed the 2.8.7 Twrp and flashed your ROM..It showed Successful but I got the same problem..
ii)I flashed your Previous ROM(The one which you had given in your vid's description) in Twrp 3.0.2 and It showed Successful just like the previous one BUT DIDN'T LOAD.STUCK AT THAT SAME LINEAGE OS BOOT ANIMATION.
Hey man, I think something is wrong, T116NY and T116BU are identical. Here's what I've done:
- Made a Nandroid backup
- Downloaded Opengapps 7.1 ARM Pico
- Downloaded the ROM
- Downloaded TWRP 3.0.2 from dl.twrp.me/goyave
- Wiped System, Data, Cache and Dalvik
- Flashed the ROM, OpenGApps, then TWRP, in this order.
You should try it this way.
---------- Post added at 08:51 PM ---------- Previous post was at 08:47 PM ----------
If it still doesn't work, check if your using the correct version of TWRP (3.0.2) Download it at the link I gave you.
---------- Post added at 08:57 PM ---------- Previous post was at 08:51 PM ----------
PS: I wasn't able to reply the private message
---------- Post added at 09:38 PM ---------- Previous post was at 08:57 PM ----------
When I flashed the ROM, I noticed that it was running on a lower resolution than the normal (480p instead of 720p). If anyone else have this issue, just go to build.prop and change lcd_density to stock value (In my case is 160). Hope this helps!
Hi,
Trying to think something else to try in your case. It's strange the same model/revision with different results
* Was your device rooted when using stock image?
* Don't know if this will work for goyavewifi, but try to use this newer TWRP
* Can you connect through adb during bootloop and collect more info please?
* getprop output
* list all content inside /data please
Interesting info. We can try to compare both versions to see what's different*Your Twrp version didn't work.. Infact No Twrp version above 3.0.2 is working..
Thanks. Props are from the img I posted, right?* I have added the link for Prop file and and /data..Pls see it..
https://drive.google.com/folderview?id=1-K3SQTwf7qiY8IPYeT-kgDJJI4pSWYJE
Trying to find the cause.Edit: Can U guess the problem with my tab?..Cause I don't even know what the problem is..The tab isn't restarting so it can't be a Bootloop right? If you guess the problem even I can start doing some research on it..
As I returned the tablet to it's owner (with the custom img by the way), I can check this now.Edit 2: The total system size on my tab is showing 516 MB is it same for you?
I have given the pic of the same down below pls check it.
Hi again,
Interesting info. We can try to compare both versions to see what's different
The SM-T113NU I had in hands worked with 3.0.2 without problems... (except the compatibility check, wich was bypassed on the generate img.
Thanks. Props are from the img I posted, right?
To be very honest, I'm trying all sort of random things
I'm trying to research on web to find something more consistent
Was your device using the latest stock image before trying the custom ones?
Trying to find the cause.
It's not a bootloop as kernel is up and running (otherwise you couldn't connect using adb)
It seems stuck during some init process/daemon loading (assuming this because logcat stops writting after some gralloc messages)
As I returned the tablet to it's owner (with the custom img by the way), I can check this now.
Will have to ask him
Will find some spare time in order to compare these versions of TWRP
@All
At first this is related to rooting:
https://xdaforums.com/galaxy-tab-3/help/how-to-root-sm-t113-t3076658
But it could be applied to our scenario?
T116BU won't work with TWRP newer than 3.0.2, either. I tried flashing CM11 in my tab, but it failed at TWRP, leaving my partitions corrupted.Yes, Twrp 3.0.2 is working on my tab but all the versions above it doesn't work..The Tab gets stuck at boot.
Yes,The prop file was from your Custom ROM..
I had the old stock firmware on my device(Rooted).. I installed CM 11 and it was running perfectly but as it could not read any internal storage that ROM was not useful..So I flashed LATEST STOCK FIRMWARE on my tab and rooted it by flashing Super su..Even that was working fine.. And then I flashed 3.0.3 Twrp version which made my tab stuck in Bootloop..Then I flashed TWRP 2.8.7 using Odin and then by using Twrp I flashed TWRP3.0.2.After that I flashed your ROM..
So you mean TWRP version Above 3.0.2 corrupted your Partitions right? And btw what will you do to repair your Partitions?T116BU won't work with TWRP newer than 3.0.2, either. I tried flashing CM11 in my tab, but it failed at TWRP, leaving my partitions corrupted.
No, I mean TWRP above 3.0.2 won't boot either. I tried flashing CM11 with TWRP 3.0.2, but it failed. This means that the ROM isn't compatible with my tab, I'm not sure why. To fix the partitions I've repaired them at TWRP, then restored the backup.So you mean TWRP version Above 3.0.2 corrupted your Partitions right? And btw what will you do to repair your Partitions?
Ok Thanks for info..No, I mean TWRP above 3.0.2 won't boot either. I tried flashing CM11 with TWRP 3.0.2, but it failed. This means that the ROM isn't compatible with my tab, I'm not sure why. To fix the partitions I've repaired them at TWRP, then restored the backup.
Yes, Twrp 3.0.2 is working on my tab but all the versions above it doesn't work..The Tab gets stuck at boot.
Yes,The prop file was from your Custom ROM..
I had the old stock firmware on my device(Rooted).. I installed CM 11 and it was running perfectly but as it could not read any internal storage so the ROM was not useful..So I flashed LATEST STOCK FIRMWARE on my tab and rooted it by flashing Super su..Even that was working fine.. And then I flashed 3.0.3 Twrp version which made my tab stuck in Bootloop..Then I flashed TWRP 2.8.7 using Odin and then by using Twrp I flashed TWRP3.0.2.After that I flashed your ROM..
mkdir /tmp/lineage-pkg
cd /tmp/lineage-pkg
last_gen_pkg=$(ls -tr ${OUT}/lineage-14.1-????????-UNOFFICIAL-core33g.zip | tail -1)
jar xvf ${last_gen_pkg}
getprop("ro.build.product") == "core33gdx"
getprop("ro.build.product") != "core33gdx"
cd /tmp/lineage-pkg
jar cvf lineage-14.1-patched-UNOFFICIAL-core33g.zip *
# 1. Boot into TWRP.
# 2. Touch mount system so that the /system is mounted as rw
# 3. Pull the file.
adb pull /system/usr/keylayout/Generic.kl
# 4. use your favorite text editor and change the value of APP_SWITCH
# BEFORE
# key 580 APP_SWITCH
# AFTER
# key 254 APP_SWITCH
# 5. Save file.
# 6. Now push the edited file back onto /system
adb push Generic.kl /system/usr/keylayout/Generic.kl
# 7. reboot back into OS
# 8. recents should work now
this is gonna fix bluetooth soundi have published this rom on the galaxy tab 3 lite community
link : https://xdaforums.com/galaxy-tab-3/...-lineageos-t4110137/post82747923#post82747923
its just an update to fix these bugs
im also working on fixing the camera and sim
---------- Post added at 11:41 AM ---------- Previous post was at 11:35 AM ----------
the bluetooth issue comes from the build prop
# Bluetooth OPP low speed for save power
debug.bt.lowspeed=true
this value needs to be set to false for the bluetooth to work normaly