yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
I've been having that issue with heroes of order and chaos, I think it's an issue with superuser. If you reboot the tablet and restart the app a couple of times it usually gets it running but it can be pretty irritating. Maybe try using superSU instead of superuser? I'm gonna run some tests and get back to you
[Galaxy Tab 3 10.1 Android Development] kb8no:
I restored build 7, your last working build. It works fine. No problem wth Neftlix or TuneIn. It's something with the new build that's broke. The two bìlds have the same superuser.
[Galaxy Tab 3 10.1 Android Development] 92slammer:
so how do you enable multiwindow? with the note 3 you just long press the back button and it shows up
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
I'll look into the glitches in the latest P5210 build, gonna spend the majority of the night working on the LTE build though, as it won't even boot. Bugs should be ironed out fairly soon though.
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
2.1.5 build 4 is now ready for the WiFi, 3G, and LTE models. All 3 ROM files are being uploaded as we speak

changelog: (will be added to OP upon upload completion)

for wifi model:

-rebuilt based on 2.1.4 build 7 to fix whatever was causing FCs on some apps

-removed a redundant binary

for LTE model:

-rebuilt, attempted to fix bootloop.

-removed a redundant binary

-added missing information to build.prop

for 3G model:

-First release!
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
version 2.1.5 build 4 is now live
[Galaxy Tab 3 10.1 Android Development] johnso:
Got fc on com.android,phone .. and if that happens providernetwork gone.. every thing else work so far i can see
[Galaxy Tab 3 10.1 Android Development] kr4zyc1d:
Hey there! Awesome ROM so far. I have been flashing my phone for years, but I picked up the Tab3 - 10.1 for Christmas and just getting into rooting it and flashing a new ROM.

I noticed a few things that might all be related (not entirely sure). Keep in mind, I am on the 1/24 release as I just saw you released on yesterday as well.

- Netflix playback (as others have mentioned)

- Microsoft Remote Desktop - You can create a connection, but when you connect to it, it freezes at loading the desktop and then reverts back to the home screen (my guess this and the netflix playback are the same issue)

- nonsensical begins to launch but then says it had to be stopped

- USB Charging, works from the wall, but when I plug it into my computer (usb 2 and 3) it shows the red X over the battery, and under settings says: 'not charging'

I think thats about it - awesome job so far, excited to see whats next!
[Galaxy Tab 3 10.1 Android Development] Nitro_123:
The USB charging thing is not an issue. The red cross is because the computer can't supply enough power to the tablet for it to charge when being used. Some USB ports support charging stuff and hence give more power over the USB cable and they don't have the red cross :)
[Galaxy Tab 3 10.1 Android Development] Zachisimo:
Also, just because your using a USB 3.0 port on your computer, didn'doesn't mean that your using a 3.0 cable. This same problem occurs with the ASUS transformer tablet. USB 3.0 ports, but aftermarket 2.0 cables dont mix.

Sent from my GT-P5210
[Galaxy Tab 3 10.1 Android Development] kr4zyc1d:
Oh, I understand, but I can ensure that it is at least a powered usb port rather than just a standard port. Just doing general troubleshooting. Did you change settings? It charges when the device was off but not when on, I wasnt sure if this was intended or not. If so, thats fine, just looking to gather information about that. Also, Om not using aftermarket cables.
[Galaxy Tab 3 10.1 Android Development] Lump800:
By my tablet I have the problem that my p5200 is instantly shutting down... Not normally it is only off and then I can start it again..... Is it possible that my battery is broken?

Sorry for my bad englisch I'm German and use school English by my self I hate Google translator
[Galaxy Tab 3 10.1 Android Development] kb8no:
[MENTION=5378432]Restl3ss[/MENTION] Build 2.1.5-4 has the same problem with media programs as 2.1.5-2. I'm going to revert back to 2.1.4-7 which doesn't seem to have any glitches. I was paying closer attention to the "super user granted to shell" this time. I don't ever remember seeing this superuser message in all the years I've been flashing. I looked on my Samsung Fasicinate phone superuser log and not a single record of shell requiring superuser. When I looked in the superuser log after installing 2.1.5-2 there were certainly a hundered of them after a short time. So this time I paid attention and there were zero "super user granted to shell" messages. I looked in the log and just what you would expect (titanium, es file explorer, etc) but not a single super user granted to shell.

