yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti] CarinaPDX:
A little clarity:

There are ROMs based on the official Samsung ROMs, and they generally support all of the same features as stock but without bloatware and with additional features. Civato's excellent ROMs are a great example; they perform better, have more features (particularly kernel-based), allow the user to select which bloatware to install, and generally are wonderful. Consider it stock ROM fixed up. I have used them for nearly a year and can recommend them highly. This means you get S-Note, and Allcast I believe at this point. There have also been other apps that have been ported from other Samsung devices to this ROM.

Other ROMs are based on AOSP (Android Open Source Project) and do not include the Samsung-specific software. No TouchWiz, S-Note, or any app that depends on the Samsung APIs in their stock ROM. The Photoshop app that is shipped for Samsung crashes immediately on my OmniROM and I had to uninstall - I guess that it is calling a Samsung API. So now, with Omni-ROM I will be dealing exclusively with the world of generic apps, which is not a problem. The stylus works out of the box. To have an app launch when the stylus is removed it is necessary to add a non-free app from the store. This will also enable other features of the pen. There are stylus-supporting note programs (e.g. Papyrus) which work just fine. Most apps using a stylus should work (e.g. Sketchbook) unless they were written using the Samsung APIs, in which case that should be obvious in the store as they will be Samsung-only apps. Edit: if you like to use the stylus for general text entry then you will need to get an app for that as well; they are available - but the neat way that the Samsung keyboard can switch to stylus input is lost.

I have no knowledge of the Allcast issue, other than noting that there are apps available. DLNA is certainly available through any number of apps for any ROM.

You will find a good source of ROM info on this thread: http://xdaforums.com/showthread.php?t=2630650
[Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti] ramjet73:
Both AllshareCast (Miracast) and Chromecast screen casting work fine on the most recent [MENTION=3986004]civato[/MENTION] ROM's (FlexNote 3.0 and FlexBurst 1.0). This app and the official app are required for Chromecast screen casting.

ramjet73
[Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti] mrmrmrmr:
Hi,

I would like to make some clarification to my question. By "custom rom" I meant "non-Touchwiz based" rom. Of course, Samsung/Touchwiz based roms do support everything related to Samsung APIs.

So my question is;

with a non-Samsung based rom, shall I be able to use S-Pen with 3rd party apps ? (like Adobe Photoshop - not the one distributed with Samsung devices but the commercial Store version)

Also does miracast work with them ? (not DLNA , real screen mirroring)

Thanks.
[Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti] User_99:
Yes you can use your stylus. Miracast depends on Rom kernel development. Due the fact that this is included in Stock Samsung Kernel Source maybe not working...

That is a problem of all Samsung devices, lack of Source code...
[Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti] mrmrmrmr:
Ok. Allshare Cast is Samsung feature but AOSP based roms do have Miracast support , correct ?
[Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti] ramjet73:
That's not necessarily true.

Some custom ROM's based on Samsung stock break things that work on the official ROM by using a different kernel, modifying the framework or implementing alternate versions of Samsung components from other devices. You need to check the OP and read through the thread to determine if any stock features are broken or missing.

It is definitely harder to mimic all the features of the stock TouchWiz firmware on ROM's compiled from AOSP source. If you plan to use one of those ROM's you really need to verify that the features you use/need are available and can expect to add several third party apps to get anything close to stock sPen support.

Here's a similar thread from last October and this post should help with fleshing out Spen support for AOSP ROM's even though it was written for the Note 3.

Allshare Cast is just Samsung's name for Miracast but it is still certified by the WiFi Alliance so it should be compatible. From the Wikipedia article on Miracast:

Chromecast screen casting is different and obviously requires a Chromecast device. I have done both successfully on the stock ROM and the latest versions from [MENTION=3986004]civato[/MENTION] but don't expect either to work on AOSP based ROM's at this point. They do work with the M10 snapshot for CM11 on my Nexus 4 but the Note 8.0 is not a Nexus device and I think those functions are highly dependent on the kernel used.

If you want all the features of the Note 8.0 working then you should stay with something close to the stock ROM. It will take a lot of time, effort and some money for apps just to get away from TouchWiz interface.

ramjet73
[Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti] mrmrmrmr:
paying for 3rd party apps is not an issue if there are apps supporting S-pen.

I would stick with Samsung ROM if I believed Samsung will support this device anymore. But I doubt Samsung will release Android L to it.

