yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Q&A, Help & Troubleshooting] CalcProgrammer1:
Did you ever figure this out? I'm having the same issue on several devices - Galaxy Note i717 (CM10), Galaxy Note 3 (CM11 and stock), HP TouchPad (CM11). I have a Debian chroot on all of them and am trying to stop Android and run xorg. I don't have devtmpfs, just bind-mounting /sys, /proc, and /dev into chroot from Android but I did make a symlink /dev/fb0 -> /dev/graphics/fb0. I ssh into the Debian session and then kill Android using "stop" from terminal emulator or adb. This blanks the screen on the Note 3 and TouchPad but on the Note 1 it just freezes the display. On all three, writing to /dev/fb0 (via cat or via starting lightdm session) results in no activity on the screen, X halting or erroring, or sometimes "/dev/graphics/fb0: no such device" messages. I also tried using fb1, which should be MHL HDMI but my MHL adapter doesn't appear to work on my Note 3 (flashed it back to stock from CM11 and still nothing) though some HDMI related stuff does appear in dmesg. I'm stumped at this point. There's a bunch of interesting stuff in sysfs that may be of interest:

/sys/class/lcd/panel - contains a bunch of stuff related to the LCD (AMOLED) panel device, including lcd_power which may be necessary to re-turn-on the screen after Android shuts it off

/sys/class/graphics/fb0 - contains a bunch of framebuffer related entries, including an option to blank the display (cat 1 > blank does blank the screen even if Android is running) and mode setting

/sys/class/graphics/fb1 - contains the same stuff from fb0 plus a bunch of HDMI/MHL related information, including HDMI connected state