I had held off updating the superuser binaries on a hunch. Then I updated the binaries and, bang, all the "super user granted to shell" messages started streaming down the line. Curiously, Netflix did not work before or after updating the binaries so it seems to be unrelated. So I think the super user bug and the media bug are different. Hope these observations are helpful. You are doing great work.
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
Hmmm. I'm getting some bizarre apps requesting super user too. Go into settings - > about and double tap Android version to bring up the Easter egg, there's a superuser request from keychain. I'm thinking the issue has something to do with the new kernel introduced in 2.1.5, I'm gonna try rebuilding with the stock Sammy kernel and see what happens.

On another note, I know what's causing telephony provider to crash on the 3g build, I'll be fixing it next build.

The new builds should be out some time today

Thank you kb8no you're actually really helpful :)
[Galaxy Tab 3 10.1 Android Development] kb8no:
[MENTION=5378432]Restl3ss[/MENTION]. I might have come across something on a hunch. Delete happy patcher with tibu and tell me if that doesn't fix super user issues. I haven't had enough time to fully test it but it's looking good so far. I don't want you to change kernels if it was just one app so I'm dropping this a little early.

Edit: I restored 2.1.5-4. I deleted Lucky Patcher and it did not fix the superuser shell bug. Sorry if Iead you down a road. However, I did the first experiment with the reverted 2.1.4-7 and I still haven't seen a superuser - shell message since I deleted Lucky Patcher. I don't have 2.1.5-5 to try but if all these things hapening in 2.1.5-4 which I believe from your post had the old kernel it is hard to blame the new kernel. I'm going backc to 7 and keep watching the SU log.

Edit 2: I stand by my 2.1.4-7 observation. I restored this ROM to revert back to it again. The restored version still had Lucky Patcher on it because I made the NANDROID before I delted it. The superuser shell thing was again plastered all over the superuser log. I deleted Lucky Patcher again and they all stopped. This did not occur on 2.1.5-4 where deleting Lucky Patcher made no difference.

I have one other observation. I put Lucky Patcher on my Samsung Fascinate which has SuperSU and no superuser shell things to be found anywhere in the log. And remember, no superuser shell things in 2.1.5-4 until I update the binaries. [MENTION=5378432]Restl3ss[/MENTION] I hope these observations are helpful and gives you some clues.
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
all the 2.1.5 builds have the new kernel, it's how I added usb charging. Gonna try a revert and see if it fixes it, i'll pull lucky patcher as well to make sure it's not causing problems :p
[Galaxy Tab 3 10.1 Android Development] kb8no:
[MENTION=5378432]Restl3ss[/MENTION] Read the rest of my edited post which I was working on when you posted before I was finished.

Please explain USB charging to me. It seems nonsensical to me since we chage it with a USB cord to a charger.
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
basically allowing it to charge when it's plugged into a computer instead of just into a wall. Visually there was no change (you still get the x) but in 2.1.5 the battery percentage would go up ever so slowly
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
I'm going to release a new build shortly with the kernel reverted, the build's done i'm just uploading it. Also uploading a new build for the 3g and LTE models, in all 3 builds lucky patcher is removed and lookout has been moved to user applications instead of system app, all 3 builds have the kernel reverted. If this doesn't solve the problem I'm going to release a new build with a different su binary, see if that makes a difference. hmm

i've also fixed telephonyprovider in the 3g build (my bad)
[Galaxy Tab 3 10.1 Android Development] kb8no:
[MENTION=5378432]Restl3ss[/MENTION] By the way, for my money, thanks for changing to Mega.co.nz for downloads. After I got over the horror of having to install an app, it's been clear sailing. I've found it a more stable, predictable, and faster download site with much less advertising clutter and deception. I don't have to remember if Chrome, Browser, or ES File Manager is the one that works on the site because they all work.
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
no problem, mega also gives me 50 gb of storage as opposed to mediafire giving me 15. The upload speed is also faster :p

on another note, I've given you credit in OP for the debugging assistance.
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
Just updated to 2.1.5 build 5. changes are in OP

