yashsingh1/xdaforums huggingface dataset:
[LG Optimus G Pro] spexwood:
This came from LG itself. Yeah, it was the customer service, but it was LG too. When the customer service tells you this kind of thing, it's usually true since it says it on their troubleshooting computer prompt.

Plus this isn't an update just in the sake of updating (like going from Jelly Bean to Kitkat), but an update to fix their pretty serious mistakes. They'd be extremely stupid to leave the firmware as it is now since it's currently broken. The KK update broke not only the AT&T OGP, but also every LG phone sold by a US mobile carrier. This includes the AT&T G2 and Verizon G2 as well.

EDIT: Actually, I was wrong. The G2 already received updates to fix issues. If they get updates to fix broken software, I'm sure we will too.

If they left the update as-is, they'd risk pissing off any current customers and driving away any future ones. In fact, they'd risk losing their entire US market. So I'm certain they'll release a "fix" update soon. I know LG has a bad update track record, but as far as I know, the firmwares they leave on their phones at least work. This is different. Nothing works correctly, and they would want to fix it.

EDIT: BTW, if you're using the E988, then yeah, any further updates may not happen. That firmware at least works.
[G3 Q&A, Help & Troubleshooting] jbak98:
Has anyone noticed that when you put the phone up to max volume when on a phone call the speaker vibrates and becomes very unclear. Not sure if this is normal or a problem with my specific phone.
[G3 Q&A, Help & Troubleshooting] jbak98:
No one else having this issue? Think I may take it back to CPW to get a replacement
[G3 Q&A, Help & Troubleshooting] suljo94:
yes I had this to trygoing in music to settings=> audio effects=> adjusted and then pull 2k down and the rest you can tinker with(speaker sound wwill drop a bit in volume)
[XDA Assist] darkmall:
Dear Devs. I purchased an Aoson M1013 tablet. Basically it is a 10.1 inch cheap quad-core tablet with A9 Cortex processor, 1GB of RAM. Although the specs are not bad, I have the feeling that the software side is responsible for the tablet's weakness. Under weakness I mean several things and symptoms. The tablet died on me twice in a way that it was only willing to boot into its factory recovery which didn't let me move on to any direction. First I sent it to a tablet shop where they refreshed the factory firmware. Then it was working for a time but the the same thing happened again. I managed to reflash the factory rom by myself, I didn't want to pay any more for maintenance, I'm not a wealthy person. Overall there is the experience that it partially freezes for shorter-longer periods of time. It is exactly like it's lagging or something. It freezes at times and then continues operating with hectic window movement while it's trying to make up for the touch input done while it was temporally freezing. It seems to be a processor issue but I believe it is the question of software and governors maybe. Upon activating wifi these freezes mulitply and the tablet gets really slow. Other times it is really smooth and quickly running, this is why I think it is a software issue. It feels as if it had a soul or something, like there was a ghost in the machine or something. Therefore I would like to ask devs to compile a well-working custom rom for this device. So far I haven't found any of these online, although I was able to root the tablet and install CWM on it. Thank you in advance.
[XDA Assist] Sib64:
Hi,

Yes, that's correct that we have no forums or threads about your device.

But if you want, you can build your own CWM recovery with these guides ;)

XDA University: Porting ClockworkMod Recovery to New Devices

Android Development and Hacking	> Android Software Development	>	[GUIDE] Compile CWM Recovery

About root, you can use Framaroot =>	[ROOT] Framaroot, a one-click apk to root some devices

Good luck ;)
[XDA Assist] darkmall:
Root and CWM done

Hello

Thank you for the quick reaction, CWM and ROOT are already done. Now what I really crave for is a simple custom rom with no special requests, just a smooth responsive ability to operate the hardware of the tablet. It really seems like the factory ROM is not doing what it is supposed to. As for custom ROMs, I don't know if ROMs for other devices can be installed to this tablet or not. I would like to know if there are any compatible possibilities.
[XDA Assist] Sib64:
For the last part of your request, I really don't know. It seems that you're the only one with this device here.

But if you follow this guide, you can build your own rom for your specific device ;)

XDA University: Building Your Own Android Rom

Good luck
[Xperia Z1 Compact Q&A, Help & Troubleshooting] surfingnoob:
Do I need the Ftf file for my country? Or is the only difference that you get different icons?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jeffbar1:
does anyone know why this happens?

has anyone found a workaround?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] NeoPlex:
i think this rom work well... i using about one week
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Trashman:
most modern roms take 10-15 mins to pass from 98% to 100%...so wait...and wait...and wait...
[8125, K-JAM, P4300, MDA Vario Software Upgrading] vbguru613:
Ditto