It definitely seems something else is either locking the framebuffer or there is some security thing preventing access to it. Not sure what would be the cause of this weirdness but I don't like it.
[Galaxy S 5 Q&A, Help & Troubleshooting] Aou:
Unfortunately, I never did figure this out. Because of this roadblock, I have pretty much given up on the idea (not to mention I had a baby and I've started in the Alpha for an upcoming MMO). I did poke around a little with /sys/class/graphics/fb0 before I quit, but didn't get far.

I'm wondering if "what changed" was SELinux, or something like that? Perhaps it is a security "feature" written into modern bootloaders that prevents direct access to the framebuffer?
[Galaxy S 5 Q&A, Help & Troubleshooting] Tautvaldas:
Ofcourse, ****ing qualcomm freaks made it atlast, good for them!!! From OpenSource to closed source == from free to jail!
[Galaxy S 5 Q&A, Help & Troubleshooting] SharkWipf:
Recently got a Oneplus One, and am facing the same problem trying to port desktop distributions to this device.

I've tried disabling SELinux entirely, but this gives the same result, which leads me to believe it's something in the kernel.

I'm currently configuring a customized Cyanogenmod 11 kernel, but am not sure what to look for.

I suspect that switching to an older Android version (and thus older kernel) would make it "just work" on this device, but the OnePlus One, as far as I'm aware, doesn't have any pre-KitKat 4.4.2 Android roms.

Did any of you get anywhere with this issue, or am I on my own on this one?

Update: I decided to see if this would work in TWRP recovery. Interestingly, I could cat /dev/graphics/fb0 and get the right output, but writing to it did nothing. I tried blanking and writing random data in several ways, including cat and dd, but the screen would stay unchanged.

That, however, is a different issue than the one we experienced so far. Now to get it working within Android.
[Galaxy S 5 Q&A, Help & Troubleshooting] kenkitt:
Hi does anyone know how to get this to work.

I have an Alcatel OT918D ANDROID 2.3.5.

I have managed to compile my own kernel and boot it. But for adding the frame buffer option in the makefile I get this error during compilation:

:(

**************************************************************************************************************

drivers/video/console/fbcon.c:638: note: expected 'struct file *' but argument is of type 'struct fb_info *'

drivers/video/console/fbcon.c:638: error: too few arguments to function 'info->fbops->fb_open'

drivers/video/console/fbcon.c: In function 'con2fb_release_oldinfo':

drivers/video/console/fbcon.c:670: warning: passing argument 1 of 'oldinfo->fbops->fb_release' from incompatible pointer type

drivers/video/console/fbcon.c:670: note: expected 'struct file *' but argument is of type 'struct fb_info *'

drivers/video/console/fbcon.c:670: error: too few arguments to function 'oldinfo->fbops->fb_release'

drivers/video/console/fbcon.c:673: warning: passing argument 1 of 'newinfo->fbops->fb_release' from incompatible pointer type

drivers/video/console/fbcon.c:673: note: expected 'struct file *' but argument is of type 'struct fb_info *'

drivers/video/console/fbcon.c:673: error: too few arguments to function 'newinfo->fbops->fb_release'

drivers/video/console/fbcon.c: In function 'fbcon_startup':

drivers/video/console/fbcon.c:868: warning: passing argument 1 of 'info->fbops->fb_open' from incompatible pointer type

drivers/video/console/fbcon.c:868: note: expected 'struct file *' but argument is of type 'struct fb_info *'

drivers/video/console/fbcon.c:868: error: too few arguments to function 'info->fbops->fb_open'

drivers/video/console/fbcon.c: In function 'fbcon_exit':

drivers/video/console/fbcon.c:3388: warning: passing argument 1 of 'info->fbops->fb_release' from incompatible pointer type

drivers/video/console/fbcon.c:3388: note: expected 'struct file *' but argument is of type 'struct fb_info *'

drivers/video/console/fbcon.c:3388: error: too few arguments to function 'info->fbops->fb_release'

make[3]: *** [drivers/video/console/fbcon.o] Error 1

make[2]: *** [drivers/video/console] Error 2

make[1]: *** [drivers/video] Error 2

make: *** [drivers] Error 2

make: *** Waiting for unfinished jobs....

CC [M] ../mediatek/source/kernel/drivers/lttng/probes/net-extended-trace.o

CC [M] ../mediatek/source/kernel/drivers/lttng/probes/block-trace.o

CC ../mediatek/source/kernel/kernel/trace_mt65xx_mon.o

LD [M] ../mediatek/source/kernel/drivers/lttng/ltt-relay.o

CC ../mediatek/source/kernel/drivers/m4u/m4u_kernel.o

../mediatek/source/kernel/drivers/m4u/m4u_kernel.c: In function 'm4u_user_v2p':

../mediatek/source/kernel/drivers/m4u/m4u_kernel.c:66: warning: format '%d' expects type 'int', but argument 3 has type 'struct task_struct *'

************************************************************************************************************
[Galaxy S 5 Q&A, Help & Troubleshooting] AlaskaLinuxUser:
How about populating with mdev?

Hey, I am not a S5 owner, but I recently ported Debian to my Samsung Captivate Glide with Xorg and XFCE:

http://xdaforums.com/captivate-glide/general/samsung-captivate-glide-debian-chatter-t3233807

The trick that I used was during the init scripts I call upon busybox's mdev to populate the nodes like fb0 and fb1:

#!/sbin/busybox sh

/sbin/busybox echo "mounting proc,sys,dev" > /log/boot.log

/sbin/busybox mount -t proc none /proc
/sbin/busybox echo "mounted proc" >> /log/boot.log
/sbin/busybox sleep 1

/sbin/busybox mount -t sysfs none /sys
/sbin/busybox echo "mounted sys" >> /log/boot.log
/sbin/busybox sleep 1

/sbin/busybox mount -t tmpfs none /dev
/sbin/busybox echo "mounted dev" >> /log/boot.log
/sbin/busybox sleep 1

/sbin/busybox echo "Populating mdev" >> /log/boot.log
/sbin/busybox mdev -s
/sbin/busybox ls /dev > /log/dev.log
/sbin/busybox echo "mdev populated" >> /log/boot.log
/sbin/busybox sleep 1

#export PATH=/sbin:/usr/sbin:/bin:/usr/bin

#/etc/init.d/rc.local start

#/sbin/busybox echo "All done" >> /log/boot.log

# Launch delayed init script
/etc/init.stage2 >/android/log/boot.log 2>&1 &

I have not messed with Ubuntu Touch yet myself, but I know that this works for Debian so that I can use /dev/graphics/fb0 in my xorg.conf file to start my x display.
[Galaxy S 5 Q&A, Help & Troubleshooting] SharkWipf:
That seems interesting, I'll dig up my OPO soon to see what I can do with that.

Did you base your project on an Android kernel, or did you manage to compile a "real" Linux kernel? What kernel version?

From what I can find the Glide (officially) only supports up to Android 4.0, did you start from an Android version and, if so, what version?

The problem I had on my OPO seemed to be specific to Android 4.4+, although your solution may still work.

I'm definitely going to play with this. Thanks for reporting your findings.
[Galaxy S 5 Q&A, Help & Troubleshooting] AlaskaLinuxUser:
Found this on http://source.android.com/devices/graphics/architecture.html

All about Android graphics. For my build on the Samsung Captivate Glide, I am using an Android kernel, but not a stock one. Cranium is the name of it. Anyways, it is an older ROM that I took it from, 2.3.7, I believe. So I bet you are right, if you take an older Android environment it would most likely work that way.

However, busybox's mdev -s option simply creates all the "standard" things you need, making nodes for all the standard things that are not there. So it *should* work, and busybox is plenty small enough to put on there. Also, you could do it the old fashion way with mknod, but I have not tried that myself, as mdev did it for me. In any event, good luck, and I hope that helps!
[Galaxy S 5 Q&A, Help & Troubleshooting] tpr0:
Guys, Im in the same situation and figured it out partially.

I can now see garbage data on screen with fast alteration between android screen and the urandom garbage after disabling hardware overlay :D:

b) debug.composition.type = gpu

c) dev.pm.gpu_samplingrate = 1