edit: 2.1.5 build 5 fixes the media issue :) netflix playback working just fine
[Galaxy Tab 3 10.1 Android Development] kb8no:
[MENTION=5378432]Restl3ss[/MENTION] Yes, indeed. Media bug fixed. Bootloop bug fixed. Shell superuser bug fixed. It's a well behaved ROM and fully functional. Now, keep pushing and nibbling away. I'd like to see the USB charge work, it is an important function and I guess it is in the kernel. I want to start exploring all the options built in this ROM now that it is working. I hope all the people on P5200 and P5220 are happy tonight. Really nice work. :D
[Galaxy Tab 3 10.1 Android Development] johnso:
So i tryed the new 5200 rom... phone works but settings FCs when i try to open it .. every thing else works so far ;)
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
I hear you. Releasing a hotfix build in the next 24 hours. Meanwhile you can fix the problem on an individual install by pulling settings / settings provider from a stock rom and replacing the ones in your system directory.
[Galaxy Tab 3 10.1 Android Development] johnso:
Tryed that gehts stuck on samsung logo ... but i did not go back to stock i am still on You rom .. work like a carm ;) atm
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
Glad you like it :) I just added a new build with the settings crash fixed to OP, 2.1.5 build 5.1

edit: i also posted a hotfix to the LTE build, as i'm fairly certain it had the same problem
[Galaxy Tab 3 10.1 Android Development] heartsaver1859:
Is that rom swap ready?
[Galaxy Tab 3 10.1 Android Development] johnso:
Setting work .. everything works ecept multiwindow but i thing that just my tab xD...

thx
[Galaxy Tab 3 10.1 Android Development] :
Multiwindow didn't work for me either...

I hope it gets fixed soon:fingers-crossed:
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
Great :) so other than multiwindow being non functional both the 3G and WiFI roms can now be considered stable. Now if only someone would give me a report on the LTE variant :p

status:

WiFi build: Stable.

3G build: Stable.

LTE build: Considered beta until I can get some feedback from p5220 users.
[Galaxy Tab 3 10.1 Android Development] kb8no:
[MENTION=5378432]Restl3ss[/MENTION] WiFi build seems so far seems stable. My wife used it for many hours so far today. However, out of the blue, there were 13 shell superuser actions in one minute. Then they quit. I'm not so sure we have competely squashed this bug but it is certainly much better.

Please explain launcher advantages / disadvantages between the "touch wiz" launcher and the Google experience "Launcher" options in this ROM. Which one do you prefer or recommend?
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
I definitely recommend the google experience launcher, it's a lot smoother / snappier than the tw launcher, it's also directly integrated with google now. It's generally much nicer
[Galaxy Tab 3 10.1 Android Development] kr4zyc1d:
Updated to 5.5 tonight. Fixed the netflix and RD issue I was having too. Nonsensical is still crashing on launch. Ill take your word about usb charging, I wasnt sure if it would be standard charging time or not, but either way, great to have it.

The only thing I have noticed is ram issues. I seem to always be at 80% usage even after killing all running apps. General slowness when after clicking the home button or pulling up the apps drawer. I can clean flash again, but wasnt sure if this was par for the course. Great rom and update! Well done!
[Galaxy Tab 3 10.1 Android Development] kb8no:
There is some weirdness here. I have never had a tablet before. I have suspected for some time that it charged faster with the stock white USB cord than a non-stock USB cord. Last night my wife was watching Netflix for hours on end and she noticed what I have been suspecting. She was using a non-stock USB cord and the stock white charger could only keep up with usage staying at the same battery level for hours.

Indeed, I changed from the non-stock to the stock white USB cord while using the same white stock charger and it began to charge quickly as it should. So, if I use the white stock charger with the white stock USB cord it charges quickly. If I use any other USB cord, even Samsung USB cord, it charges much more slowly only staying even with the battery when when my wife is watching Netflix.

Anybody else notice this? A USB cord can't be that complicted. [MENTION=5378432]Restl3ss[/MENTION] this could have some implications about your trying to fix USB charging.
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
This one isn't a result of my rom I assure you, Its more so the cable. Use your phone with the stock white Sammy cable, it charges much faster. Different cable = different output, depends on the quality of cable
[Galaxy Tab 3 10.1 Android Development] MobiMikes:
Charging depends upon the cable and the power supply. The galaxy tab charges at 2 amp, some chargers, and most usb ports charge at 0.5 amp (usb 3 ports can charge at 2 amp if the correct cable is used I believe)

