yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
Not sure if this has been answered before (couldn't find it on a search). But if doing a factory reset Or complete wipe & install I get an FC on setup wizard failed. Anyone else? Anyone got a work around?

TIA to all who can help. Great work as always thanks joshndroid,
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I did what you said...flashed ROM and SU and wiped cache/dalvic....but still getting a bootlop after the dialog "perparing apps"
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
have you considered a full wipe? That normally fixes issues
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
that option I wanna take at last...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ViRuS-MaN:
the zip file are corrupted
[Galaxy Note 10.1 (2014 Edition) Android Developmen] silverom:
Pocket Casts Problem

Anyone uses Pocket casts? Whenever I play the podcast file, it crashes.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
The MD5 pf 5.5 is the same: 153d663f7774c8c5ee3c039802e96bb6
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ViRuS-MaN:
when i want to open with winzip , winzip say not possible to open

when i want to install in my tablet , trwp say the file are corrupted

i dont have same md5

i already download 5 time and same problem for me
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
use 7zip
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I can't get v.5.5 installed doing a clean install with todays open gapps mini. Getting setupwizard stoped after apps optimisation

EDIT: Ok, with open gapps mini from 20160130 I could make a clean install. Now setting up and installing apps
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ViRuS-MaN:
i use 7zip , winzip and winrar for try and same problem for this file

if you arrived to enter in the zip file , it s possible for you you upload for i sownload and try

i want to use winrar for fix but it s not possible
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Dr. Light:
yeah is something wrong with 5.5? says its only like 14mbs
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Slow uploding I think
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
Your right Gdrive is 322Mb (works ok) basket build is only 66.51Mb.

May I suggest since this has happened before that you request joshndroid access to gdrive (as per OP), as that one is always correct

---------- Post added at 08:16 PM ---------- Previous post was at 08:15 PM ----------

small donation conf no 1MY21493G9120620T hope this helps. gr8 work
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I am giving up...I can't get v.5.5 to work....I flashed the ROM an GApps. Everything was fine. Than I rebooten the tablet and restored some apps. Made some changes in the settings rebooted the tablet and installed Viper4Android. Rebooted the phone. Made some other changes....rebooted into recovery and made a backup. Restarted the tablet and bam....bootloop! I don't understand it!

For now I am restoring my backup of v5.0

EDIT: [MENTION=4144316]joshndroid[/MENTION] I have attached a logcat from the time where it reboots. Maybe you can have a look into it? :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Basketbuild may be taking longer to sync server than what it is taking to import the upload.. I'll watch for this next release. It appears as same file size right now for basketbuild and Google shares for me.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Sorry to hear that..

U by any chance get a log of the setupwizard f/c I could browse. I have asked Tema as well as may try something with setupwizard I think ?

What kind of changes did u make? Did u wipe cache or anything while back in recovery? I'm beginning to think this only really affects 32bit at random intervals
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
I had a a very similar issue i used the pico gapps i think there may be something wrong with that gapps itself not sure. Tried banks gapps and the full opengappss and they were ok
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I only made a backup and than rebooted....than I got a bootloop where it comes till "preparing apps" and than reboots again.

I tried than wiping cache and dalvik but got the same result.

I attached a logfile from the time between it is saying "preparing apps" and the reboot.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I have used the gapps (mini-20160130) that I have used too for setting up v4.x and it worked....with the mini-20160325 I got the f/c
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
Yep i think it points to todays open gapps build. Historicaly they do sometimes make a mistake
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
I have been talking to temasek on twitter relating to this.

It would seem that for a clean flash temasek recommends doing 'rom flash, gapps flash, rom flash' as there is a script in the rom that will remove the offending setupwizard.apk that ultimately crashes.

Twitter Quote
@Joshndroid if clean build... Flash Rom, flash gapps, flash Rom again (or optional manual remove setupwizard that comes with gapps)

i was originally thinking it was a boot script that removed the setupwizard and i was going to create a flashable zip, but it seems tema's method removes it within recovery

give the above a try and see if that makes any difference.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Hi, thanks for your reply. I had got it working with older GApps but like I wrote above....right when I had set up everything and made a backup in recovery and rebooted the phone the bootloop started...in the logcat it looks like some value from settings can't be found during boot.

For example....

Can't get key statusbar_clock_color from content://settings/system
android.os.DeadObjectException
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(Binder.java:503)
at android.content.ContentProviderProxy.query(ContentProviderNative.java:419)
at android.provider.Settings$NameValueCache.getStringForUser(Settings.java:1396)
at android.provider.Settings$System.getStringForUser(Settings.java:1671)
at android.provider.Settings$System.getIntForUser(Settings.java:1779)
at android.provider.Settings$System.getInt(Settings.java:1774)
at com.android.systemui.statusbar.policy.Clock.updateClock(Clock.java:246)
at com.android.systemui.statusbar.policy.Clock.updateSettings(Clock.java:414)
at com.android.systemui.statusbar.policy.Clock$SettingsObserver.observe(Clock.java:142)
at com.android.systemui.statusbar.policy.Clock.onAttachedToWindow(Clock.java:193)
at android.view.View.dispatchAttachedToWindow(View.java:14545)
at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2843)
at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2843)
at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2843)
at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2843)
at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2843)
at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:2843)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1372)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1115)
at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:6029)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:858)
at android.view.Choreographer.doCallbacks(Choreographer.java:670)
at android.view.Choreographer.doFrame(Choreographer.java:606)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:844)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5463)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
Can't get key clock_use_second from content://settings/system