d) debug.sf.hw = 1

e) debug.egl.hw = 1

^ In build.prop, though i still recieve no such device, still works

The garbage data is updated while having graphical changes in Android, like scrolling menus updates the garbage data...

The main issue is, killing Android (surfaceflinger etc) results in black screen. Ofc all this worked after doing what OP has done in kernel config. Tried on both s5 and tab s, gotta check TWRP/CWM source code and device tree specific files for our devices to see how it works. (Hate that proprietary Mali gpu)
[Galaxy S 5 Q&A, Help & Troubleshooting] Peng13:
I met this issue too when I want to write something to /dev/graphics/fb0. Yeah, I got this info "/dev/graphics/fb0 no such device" as well.

And then I tried to use "adb reboot recovery" command to come to Recovey mode. (I'm an Android smart phone developer, so I have many test phones.)

I found I can read and write data from/to /dev/graphics/fb0 node in Recovery mode.

Share this information with you guys, hope it's helpful.
[Verizon HTC One (M8)] ransz:
Im using ruu1.55.605.2 rooted stock rom. I noticed that when i go to software update and press on check new it states "software update only works on CDMA". I bought this verizon phone on ebay and using it in israel on Global network option.

Why does it say i must be on CDMA to use software update?
[8525, TyTN, MDA Vario II, JasJam General] Malibu Stevie:
Hi guys! Just wondering if anyone knows how and where to install polyphonic ringtones for text messages on the TyTN. Spoke to a really helpful guy at TyTN HQ who tried to help but to no joy.

At the moment, text message alert is using midi sounds but I would like to use my own MP£ or polyphonic sounds as an alert instead as I don't like the ones provided...can anyone out there help me at all please?

Many thanks,

Stevie.
[8525, TyTN, MDA Vario II, JasJam General] rob22:
Hi,

without a special prgramm you can only use wav format as polyphonic format. copy the wav files into the windows folder. thats it.
[8525, TyTN, MDA Vario II, JasJam General] Malibu Stevie:
Good man Rob and thank you so much for the reply. Managed to find a sound conversion program and it seems to have done the job.

Which program were you talking about which would do the job for me just fine?

Many thanks once again,

Stevie.
[Galaxy S 4 Active General] AndroidUser12345678910:
Ok so ive cracked my S4 Active's glass (digitizer is fine) so I bought a new digitizer and glass for it because j didnt want to go through all the trouble of removing the glass from the glue and all that. But I cant find a decent tutorial anywhere on how to replace this. Can someone direct me towards one?

Sent using my Galaxy S4 Active (using XDA Developers app)
[HTC Sensation] v.konvict:
any app out there that will allow me to hold the shutter button ,,,,then it turns on the flash and focuses on the image so i can take better night pictures. my night pics are coming out blurred out.
[HTC Sensation] ShadowCodeGaming:
It's called flashlight and it's included in most roms.
[HTC Sensation] v.konvict:
thanks ....u are the second person to say that now i finally figured it out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bsballkingben99:
I am running the quantum 4.1 ROM and the KT747 kernel. I like to use media utilities with Zooper to make a widget for all my different music sources. Since using this setup, media utilities doesn't update when the screen is off anymore. When I was on stock it worked fine. Does anyone know anything about this or have any experience with it? I'm wondering if it has anything to do with how the ROM or kernel is setup. Any possible solutions are greatly appreciated.
[Galaxy S 5 Q&A, Help & Troubleshooting] TomaLLoS:
Hey. Today by the accident I did photo in totally dark room and I notice that middle of the screen is dark and outside till edge is getting more lighter I'll post photo of this what I did.

Please everyone to make test photo in totally dark room and let me know if only I've this issue or everyone have same problem otherwise I need to go to store change him (3 time) for new
[Galaxy S 5 Q&A, Help & Troubleshooting] Ave666:
It show all black on my screen
[Galaxy S 5 Q&A, Help & Troubleshooting] Michael_P:
Did you remember to remove lens protector sticker?
[Galaxy S 5 Q&A, Help & Troubleshooting] TomaLLoS:
You have to watch on it in the night or where is totally dark. And if you zoom in this photo/screen shot you can see that middle part is totally dark and edges are more light.

And yes I removed lens protection sticker
[Galaxy S 5 Q&A, Help & Troubleshooting] TomaLLoS:
is same foto (foto 2) but i did two arrows to show where is this and if you watch on mobile please zoom it an if in laptop please go to your screen 5 - 10 cm to see this
[Galaxy S 5 Q&A, Help & Troubleshooting] Ave666:
I think it is normal issue on non ois camera
[Galaxy S 5 Q&A, Help & Troubleshooting] TomaLLoS:
But did you check also at yours if you have same issue ?

just make a photo in totally dark room/place without any flash and other extra light
[Galaxy S 5 Q&A, Help & Troubleshooting] enop4:
http://xdaforums.com/showthread.php?t=2675768

Read it! I think it's normal.
[Galaxy S 5 Q&A, Help & Troubleshooting] ElenaPower:
I played a little bit with Photoshop with your black picture. I think it is totally normal that you cannot get a real 100% black picture out of a cam. A dark room is not 100% black for your cam. Maybe for your eyes. And even if you would make a photo of an ideal 100% black room in the end you would make a photo of your cameras chip noise. But the picture for me looks more like a litte rest of light the camera could fetch.
[Galaxy S 5 Q&A, Help & Troubleshooting] TomaLLoS:
Ok looks like you make my pic way easy to see for everyone but you can check if is same at yours s5 ?

I just need to know if every s5 have a same issue because my nexus5 in same room same time have no this issue !!
[Galaxy S 5 Q&A, Help & Troubleshooting] ElenaPower:
I tried to make a black picture. it looks similar to yours but it is nearly black (more than yours). I pressed my black soft S5 bag on the camera lens.

So I still think its not an issue but it shows that the S5 camera is much more sensitiv to distinguish between black and nearly black than other cameras that recognize 100% black where the S5 recognizes 98% black. No issue for me.
[Galaxy S 5 Q&A, Help & Troubleshooting] TomaLLoS:
I would like to say that samsung galaxy s4 have no this issue so I go to change my s5 for new.... again.... what for full of problems phone... really disappointed. ... photo is prove
[Galaxy S 5 Q&A, Help & Troubleshooting] ElenaPower:
From which camera was the last picture you posted? Its not 100% black like all the others.
[Galaxy S 5 Q&A, Help & Troubleshooting] TomaLLoS:
From galaxy s4
[Galaxy S 5 Q&A, Help & Troubleshooting] ElenaPower:
So the S4 has the same issue what is no issue for me :confused:

What you are looking for is a theoretical ideal camera that makes a 100% black picture of a 100% black original. You won't find such a camera anywhere.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] jlu459:
I bought the Samsung Galaxy Note 10.1 2014 Edition recently and it states that it has been modified. I do not want it rooted and just want the official device status that it is supposed to be. If I unroot it to the latest 4.4.2 version, will I be able to on the tablet, update the software to the latest edition? I just want to be able to update it normally from the device and keep up with the latest versions. Thank you in advanced for your input.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] jgaf:
As far as I know you won't be able to receive OTAs, but you will be able to do updates manually via Odin.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] ¿Will-it-Blend?:
Odin flash the 4.4.2 firmware for your region and reboot into recovery and factory reset from there. Reboot and you'll be back at official non-rooted status and can receive OTA's.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ericmerl:
Hey guys, I seem to have soft-bricked my AT&T S3.