My old viewsonic viewpad tablet charged at 2 amp from mains adaptor but it used a cable that had all 10(?) Pins wired if I recall correctly. I don't have the Samsung charger at hand to see if it's similar or not at present.

Caveat: I'm relying on memory here and the information I've imparted is not guaranteed to be correct! :P
[Galaxy Tab 3 10.1 Android Development] LYandroid:
[MENTION=5378432]Restl3ss[/MENTION] it's pretty awesome you have ported this ROM for P5200:),can you upload the ROM file to another file server(eg dev-host,mediafire)?i have slow internet connection as you see in my signature :(,and many thanks to you:).

Sorry for bad enghlish.
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
Mega is actually more dependable than mediafire, and for some reason dev-host doesn't like tab 3 10.1 roms, i upload it and 300 mb usually gets lost off the download
[Galaxy Tab 3 10.1 Android Development] LYandroid:
good point :good:,but i think google drive site is a good option i guess,i don't download ROM's from mega site due to bad internet connection(about 10 hours to download a ROM!!!!).
[Galaxy Tab 3 10.1 Android Development] johho:
Does anyone manage to get gamekiller APP working on this rom (or another gt3 Rom)?

For me the app starts but when performing any search it doesnt find even a single result. :(
[Galaxy Tab 3 10.1 Android Development] kb8no:
I need to understand this to get the most out of my tab. The P5210 USB cord has the usual 4 tabs and ground and looks like any other USB cord. Older USB2 computers only charged at 0.5 amps and newer USB2 computers can charge at 1.0 amps. Likewise some or most phones only charge at 0.5 amps but if you enable "fast charge" in the kernel (if the kernels has fast charge) they will charge at 1.0 amps. Likewise some chargers (wall or 12v auto) only charge at 0.5 and some at 1.0.

I love a phone that has fast charge because sometimes if you are working your phone hard (e.g. wifi teather, data connection, weak signal, screen on bright, etc) the phone is using more than 0.5 amps and is actually gradually discharging while you are charging. (Not to mention just the convience of it charging twice as fast all the time.)

Now we have tabs that charge at 2.0 amps and wall chargers made for 2.0 amps as well as USB3 which charges at 2.0 amp. All this multiplied by the 2.0 amp factor makes it more confusing. So I am using the stock white 2.0 amp charger with the p5210 and with the white stock cable it charges extremely fast. It charges quickly, even when my wife is working the device hard (screen bright, Netflix streaming).

But if I change to a non-stock USB cord without changing the stock charger the charge rate drops dramatically to where the charge just manages to keep up with the usage, similar to a phone not keeping a charge with heavy usage even though it is charging. Does the stock USB cable have exactly the same wiring diagram but just larger wires? Is the difference only because of smaller wire size and voltage drop? Does the hardware/software sense that it is not receiving the full 2.0 amps and automatically throttle it back to, say, 1.0 or 0.5 amps? If I want to use after market 12v chargers for my camper I certainly understand I need to find one that will deliver 2.0 amps (already have them). If I use aftermarket USB cables (for example that have 90 degree micro USB plugs which work much better on this device than the straight ones) what do I need to look for? Just ones with larger wires?

How does all this play into Restl3ss trying to put "USB charge" into the kernel and what does that mean? Does "USB charge" prevent throttling back the charge, maybe? I hope someone has some ideas and some interest in figuring this all out. It's important to me for powering this "off the grid" and for having extra power supplies and charging USB cords at my different computer using positions at home and at work so I don't have trundle the them everywhere I go. [MENTION=5378432]Restl3ss[/MENTION] do you have any thoughts of enlightenment?
[Galaxy Tab 3 10.1 Android Development] Zachisimo:
if you want to buy an aftermarket cable to charge your phone, make sure that it does say USB 3.0 on it and not USB 2.0. There is a difference in the pinning in the cable.
[Galaxy Tab 3 10.1 Android Development] wg25:
Hello,

which version of TWRP are you using? 2.6.1.0?

Thank you.
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
there's only one version out for this tab unfortunately, so yes 2.6.1.0
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
Just added a flashable zip to OP for the aosp kitkat camera / gallery if people would prefer that instead of the sammy one. It's fully functional, but flashing it WILL break your ability to set a custom lockscreen wallpaper, as secwallpaperchooser refuses to use the aosp gallery (and no, I can't fix this).
[Galaxy Tab 3 10.1 Android Development] tcmixx:
For me the 4G dosent work on the p5220 model. Cant seems to get it to work, it only displays no service. Dont know if this is a common problem or just me. Thanks!
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
Fairly sure this is unique to you, I've had a couple p5220 users messaging me for the sake of debugging, so far this is the first report of no signal. Maybe try reflashing?
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
just updated to version 2.1.5-6 (20140129) changes are in OP :p
[Galaxy Tab 3 10.1 Android Development] :
Does multiwindow work now?
[Galaxy Tab 3 10.1 Android Development] johnso:
On my tab multiwindow dosnt work .. at the moment ;) but i think it will soon ;)
[Galaxy Tab 3 10.1 Android Development] Christoph21x:
Don't get it to work here: GT P5220