You gots to wait!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jeffbar1:
i should still wait 15 minutes after the computer says 100%
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jeffbar1:
it has been 15 minutes and still at 99% how much longer

the update utility says congratulation! wtf
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jeffbar1:
20 minutes and i am almost ready to flashback?

whats the problem? what roms haved you tried updating from i,ve tried

2.26 2.3 and 3.2 rc1?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Trashman:
both in the computer and the wizard it stay at the same number, if the computer finished be4 then there is a problem...
[8125, K-JAM, P4300, MDA Vario Software Upgrading] DynaMight:
Whats your IPL/SPL version number?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Kartboy:
had the same problem,

and wasn't patient :$

now i get stuck in the boatloader :s

another upgrade isn't a go since i itz not connected

to active sync?

is there a way out :s
[8125, K-JAM, P4300, MDA Vario Software Upgrading] GldRush98:
haha, you don't have to be connected to activesync.

Just boot it in boot loader mode and plug it in. You can flash like that.

That's actually how I do all my flashes.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Kartboy:
I am just on bootloader ...

itz stuck there :s
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jeffbar1:
any reponse

i would like to try flashing again any ideas because it didn't work the first five times.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] prestonmcafee:
Me too

I have a G3 T-Mobile wizard (no .001), and it stuck at 99% with the PC version saying finished. I waited 25 minutes, gave up (there is a battery issue!) and reflashed with Molski's 2.26.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Kartboy:
how can u flash it again?

I am in bootloader and stuck there no updates work nothing :s
[8125, K-JAM, P4300, MDA Vario Software Upgrading] molski:
If you have .0001 then you have a G4 Wizard and NOT a G3 Wizard.

Molski
[8125, K-JAM, P4300, MDA Vario Software Upgrading] prestonmcafee:
no no

Yes, but I have "no .001", which should have been "no .0001".

Is your rom the same as T-Mobile 2.26 if I don't install the extended rom? (I install my own extended rom manually.)

Kartboy: As goldrush98 said, you don't have to be connected to activesync. If you see "usb" on the tri-color bootloader screen, just start the rom flash program and it will flash the new ROM. Worked for me.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jeffbar1:
please stick to topic

the topic is ell AKU 3.2 rom 99% crash not ell AKU 3.2 rom ipl/spl

i do not think the crash has to do with ipl b/c i know i have a G3

where is the developers response
[8125, K-JAM, P4300, MDA Vario Software Upgrading] hamsexy:
Same issue here.

I have the same problem here. Mine gets to 99% on the phone and the computer says it's done. I've waited over an hour for the phone to finish.
[Galaxy Note 3 Q&A, Help & Troubleshooting] UPSS !!:
Hello everyone i recently installed an custom rom on my note 3 SM-n900,the rom is called vm 14 is like a porting to Galaxy S5 setting with the new touchwiz,but the problem is that i got bored using this rom and when i tried to get back to stock rom from samsung it changes my imei to null/null.

So i tried to revert to custom rom once again and it works.Imei is stable not errors at all.

Any help how to revert to stock rom and to fix my imei ?

Thanks in advance.
[Galaxy Note 3 Q&A, Help & Troubleshooting] dr.ketan:
It's known issue after VN ROM V14/14.1

Read this, perticularly post #2

In short - If you have flashed VN14/14.1 ever

1.Everytime you flash any other ROM you have to flash NE1 modem otherwise you won't have IMEI

OR

2.If you have any EFS backup made prior to flashing VN 14/14.1, just restore it and you are again free to flash any other ROM without loosing IMEI
[Sony Smartwatch] znorf:
Hi there,

I'm looking for a way to configure my smartwatch in a way that every notification is shown within the watchface.

I want to be notified by vibration, but without displaying the notification on the screen as explicit fullscreen notification.

Does anybody know if such a configuration is possibly, maybe with third party notification apps or something else?

Thanks

Znorf
[Sony Smartwatch] dersie:
In watch setting there are 3 way to display notification. The last is for just icon notification, no text.
[Sony Smartwatch] znorf:
yeah i already found that setting, but it's not what i was intrested in.

The screen is still being activated.

I'am looking for a setting where the "passive mode" of the smartwatch will not be interrupted.

Only the vibration should notify me, the screen should still show the smartface without background light.
[Samsung Galaxy Nexus] Ziyan:
I've updated most of our kernel to 4AJ.2.2. Our kernel was really outdated, but with these changes, it should be easier to make the newer binaries work, as there are many, many kernel side dependencies for them.