So , I should turn to non-Touchwiz rom at some point. (I like the idea of 8 inch note device, and Samsung doesn't release a 2014 edition replacement)

2 things important for me on the Note device:

- S-Pen usability with 3rd party apps (I understand that non-Samsung roms support S-Pen)

- Screen mirroring (miracast should work if the rom is based on AOSP)

Any advice for a good non-Touchwiz rom ?
[Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti] ramjet73:
"Should" and "does" are two different things.

Out of curiosity, I loaded the M10 snapshot (the latest) for CM11, just to see if it supports screen casting for Miracast and/or Chromecast. The answer is "no" and it doesn't even appear in the display options for settings even though the M10 release for my Nexus 4 works fine with both. :rolleyes:

The moral of the story is don't expect much better support in the future from the AOSP ROM makers. CyanogenMod will probably release an L (CM12) version since the N51xx is an officially supported device but don't expect it to support all the features of the Note 8.0 that the stock ROM does.

For a ROM recommendation, I'm planning to stay with the enhanced stock versions from [MENTION=3986004]civato[/MENTION].

ramjet73
[Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti] CarinaPDX:
I appreciate your confusion on the stylus support, so let's talk about that. First off, the stylus is not unique to Samsung. Most if not all ROMs will provide the status of the raw stylus data (location, pressure, button, storage slot) to applications. Programs written to access the stylus at this level should work on any device that has the (Wacom?) stylus, Samsung or not. The PS Touch in the store should work fine on AOSP - the one I tested last night was a freebie tied to the Samsung ROM and didn't work on Omni-ROM (no surprise there). The fly in the ointment is that Samsung includes a library of stylus functions in their ROM which makes it easier to develop apps for use with a stylus, and which will lock the apps to Samsung devices (the APIs are Samsung-specific). Any app using those APIs will not work on AOSP ROMs. It is easy to tell the difference in the Store because those apps will be for Samsung-only; if it works on non-Samsung devices it is a good bet it will work with open ROMs.

In addition to the stylus software library, Samsung includes software to do things when the stylus is removed from storage or touches hot-spots, a keyboard option to use the stylus and handwriting recognition to create text input in any program, and stylus-enabled programs like S-note that can also convert your scribblings to text with varying levels of success - YMMV. These functions can all be added back into AOSP ROMs with programs from the store, at a modest price. Of course they will be a little different but the functionality will be there.

My recommendation would be to go with Civato's latest ROM (FlexBurst) for now, assuming you are using your stylus a lot and enjoy the Samsung implementation. Civato has added into the ROM support for aircommand, which is available on other Samsung devices but not stock for the Note 8. Also, there are newer versions of S-note available. Samsung (and thus FlexBurst) is currently at 4.4.2, while Omni-ROM is at 4.4.4; I don't see the small lag as anything important at this stage. Once Samsung stops supporting it there will be time to convert to AOSP. In any event once your Note is rooted and TWRP Recovery installed it is a simple matter to make a Nandroid and Titanium backup before installing a new ROM to try out; if you don't like it then wipe and reinstall - not a big deal. The only downside is that you will break your warranty if you have a KitKat bootloader (required for Civato's latest as well as Samsung's latest).

Hope this helps,

Greg
[Samsung Galaxy Star] Zurickhi Adara:
Please help me how to solve Flashing error!!!:crying:
[Samsung Galaxy Star] akshaygalaxystarmod:
What kind of error
[Samsung Galaxy Star] utkarsh agarwal:
Maybe you zip is not a flashable zip

If i helped you please hit thanks :D
[Samsung Galaxy Star] akshaygalaxystarmod:
Tell bro what kind of problem ?
[Galaxy Tab 4 Q&A, Help & Troubleshooting] Aiman Alrubaiee:
hi

when i want to register my Tab 4 in Samsung website, its say the serial number is invalid.

i bought it from UAE as a new

i checked IMEI in imei.com and it doesn't say the imei number is invalid, but error msg say : We're sorry, but at this moment we can't find required number.

i connect it to Kies, and its look ok, buuuut the battery doesn't charging.

plz, may tab is orignal or faked?

Tab 4 10.1

SM-T351NZWAXSG
[Galaxy Tab 4 Q&A, Help & Troubleshooting] repey6:
Install the program Phone INFO ★ Samsung ★ and you will be happy. https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
[ONE Q&A, Help & Troubleshooting] anhtin:
HI all,

After root, and trials of IUNI OS, I realized that my fast boot screen is not just one line of some chinese words and the word fast boot, nothing else. How can I go back to the original English version of fast boot?

Also, when I charge the phone while its off, the battery icon is not showing anymore but just the One Plus logo on. Any idea how to fix it?

Thanks so much
[ONE Q&A, Help & Troubleshooting] zephiK:
https://cyngn.com/products/oneplusone/

Scroll down to Factory Images

And fastboot flash the bootloader.
[ONE Q&A, Help & Troubleshooting] anhtin:
is that file boot.img?
[ONE Q&A, Help & Troubleshooting] zephiK:
No thats the kernel. Usually on Nexus devices, its fastboot flash bootloader bootloader.img but on the OnePlus One its another file.

I'm not sure which one it is but try them all,

I removed the ones that wouldnt make any sense towards the bootloader. If it was my guess, it could be sbl1, so try that first.
[ONE Q&A, Help & Troubleshooting] anhtin:
that's it!! Thanks so much
[Android Q&A, Help & Troubleshooting] puttputtmoo316:
Hi guys.

So today I was like experimenting with my phone (3 months old) and I was trying to install new ROM on it. I couldn't install custom ROM (CM 11.0) from my recovery mode because I was always getting some sort of errors so I took it to the next level and tried to do it with my PC. I downloaded ROM on PC and tried to install it with fastboot mode and the program that I downloaded on my PC asked me to flash .img file not .zip and I(dumbass) found boot.img inside of .zip file and selected only that boot.img file and flashed it. And now its stuck in boot loop.

My phone is not really famous and its not brand phone. It's "H18 NOA C24" some copy of S3 Mini I couldn't find the stock firmware or ROM for it on the internet. Please help, tell me what can I do to bring my phone back to live.

Thanks :)
[T-Mobile Samsung Galaxy Note 3] c-pimp:
What is the best practice procedures from going from root de la vega MI7 running wicked rom knox 0x0 to a current kitkat recovery, bootloader, kernel, rom... I no longer care about knox.