temaseak is talking about removing setupwizard that comes with gapps as optional option. Is he talking about Core\setupwizarddefault.tar.xz and Core\setupwizardtablet.tar.xz ?

EDIT: Ok, I continue next weekend...I can't get v5.5 to work. Everytime I have set up the tablet and reboot into recovery and restart the phone I end up in a bootloop....back to v5.0 till next weekend.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Try clean flash, wipe system, cache and dalvik... Then flash rom, gapps, rom then supersu 2.65 stable then boot to rom that seems like the easiest and foolproof method based on what temasek advised
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I did that. The tablet started...after I restored the apps and made my changes within the settings and rebooted to recovery and restarted the tablet I ended in a bootloop-

EDIT: I will try again next weekend.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
That seems like it's something else then, specific to your setup by the sounds of it
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I did the same steps like I did to set up the tablet before.

Will see next weekend. Will start again from scratch.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mising:
Just as an FYI, I was having the Setup Wizard crashing issue as well.

As suggested, I rebooted to recovery and reinstalled the ROM only without further wiping, and all is well!

I had to set up everything manually that wizard would normally take care of (wifi, Google acct, time/date, etc) but that was a no-brainer.

Seems to be running great so far!

Thank you
[Galaxy Note 10.1 (2014 Edition) Android Developmen] lost_knight:
Difference with official cm13

I just saw (at cmxlog) that official cm-13 builds have started for lt03wifi. Can anyone tell me what the differences with this build are aside from the filesystem, kernel? Does camera work there? Any information would be great. Thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I can only see it for lt03lte.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
its here https://download.cyanogenmod.org/?device=lt03wifi. I tried the very first build, it's no where near as good as this one. Josndroid's rom has many more features. Also cm had some display issues. That may have changed in latest.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Ah, ok, thanks! I have looked at cmxlog and didn't find lt03wifi. :good:

---------- Post added at 11:20 AM ---------- Previous post was at 11:19 AM ----------

I think the main difference is that this one contains changes from temaseak... [MENTION=4144316]joshndroid[/MENTION] correct me if I am wrong. :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] lost_knight:
I only see the 12.1 builds there. I saw the 13.0 directly on cyanogenmod's Jenkins server, then checked cmxlog com and sure enough there is some interesting activity. The only reason I'm not using Temsasek's is the camera issue, so if anyone is adventurous enough to try out the new official hidden (because it is not visible on cm download page) build that will come out in a couple of hours, I'd appreciate the feedback.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
status bar, nav bar, gestures, all sorts of other additions in temasek over stock cm rom. its whateve ryou want really, i build both atm

considering at the moment i am the maintainer for cm-13.0 and lt03wifi i would know if there is an official version. Which there is not, i dont want to push trees to cm when they contain broken camera. It's just not ready yet. I build an unoffical build to keep things going for those interested (in fact one is uploading right now).

The temasek v5.6 is uploading now as well. Some device tree changes, kernel changes and a couple vendor changes, picked from shevT
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Are you using a settings backup and restore app to restore your settings? There was a post recently on Google plus that stated that these apps will sometimes cause bootloop's on marshmallow due to Google setting up their own settings backup and restore method.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I made a backup of a clean install of the ROM and GApps....At some point of the whole install and setup process I have restored the setting using TB. I don't think it is included in that backup...but I can't tell it for sure...for that reason I will restart from scratch.