Currently, I reverted everything that broke functionality with the current binaries (that includes remoteproc stuff which broke the camera, some sound and usb commits, not that much...), so everything still works.

As far as I see, we can compile the binaries ourselves: Building SGX driver (or just borrow them from another device?). As I have a little side project that I want to do now, I don't intend to get into ROMs too much, but I may as well join the party soon :)

The best starting point to make the kernel side changes is... well, my simple, but effective method is to compare the kernel dirs, like this. With this method, one can easily find & cherry-pick the changes from github, or I can create a separate branch that includes them (should I do it?), as it's not hard, I actually got them merged at a time with it's dependencies, but I reverted everything to get back the display.

Here's the kernel: https://github.com/Ziyann/omap

and the source: https://github.com/icepeda/omap/tree/icepeda-panda-4aj22

Also, it would be nice to know which binaries should we use, as there may be different versions for 3.0 and 3.4. Which binaries work with this panda kernel? [MENTION=5747201]isrcepeda[/MENTION], we don't want to disturb you as you work on the 3.4 kernel, but it'd be great if you could give us some hints :highfive:
[Samsung Galaxy Nexus] pianistaPL:
Sorry for the noob question, but you are talking about this driver? http://omapzoom.org/?p=device/ti/pr...it;h=8137028adad92178573b3448f833e1f0338c20db

Keep going, i can't helo you but i'm with you with my heart ?
[Samsung Galaxy Nexus] Ziyan:
Yes, that driver :)

[MENTION=4022928]Carlos_Manuel[/MENTION]

Check out my exp branch, I think I merged most of the things we need, it compiles fine, but I couldn't test it further - I may have easily missed something. I may setup a rom building environment tomorrow, as things are getting complicated...
[Samsung Galaxy Nexus] mrgnex:
I am going to say something absolutely stupid but as far as I remember there is a Galaxy S version (was it the advance?) that got a 3.4 kernel from an awesome dev. And the Galaxy Nexus uses the same gpu right? Isnt there a way to use some of that code?
[Samsung Galaxy Nexus] Carlos_Manuel:
I'm too sleepy to check them out. Build an kernel, use hardware/ti-omap4xxx/ from omapzoom (d-jb-mr2), update kernel-headers if needed to (some ion changes needed this change), etc.

With the ROM side I hope I can help, when help is needed, as I'm stronger in that than with kernels...

Nexus S uses pvr 540 too, but it has cortex A8 and possibly is an omap4430 device and it doesn't have same files in kernel as tuna.. because Nexus s is another device.. so it won't help at all
[Samsung Galaxy Nexus] Ziyan:
Hmm, do we need hardware/ti-omap4xxx? The sgx stuff seems to be in device/ti/proprietary-open.git. And as I see, we need to integrate it to the build system, as android-4.3_r3.1 doesn't have such a folder :mad:

Edit: lol, we may not even need to build a rom, just follow these instructions
[Samsung Galaxy Nexus] Ziyan:
Well, I managed to compile them. As excepted, things didn't just magically begin working. Android didn't automatically load the modules from /system/lib/modules, but:

insmod pvrsrvkm_sgx540_120.ko

seemed to work... (note: I had to enable CONFIG_MODULES in the kernel)

dmesg:

http://pastebin.com/RTM4fQAW

<6>[ 66.322906] PVR: PVRCore_Init
<6>[ 66.323242] PVR: LinuxMMInit: Maximum page pool size: 10800
<6>[ 66.323516] PVR: PVRSRVDriverProbe(pDevice=c78b2800)
<6>[ 66.323760] PVR: SGX register base: 0x56000000
<6>[ 66.323822] PVR: SGX register size: 65535
<6>[ 66.323944] PVR: SGX IRQ: 53
<6>[ 66.324218] PVR: EnableSystemClocks: Enabling System Clocks
<6>[ 66.324768] PVR: PVRCore_Init: major device 246

This appeared after doing insmod.

logcat:

http://pastebin.com/HyK887z7

Something's definietly bad there. The problem starts there:

E/IMGSRV ( 4513): :0: OpenServices: Cannot open device driver /dev/pvrsrvkm.

root@maguro:/dev # ls -l /dev/pvr*
crw------- root root 246, 0 2014-07-02 11:31 pvrsrvkm

Hmm, maybe a permission problem? Let's chmod it to 777 (maybe we'll need this included in the ramdisk).