If someone can give me just the basic steps I can figure everything else out but I am confused if I cf autoroot or after upgrade to kitkat and what can or cant be done in odin or what would be the best method to go straight to current builds...
[T-Mobile Samsung Galaxy Note 3] Misterjunky:
Re: upgrade to latest N900T latest firmware.

The very best thing you can do if you don't care about knox is to go to

http://SamMobile.com and download the official kitkat NF9 4.4.2 stock

firmware to start with. You can also download it from this link below:

http://tinyurl.com/of4dgnr

Use Odin to flash this firmware. (you cannot flash this using twrp/cwm)

Be sure to do a full wipe before odin flashing.

Then you need to flash cf-autoroot and twrp custom recovery.

Here are the direct download links for cf-autoroot and twrp custom recovery.

Use odin to flash both cf-autoroot and twrp but flash cf-autoroot first.

CF-Autoroot:

https://dl.dropboxusercontent.com/u/...mo-smn900t.zip

TWRP custom recovery:

https://dl.dropboxusercontent.com/u/...ltetmo-4.4.zip

Once you have rooted the phone and flashed twrp recovery you are

ready to go, and you can then flash any of the custom roms available

here in the Note 3 N900T threads.

Good luck.
[LG G2 Mini] Lukiqq:
Hello, I'm trying to compile my own kernel from sources for this piece of hardware, everything went well and I completed the whole process, but with my kernel device doesn't boot up and stuck on boot screen at bootloader stage (fastboot mode). I'm using CNexus Boot.img tools from here. To obtain

PAGE SIZE: 2048

BASE ADDRESS: 0x00000000

RAMDISK ADDRESS: 0x01000000

I've used arm-eabi-4.6, stock and working kernel with command ./boot_info boot_327680.bin so I think, these parameters are ok.

[IMG="boot_info"]https://imagizer.imageshack.us/v2/1141x112q90/537/w08sKW.png[/IMG]

Whole ramdisk image is also taken from stock kernel with command ./split_boot boot_327680.bin. Configuration used ".config" comes from stock kernel too. Even after compilation of pure split image, device won't boot...

This piece of code I'm using to compile kernel image for example:

./mkbootimg --kernel boot_327680.bin-kernel --ramdisk boot_327680.bin-ramdisk.cpio.gz --cmdline "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 msm_rtb.filter=0x37 androidboot.hardware=g2m" --base 0x00000000 --pagesize 2048 --ramdiskaddr 0x01000000 -o test_stock.img

It looks like in newly compiled kernel at the end of file a lot of code is missing.

You may open following files with hex or text editor to see what I mean.

Stock kernel:

https://www.dropbox.com/s/0jidfk7jcsopvy7/stock_boot.bin?dl=0

Compiled one:

https://www.dropbox.com/s/ceui3620ief7m5j/test_stock.img?dl=0

Any suggestions?
[LG G2 Mini] Lukiqq:
Really? No one can help me? :(
[LG G2 Mini] Zaaap72:
What about dt image in boot image?
[LG G2 Mini] Lukiqq:
Thank you for that, didn't really know about that, now I have to find out how to build dt.img or extract it from stock image.

Wysłane z mojego LG-D620 przy użyciu Tapatalka
[LG G2 Mini] Lukiqq:
I managed to build working kernel but something is still wrong with graphics, there is no image, display stays black. I can hear that system boots up and touch is working, adb is working too.

EDIT: Attached here kernel with broken video and logcat of it.

If someone want to test it and help me to find out the problem, do nandroid boot backup first!
[LG G2 Mini] partyzant_x:
Guys for CM we need CAF kernel. Kernel from me is CAF and need couple of fix but system is boot and working.
[LG G2 Mini] Garcia98:
Which sources did you use?
[LG G2 Mini] Lukiqq:
Pure stock sources from LG site.
[LG G2 Mini] partyzant_x:
Can You post a logcat file with that command : logcat *:E
[LG G2 Mini] Garcia98:
And are you using stock ROM?
[LG G2 Mini] Lukiqq:
Yes, stock odexed ROM.

PS. Repacked with this method and then compiled stock boot.img is working ok, so I assume something is wrong with zImage instead of ramdisk.
[LG G2 Mini] Garcia98:
Which defconfig did you use?
[LG G2 Mini] Lukiqq:
I've used extracted config from stock kernel and d620 global, both failed same way...
[LG G2 Mini] Garcia98:
If you upload the source that you used to GitHub I vould help you more, because I doubt that you used stock kernel source code plus stock defconfig, as in logcat appears some errors of missing functions that are defined in stock kernel source ;)
[LG G2 Mini] Lukiqq:
Here you go, kernel compiled from clean LG sources + Garcia98 config file cyanogenmod_g2m_defconfig. Still working system with black screen :(
[LG G2 Mini] Lukiqq:
I give up... tried one more time with Zaaap72 CM kernel sources and this time I've got bootloop right after first LG logo appear :-/
[LG G2 Mini] Lukiqq:
Still no ideas? C'mon DEVS! Any help would be greatly appreciated! :(
[LG G2 Mini] judas1977:
OT.

Are you THE Lukiqq, who made kernels for spica???
[LG G2 Mini] Lukiqq:
Indeed, now I'm the one who needs help :)
[LG G2 Mini] judas1977:
Hmm.. i think i cannot help you, because i have LG G2 Mini twin brother - L90. But making own kernel from clean LG sources comes trough my mind;))
[iPAQ rw6828, XDA Atom General] lorneng:
Dear all,

i have recently bought a Atom Exec and i badly needs a chinese SIP. Can someone pls share a cracked version of CSstar or Monster chinese?

thks thks in advance!!!

cheers.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] c5ruzr:
Mods please delete
[Xperia Z1 Compact Q&A, Help & Troubleshooting] pooh9911:
Downloading some apps like pixel dungeon doesn't have this problem.

I took a look at log report and it has broadcast of intent and somethings about GCM.

Can anyone help me.
[G2 Q&A, Help & Troubleshooting] BFX91:
Hello dear Xda Forum Members,

two days ago i noticed a annoying Issue about my LG G2, im very worried and sad because the LG G2 is a fantastic Smartphone with a Monster Battery Power. Every time i tap on display it looks like i would tap on a TFT screen. I dont know how to explain it, the display do waves like i would press my finger on a led screen while its on, it look a bit like waves.

I asked in many forums now but no one noticed that kind of this problem yet. Its the second LG G2 where i noticed that problem.

Mostly i noticed it on darker background or some games and 100 percent screen brightness.

Sorry but my english isnt that good, i hope you guys can help me.

Thanks in advance
[G2 Q&A, Help & Troubleshooting] Art Vanderlay:
Yeah I'm not getting any ripples at all, on any background or brightness. There's something wrong with your phone if it ripples that easily. Maybe there's something in this thread that can help you
[G2 Q&A, Help & Troubleshooting] BFX91:
Ok thank you for your answer, the link helped me. I will RMA it tomorow.
[G2 Q&A, Help & Troubleshooting] Nahov91:
My screen ha flickering issue, but it happens only sometimes. If I swype on the screen, or touch it it goes away, or it gets better. It is a bit random. Do you have any idea what can couse this? It is really annoying
[Streak 5 Android Development] hunderteins:
Hello,