I did get the same error when I dirty flashed v5.5 over v5.0....
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
V5.6 is up on Google shares and basketbuild
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Great work. I realize definitely performance improvements. My sidebars open same smooth as on temasek 18.5 cm 12.1 build back in the days, now. Thanks to you Josh and also to shevt and tema.:)

---------- Post added at 01:37 AM ---------- Previous post was at 12:59 AM ----------

Ohh, and i realized, that menu button seems to work on all my apps. I think the three dots to enter menu can disappear with the upcoming builds, now. Like it was plant on temasek cm 12.1.

---------- Post added at 02:22 AM ---------- Previous post was at 01:37 AM ----------

Display rotation causes screen distortion...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Good......

Thank you
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
V5.7 up on Google shares and basketbuild
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Damn I just download v5.6
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
I think there is a problem with 5.7 and display driver.

screen sometimes gets briefly mess up example when rotating

Reflash 5.6 and the same, I will clean install.

anyone else?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] sorenkierk:
I'm having the same issue with 5.7. I came from 5.4 where the problem didn't exist.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Going to try 5.4

Afraid it is tablet malfuncion

Confirm: Driver has issue, since 5.6
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Clean flash doesn't solve the problem. The issue starts with v. 5.6 as joshndroid updated the rom with the latest updates by shevt. On v. 5.6 screen distortion is only during screen rotation. With v. 5.7 screen distortion affects also recent apps overview and Multiwindow function doesn't work correctly anymore. I hope upcoming builds will solve this issue, because temasek includes some good new display functions in his latest build and i like the new display resolution.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Smac7:
Not sure if it's a "dirty flash" problem or a ROM problem, but I flashed the latest (5.7) and it created some issues. Everything was large as if the DPI was changed. The Google launcher icons lost their text beneath them and the check weren't lined up with any check boxes. I tried to lower and raise the DPI settings but it made every extremely tiny and now modifying that back to where it was previously has no effect.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
I see that I am in fine company with my troubles on the 5.7 build. Definintely looks like a driver malfunction. It's almost as if the screen res settings have been going to "pot". I thought it might have been from my dirty flash as well. I used the open gapps aroma version, but the setup interface is really confusing. The setup almost requires on to input double negative settings. Instead of having pre-checked boxes, they should ALL be unchecked so we may have better input. But, maybe that's just the way this old fart sees things. Hope we can find a work around for this cuz if my displays gets any smaller, I won't be able to read it at all. ;-Deano
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Yeah Yeah I hear ya lol[emoji14].. Might revert a couple things lol
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
Hi, haven't tried extensively, but rotation etc. don't cause trouble for me. Could anyone who has the problem say where exactly you encounter the problems? Apart from that, 5.7 is the fastest ROM in a while for me, got me 944/3005 on geekbench 3 (may actually be within the margin of error, but kinda cool to have over 3000, which I normally only reach on the hlte).
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Aletheia:
Not a bug report!

So ever since r22 (version 5.0) I've been getting periodic screen crashes, as in the screen goes backlit dark but sound, vabrition, etc works. I'm guessing since I've not heard any other complaints its something on my end and I just wanted ta ask if anyone had an idea as to what the problem could be?

So far I've only excluded xposed as the culprit. I'm currently running a nand backup of 4.8 with out any problems so no worries just curious really...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Ähhmmm... i need to add an issue.^^

Infrarot also doesn't work anymore on my device...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
If you are using pie or omni switch disable it and reboots stop.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] israel_andrade:
I've seem a slight breakup of the display while watching Netflix. Looks like a brief second of dashes on the display. Also, get a buzz on the audio every once in awhile. One final issue, not sure if it was a fluke or what, but I was using the S-pen and the tablet kinda locked up, so I rebooted and got stuck in a bootloop cycle until I put the s-pen back into the tablet, then it booted fine. have not seen this happen since.

Here is a update, I get the dashes on the display simply by rotating the tablet from portrait to landscape. Also, how do I increase the display picture. Everything is so tiny on the browser.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
[MENTION=4144316]joshndroid[/MENTION] last weekend I wasn't able to flash v5.5 now I flashed v5.7 wishout a problem over v5.0