dmesg again:

http://pastebin.com/1vqZunrf

logcat again:

http://pastebin.com/AWJz51X9

That did the trick, it went ahead, and another error popped out.

Well, I'm open to any suggestions while I try to fix this...

EDIT:

root@maguro:/ # free -m
total used free shared buffers
Mem: 809120 66744 742376 0 4896
-/+ buffers: 61848 747272
Swap: 0 0 0

That's a bit too much, isn't it? That android-display stuff which should allocate memory doesn't seem to work, I had the same problem when I merged it with the current drivers. I think I edited the board files the right way... but I'll look around.

EDIT 2:

<6>[ 0.000000] android_display: setting default resolution 720*1280, bpp=4

This may be the problem - we're not 4 bits, that should be 24.

EDIT 3:

Sadly, no.

u32 bpp;	/* must be 2 or 4 */

But the error must be somewhere in the memory allocation process. Another evidence.

<3>[ 0.213623] omap_rproc_get_pool: dsp - no carveout memory is available at all
<3>[ 0.214782] omap_rproc_get_pool: ipu - no carveout memory is available at all
[Samsung Galaxy Nexus] Carlos_Manuel:
I'm too lazy to read..:laugh: I've seen that page many times... it's for building the needed module for kernel...?

---------- Post added at 01:07 PM ---------- Previous post was at 12:56 PM ----------

IF possible, then may this be caused by SELinux?
[Samsung Galaxy Nexus] Ziyan:
The module loading may be easily caused by it, as SELinux doesn't allow loadable modules. But as I loaded it manually, this shouldn't be a problem.
[Samsung Galaxy Nexus] Carlos_Manuel:
File_contexts file may be the causer build a ROM with the module. Also enable module support for kernel (just in case)..

:)
[Samsung Galaxy Nexus] Carlos_Manuel:
What you can try:

(optional) can be done manually: http://git.omapzoom.org/?p=device/t...;hpb=906910612220d73ae7f92598f899dc1fb370f756

Enable permissions for ION driver. http://git.omapzoom.org/?p=device/t...it;h=e17db8f823da9d27144a60cd6e1cb09e17ef79bb

[Tablet] Set the permissions to rpmsg, tiler & dss http://git.omapzoom.org/?p=device/t...it;h=0c26dc60a9ee661a504cc6994c3f0d8ac6ec226d

Blaze Tablet: SGX: Add class core to the SGX init http://git.omapzoom.org/?p=device/t...it;h=abf171fa6eef6c2f7fee55f851699a40534f7f1a