Doesn't boot and jumps back to TWRP recovery in the second loop
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
Return to stock and follow the instructions in OP to the letter. This is an unfortunate glitch but it's a result of TWRP; I've had that happen to me
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
After looking into it I'm going to have to rewrite a few system files to get it working, I will be fixing it but not in a 2.1.5 build :p expect it to be working when 2.1.6 drops
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
Also the cyanogenmod clock app/widget FCs in the new build for some reason, this may cause problems. To prevent this, drag "clock" in the application drawer to app info and press disable. This will not affect the function of your stock clock / alarm, it's completely separate
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
Just updated to 2.1.5 build 7 (20140130) changes are in OP.
[Galaxy Tab 3 10.1 Android Development] LYandroid:
[MENTION=5378432]Restl3ss[/MENTION],thank you very much for porting the ROM on Mediafire:),downloading........
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
I just bought a mediafire pro account; I was at 12.9 out of 13 gigs used after uploading 2.1.5 build 7 :p So now i have 103 gigs of storage with them, and all my links are now direct downloads with no download speed cap :)
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
Just updated to version 2.2 build 1. Changes are in OP.
[Galaxy Tab 3 10.1 Android Development] luisdelv:
How do I enable multi window ?
[Galaxy Tab 3 10.1 Android Development] :
Great!

I'll flash later and give my feedback:good:
[Galaxy Tab 3 10.1 Android Development] :
I flashed your ROM but I can't enable multi-window...
[Galaxy Tab 3 10.1 Android Development] imagelost:
I did a full wipe with TWRP. Getting a bootloop. Shows that it installed fine. Ill re-download and start all over and see what happens.
[Galaxy Tab 3 10.1 Android Development] kb8no:
I'm not getting "Smart Stay" to work in Pimpdroid. It works in stock (sort of). Anyone else getting the same experience? It's subcritical but now things are working better :beer: smaller things are becoming more interesting. BTW, be sure to Odin the new TWRP release if you haven't already. It's cherry.
[Galaxy Tab 3 10.1 Android Development] luisdelv:
Does multi window work ?
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
Which model are you using?
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
The foundations for multiwindow are there in the new build, but for some reason it's still not showing up in settings. I'm working on it

On a side note, thanks for letting me know about the new twrp release :)
[Galaxy Tab 3 10.1 Android Development] imagelost:
Im using the wifi. 2.2-1
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
The new build can't be dirty flashed whatsoever, and can take about 15 minutes on first boot.
[Galaxy Tab 3 10.1 Android Development] imagelost:
Tried again. No go. I did a full advance wipe with TWRP. Haven't Odin the new version yet. Shows that it installed fine. But after the load image it reverts back to TWRP. Won't load the ROM. I'm going to Odin the newer ver of TWRP and see how that goes.
[Galaxy Tab 3 10.1 Android Development] Christoph21x:
Which model?

Here the same - but not just now, already 2.1.x versions. Has NOTHING to do with the ROM, I guess.

Model here: P5220

Problem: root.zip and recovery are not suitable.

Both are confirmed for 5210 models, not explicitly for 5220.

Anyone successful with P5220? If so - share root.zip and recovery source (and some hints?) with us pls.

Thanks in advance - Chris
[Galaxy Tab 3 10.1 Android Development] imagelost:
Model: 5210
[Galaxy Tab 3 10.1 Android Development] Restl3ss:
If all else fails return to stock 100% and follow the instructions in OP, I can promise you this isn't a result of the ROM but this isn't the first I've heard of this bug; usually the aforementioned will fix it