I was running Paranoidkangdroid 2.32 (based on CM10.1, 4.2.2), but started having some stability issues. Thinking it was time to start fresh with a new ROM, I downloaded SlimKat 4.1 and tried to install it following these instructions.

Upon rebooting, my phone hit the SlimKat loading screen and never finished booting. I rebooted to recovery, and saw errors saying it was unable to mount /cache, /data, and /system. I still have access to recovery and download, and have tried flashing and reflashing a variety of different ROMs, both custom and stock, but haven't been able to get past those errors.

When flashing from recovery, I get errors saying the partitions aren't able to be mounted. I can flash ROMs from Odin, and they do seem to be installing (no errors in Odin, and the Current Binary setting does change depending on whether it is a stock or custom ROM).

Best I can tell, my partitions are screwed up. Any advice on what I did wrong and the best way to proceed? If the partitions are screwed up, is there a way I can rebuild the partitions through the shell?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Larry2999:
What stock ROM did you try to flash via Odin and did you get the <PASS> message? If you did, then it would seem the flash was successful. Can you try booting into recovery and doing a hard wipe/reset? Unless your phone has hardware issues, flashing a complete stock image should update all partitions.

Finally, if you were already on Android 4.3, you may try doing a stock restore using the instructions in the following thread ...

http://xdaforums.com/showthread.php?t=2658486
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ericmerl:
Stock ROMs