You may have read about an error in a piece of software named bash. [1]

This software is installed on my DSC, I think it came from GingerStreak.

You may find it also on CM-based ROMS.

Just try:

sh-4.1# test="() { echo Hello; }; echo hacked" bash -c ""
hacked
sh-4.1# X='() { function a a>\' bash -c echo; [ -e echo ] && echo "hacked"
hacked

If it shows "hacked" your tablet is in trouble. It is highly encouraged to replace the

bash software, because there are so many applications for this flaw, you'd never know

how it can be used to trick your tablet in doing things it shouldn't.

Attached is a zip of a static binary of bash-4.3 [2] with the latest patches from [3]

I compiled it, like it is described in [4] and [5]. I just changed the default

PATH to "/system/bin:/system/xbin:/sbin:/data/local/bin" to suit android

needs. Just put it into /system/bin/ for DSC/GingerStreak or /system/xbin/ for

CM-based ROMS.

So it should look like this

sh-4.3# test="() { echo Hello; }; echo hacked" bash -c ""
bash: warning: test: ignoring function definition attempt
bash: error importing function definition for `test'
sh-4.3# X='() { function a a>\' bash -c echo; [ -e echo ] && echo "hacked"
bash: X: line 1: syntax error near unexpected token `a'
bash: X: line 1: `'
bash: error importing function definition for `X'

Have fun,

hunderteins

[1] http://en.wikipedia.org/wiki/Shellshock_(software_bug)

[2] https://ftp.gnu.org/gnu/bash/bash-4.3.tar.gz

[3] https://ftp.gnu.org/gnu/bash/bash-4.3-patches/

[4] http://blog.droidzone.in/2014/08/06/cross-compile-bash-for-android/

[5] https://shellshocker.net/
[Streak 5 Android Development] Strephon Alkhalikoi:
Just tested PseudoCream, and its bash script returned the error messages on the second command, but returned "hacked" on the first. So, partly vulnerable? Irrelevant as I'm just going to change bash anyway to your version.
[Streak 5 Android Development] hunderteins:
this is no fun at all

Hello,

just an hour after I compiled the static bash, an other patch appeared [1]

going after CVE-2014-6277.

I compiled bash and attached it, again.

[1] https://ftp.gnu.org/gnu/bash/bash-4.3-patches/bash43-027
[Streak 5 Android Development] Strephon Alkhalikoi:
Hasn't that been the norm for this bug? They keep finding exploit vectors because the bug dates back to 1993?
[Streak 5 Android Development] hunderteins:
no, I think the first one was CVE-2014-6271 yeah, really old bug. Maybe msh should be enough.

CVE-2014-7186 also applies to this build. :(

bash -c 'true <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF' ||
echo "CVE-2014-7186 vulnerable, redir_stack"

but at least that's not done via environment.

Unfortually I've found a possible attack vector on Android. To get an IP-

adress f.e. via WLAN we use dhcpcd and shell-skripts in /etc/dhdpcd/dhcpcd-hooks.

A special crafted public accesspoint may be able to use this to run code as dhcp user on the Streak.

I have no concrete exploit, but that looks bad.

hunderteins
[Streak 5 Android Development] hunderteins:
Here we go again

Hello,

under [1] is a shell-script to test against known bash bugs. I attached an android-version of this script (changed path to bash and /tmp) and my latest build of bash 4.3 patchlevel 30.

I tried to compile this with gcc-4.8 for 'address sanitizer', but the kernel on the streak is too old for that. So I got back to 4.7.

now I get:

Testing /system/bin/bash ...
GNU bash, version 4.3.30(1)-release (arm-unknown-linux-gnueabihf)

Variable function parser pre/suffixed [%%, upstream], bugs not exploitable
Not vulnerable to CVE-2014-6271 (original shellshock)
Not vulnerable to CVE-2014-7169 (taviso bug)
Not vulnerable to CVE-2014-7186 (redir_stack bug)
Test for CVE-2014-7187 not reliable without address sanitizer
Not vulnerable to CVE-2014-6277 (lcamtuf bug #1)
Not vulnerable to CVE-2014-6278 (lcamtuf bug #2)

have fun,

hunderteins

[1] https://raw.githubusercontent.com/hannob/bashcheck/master/bashcheck