The only difference I flashed RC-SuperSU-v2.70-SYSTEMMODE.zip before and after I have flashed the ROM.

Till now I can't see the display problems...how can I reproduce that?[COLOR="Si[QRCODE][/QRCODE]lver"]

---------- Post added at 04:13 PM ---------- Previous post was at 03:42 PM ----------

[MENTION=4144316]joshndroid[/MENTION] ok now I have a problem with the display too....the keyboard is way to big!

Switched to 200dpi rebooted and back to 160dpi...it stays at 200dpi...at least the resolution.

The more I change the dpi to a lower dpi for exmaple back to 160 the smaller the symbols get....:confused:

Have to go back to my back :crying:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Change it in the build.prop
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
But before I changed any dpi my keyboard was way to big. It looked like for a bigger resolution

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Use a keyboard like SwiftKey so u can change the size of the keyboard independent of the dpi
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
[MENTION=4144316]joshndroid[/MENTION] I use that keyboard...what happend was that I only could see less than half of the keyboard....the buttons have bean huge and the text prediction as well.

EDIT: It must have to do with the themes (no the keyboard theme)....if I use the default CM theme tham the keyboard has the right size but if I use a theme from playstore the buttons get huge....when I change back from default theme to my theme the keyboard is ok till unexpected it gets big again.

EDIT2: The build in AOSP works
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
We all have problems with screen resolution and distortion since v. 5.6. Some apps also don't show the right screen resolution like my translator app and multiwindow function. Wait for the next build, if the changes from build 5.6 are reverted. It has maybe to do with the updates by shevt. Maybe there is also a kernel issue because infrared doesn't work anymore.

.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
After about 8 builds today for lt03wifi V5.8 is uploading..... hopefully the display issue is atleast reverted to what it was
[Galaxy Note 10.1 (2014 Edition) Android Developmen] konserninjohtaja:
Why google play is saying "device is not compactible with this version" whe i am trying to install chrome/firefox/google keep...?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] algieba:
Unfortunately the zip is missing on Basketbuild.

Thanks for your work. You make a very good job!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Bro it's not up yet still uploading I will notify when complete the prior post by me was a bit of a status update not rom release just yet
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Lol!

But you know we are flashaholics, .. thirst ..
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ViRuS-MaN:
when i open my tablet i show galaxy note 10.1 edition 2014 very long time i dont know why , because before i dont see long time
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Flashed build 5.8. Screen distortion in recent apps/during screen rotation & resolution issue still there and also no working infrared...:(
[Galaxy Note 10.1 (2014 Edition) Android Developmen] aridity:
Flashed 5. 8 as well, but still the same weird display error with small icons and the line distortions when turning the tablet...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Ok, it seems like the choosable screen resolutions in display& LED options are optimized for hlte and not for tablet. I changed from standard (160 DPI) to 200 and 140 and back to 160 but i don't get the old resolution back. Everything is too small, now. Dirty flash an older build doesn't make a difference. This is a huge problem, now...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
Have to agree with all the others display is worse (tiny + distortions) went back to 5.7 but problems still persists. Sorry Joshndroid.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
I think dirty flash doesn't change screen resolution. Maybe clean flash is necessary...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] marcmv:
FYI 320 dpi is default. I have been using 240 with success. Anything lower and it's no good for me. I am trying to download 5.8 now and try my luck with it.

If you want to manually change the DPI I found this article or from what I've researched you can type wm density <dpi> from a shell... ie

wm density 320

http://wccftech.com/article/increase-screen-dpi/

1. Open Root Explorer.

2. Go to /system

3. Click on Mount RW (It should appear as Mount RO, that’s when it is correct!)

4. Look for build.prop. Long press on the file and press Open file in Editor

5. Scroll down to ro.sf.lcd_density=XXX

6. Change the XXX to the desired DPI

7. Click on the Menu button, and Save and Exit.

8. Reboot.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
I restored nandroid backup and dirty flashed v. 5.5 again to get working infrared back. The screen resolution options in display and LED are wrong. So i can't enable 320 dpi again. For now everything is ok again, but thanks for your tutorial.

Update: You're right. It was necessary to change it in build.prop to 320 manually. Now Screen-Resolution is fine again.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
Reverted back to 5.5 backup I had and all is good again. I don’t think any releases since then have been right. Shame keep going joshndroid your hard work is still very much appreciated