The ROM I had previously installed was based on 4.2.2, so I'm not sure the instructions in that thread will apply...

I have tried installing the UCDLK3 ROM, as well as a couple of custom ROMs. I'm about to try another stock ROM (UCALEM), and will report back with the results in a few minutes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ericmerl:
Sad times.

I just tried installing the UCALEM stock ROM with Odin. Everything seemed to go well, and it finished with no errors and a "PASS!" result.

When my phone rebooted, a screen briefly popped up with red text. It didn't stay up long, but the errors I saw were similar to what I had seen before (unable to mount, etc.). The background was the red exclamation with the android robot lying down. The phone quickly rebooted, and sat with a black screen. When I pulled the battery out and powered it back on, it tried to enter recovery mode on its own, but only flashed the Samsung Galaxy S3 screen and remained on a black screen.

I can still access download mode, and the Current Binary now reads "Samsung Official." My phone did this same thing earlier when I flashed another stock ROM, and I was able to get back to recovery mode by flashing a fresh instance of CWM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ericmerl:
To follow up again, I was able to re-flash TWRP using Odin. Once that was done, the phone no longer tried to boot straight to recovery. I was able to three finger into TWRP, though it took a super long time for it to boot.

Here's the console log taken from TWRP once it boots:

E:Could not mount /data and unable to find crypto folder.
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Unable to mount internal storage.
E:Unable to mount /data/media during GUI startup.
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
Running boot script...

Finished running boot script.
E:Unable to mount '/cache'
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E:Unable to mount '/data'
[Sprint HTC One (M8)] mswlogo:
I'm currently S-OFF, Stock Firmware (as shipped, except for hboot, recovery).

And I'm running BadBoys 1.1

I don't want to flash "Modified Firmware" (this time).

What do I need to do let the OTA update come in normally?

I assume I need to flash Stockish ROM (with or without root).

Do I need to relock?

I know there is unmodified firmware as well. I might go that route too.

But I want the most "Official" way to let the firmware be updated. I want to hold off on Harman Firmware just yet.

If a Stock RUU (that included OTA firmware) existed, I'd definitely just use that. I know about the Harman RUU.
[Sprint HTC One (M8)] Sloth:
I've never personally taken an OTA.

I think all you need is a stock rom and stock recovery.

Not sure if you need to re-lock being s-off.

Btw the unmodified firmware is pulled from the OTA zip.
[Sprint HTC One (M8)] mswlogo:
Yeah, I know. I ended up doing just that. Being crazy anal for nothing.
[Sprint HTC One (M8)] Jerz201:
I learned my lesson on my old EVO 4G about accepting OTA's.

I lost root for a while until a new method opened up.

Patience is everything.
[Sprint HTC One (M8)] Magnum_Enforcer:
Since you're S-off you can just install the stock Android recovery, then accept the OTA. You'll retain S-off but lose root. You can then root again by installing a custom recovery and flashing the SU binary in recovery. Honestly, though, Captain Throwback's firmware will get you where you want to be without the hassle of doing everything I listed above.

Sent from my HTC device
[Sprint HTC One (M8)] AarSyl:
Yes, and no...for Sense enhancements, you get to check them out first without waiting for a stock rooted rom or a custom rom running the same base. Matter of preference, I guess.
[Sprint HTC One (M8)] Magnum_Enforcer:
Right. I personally prefer to wait for a stock rooted ROM based off the latest update, and separately install the corresponding firmware package.

Sent from my HTC device
[Sprint HTC One (M8)] AarSyl:
Meh...to each his own. It depends on what the update contains for me. For example, I had no interest in waiting for a stock rooted Sense 5.0 rom when it was finally released for the LTE.
[One (M7) Q&A, Help & Troubleshooting] Atrax_:
Question is in the heading, is there any mod for CM11?