possibly help from the IRC to the egl hal problem: http://pandaboard.org/pbirclogs/index.php?date=2011-12-21#T06:11:51
[Samsung Galaxy Nexus] Ziyan:
I'll try to build an aosp 4.3 based on the blaze device tree, seems like they integrated ti/proprietary-open, which is good, hopefully we'll have more luck... in the meantime, go experiment with it :D I'm a noob when it comes to ROMs, and I think the issues now are ROM-sided, as there are no dmesg errors (except one, but that's because userspace drivers failed to initialize).
[Samsung Galaxy Nexus] Carlos_Manuel:
If you use vendor/ti/ device/ti/* then modfiy the files for tuna and edit paths to the tuna's files. That's the way to keep all correct and not to mess up wrong files.. :)

I can't help at all, because I am trying to fix those damn errors caused by L preview from AOSP. I hate that SELinux!!!
[Samsung Galaxy Nexus] Ziyan:
Well, I'm getting closer and closer - I compiled AOSP 4.3 with ti/proprietary-open. Copied in my zImage and added one simple line to the boardconfig, and suddenly everything seems to get compiled & copied to the right place, new drivers, gralloc, egl...

Some more error messages gone. Dmesg, logcat.

I/SurfaceFlinger( 2501): SurfaceFlinger is starting
I/SurfaceFlinger( 2501): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL ( 2501): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 2501): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 2501): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
W/libEGL ( 2501): eglInitialize(0x1) failed (EGL_BAD_ALLOC)
W/gralloc ( 2501): page flipping not supported (yres_virtual=1280, requested=2560)
I/gralloc ( 2501): using (fd=14)
I/gralloc ( 2501): id = omapfb
I/gralloc ( 2501): xres = 720 px
I/gralloc ( 2501): yres = 1280 px
I/gralloc ( 2501): xres_virtual = 720 px
I/gralloc ( 2501): yres_virtual = 1280 px
I/gralloc ( 2501): bpp = 32
I/gralloc ( 2501): r = 16:8
I/gralloc ( 2501): g = 8:8
I/gralloc ( 2501): b = 0:8
I/gralloc ( 2501): width = 58 mm (315.310333 dpi)
I/gralloc ( 2501): height = 102 mm (318.745087 dpi)
I/gralloc ( 2501): refresh rate = 59.14 Hz
E/gralloc ( 2501): Error mapping the framebuffer (Invalid argument)
E/ti_hwc ( 2501): Composer HAL failed to load compatible Graphics HAL
E/SurfaceFlinger( 2501): composer device failed to initialize (Invalid argument)
E/SurfaceFlinger( 2501): ERROR: failed to open framebuffer (Invalid argument), aborting
F/libc ( 2501): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 2503 (SurfaceFlinger)

Something's still off...
[Samsung Galaxy Nexus] Carlos_Manuel:
Hwc, surfaceflinger errors:

You probably have to use omapzoom's hardware/ti/omap4xxx, modify kernel headers and modify frameworks/av for the hwc changes
[Samsung Galaxy Nexus] Ziyan:
Ok, omapzoom's hardware/ti/omap4xxx required hardware/ti/domx, which I added too, but it requires something more (I've also added external/bltsville and hardware/ti/omap4-aah, but they didn't help):

hardware/ti/omap4xxx/hwc/color_fmt.c:23:29: fatal error: linux/bltsville.h: No such file or directory
compilation terminated.
make-3.82: *** [out/target/product/maguro/obj/SHARED_LIBRARIES/hwcomposer.omap4_intermediates/color_fmt.o] Error 1
make-3.82: *** Waiting for unfinished jobs....
hardware/ti/omap4xxx/hwc/blitter.c:27:29: fatal error: linux/bltsville.h: No such file or directory
compilation terminated.
make-3.82: *** [out/target/product/maguro/obj/SHARED_LIBRARIES/hwcomposer.omap4_intermediates/blitter.o] Error 1
hardware/ti/omap4xxx/hwc/display.c:30:24: fatal error: ion_ti/ion.h: No such file or directory
compilation terminated.
make-3.82: *** [out/target/product/maguro/obj/SHARED_LIBRARIES/hwcomposer.omap4_intermediates/display.o] Error 1
In file included from hardware/ti/omap4xxx/hwc/dsscomp.c:26:0:
hardware/ti/omap4xxx/hwc/hwc_dev.h:26:29: fatal error: linux/bltsville.h: No such file or directory
compilation terminated.
make-3.82: *** [out/target/product/maguro/obj/SHARED_LIBRARIES/hwcomposer.omap4_intermediates/dsscomp.o] Error 1

Well that's it for today, I need to sleep, but if you find the relevant sources/commits, post them :)

I can't believe how outdated we are, I thought at least the rom side things are updated, but no... seems like google doesn't really care about kernel/rom side device specific things, they only improve android...
[Samsung Galaxy Nexus] Carlos_Manuel:
Include missing files which it can't find, to hardware/ti/omap4xxx/kernel-headers/original
[Samsung Galaxy Nexus] pattyboi:):
does the new drivers "NEED" the carveouts to be dynamically set up? if not,static them in,that way nothing needs to be allocated on its own i guess?(id help but im clueless on any of this,plus no device)
[Samsung Galaxy Nexus] Ziyan:
Yeah I thought about it, but I think it works fine now, so I'll give it a try with the new ROM side hwc, which is indeed required to make them work. If that fails, I'll fall back to static allocation, as dynamically it only reserves 8 MB VRAM, but according to my calculations, is should reserve about 10.5 MB with triple buffering... now, it reserves only the amount needed for double buffering (almost exactly, which makes sense for dynamic reservation), but who knows, maybe it fell back do double buffering, or even better, we didn't ever had triple buffering :confused:
[HTC Pico (Explorer)] SaifAli22:
I am using stock rom in htc explorer and i want to increase internal memory in stock rom pls give me the working solution for it help me fast
[HTC Pico (Explorer)] shubhojit89:
First you need to have a ext partition.. which can be done via recovery.. Then after partitioning.. Download link2sd from play store..

Or download pimp my rom.. Google it.. In that you will find universal init.d.. select it..
[HTC Pico (Explorer)] reshampanth:
Read this article- http://www.epiblog.in/2013/02/free-up-internal-memory-android.html.

I would still recommend using cm11 weekly 5 by [MENTION=5158920]kirmaniarslan[/MENTION] since its stable and far better than stock!