yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Alpha] modpunk:
I'm not available for one week. If someone wants to hack on the ROM, take a look at the TESTING branch ...

http://git.cryptomilk.org/projects/android/android_device_samsung_slte.git/log/?h=TESTING
[Samsung Galaxy Alpha] qkdxorjs1002:
%device_slte.mk%

# This file gets automatically copied to the recovery root by CM.
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/recovery/init.recovery.universal5430.rc:root/init.recovery.universal5430.rc

%device_slte.mk%

# This file gets automatically copied to the recovery root by CM.
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/recovery/init.recovery.universal5430.rc:[B][COLOR="Red"]recovery/[/COLOR][/B]root/init.recovery.universal5430.rc
[Samsung Galaxy Alpha] modpunk:
You read the comment, didn't you?
[Samsung Galaxy Alpha] qkdxorjs1002:
yes, i read it. but it copied to 'slte/root/init.recovery.platform.rc'(ramdisk has no init.platform.rc) and 'slte/recovery/root/init.recovery.platform.rc'

check yours

sorry for my grammer
[Samsung Galaxy Alpha] modpunk:
Yes, you copy it to the root of the ROM, there is a Makefile rule in CM which copies it from the ROM root directory to the recovery root directoy. That's what the comment says ...
[Samsung Galaxy Alpha] martellog:
Hey thank you very much for your efforts, so why not post a sticky with the donations "goal" sort of like a kickstarter thing?
[Samsung Galaxy Alpha] modpunk:
Ok, I have a few more fixes. NFC is starting now, haven't tested it yet. VoIP calls are not working that's what I try to fix now.

Help would be appreciated e.g. by debugging vold why a usb stick via USB OTG is not detected correctly ...
[Samsung Galaxy Alpha] sunsettrack4:
[MENTION=4297219]modpunk[/MENTION] Does mobile data work on your ROM? And how much work is needed to get a stable build?

Thanks for the attention you take on this device. :)
[Samsung Galaxy Alpha] neofral:
i noticed CONFIG_USB_OTG is not set on kernel config. could that be a reason?
[Samsung Galaxy Alpha] modpunk:
It works in the recovery which runs the same kernel ...
[Samsung Galaxy Alpha] modpunk:
Yes, it I have mobile data working. A lot of work but time is limited. I would say the most important features are working. But what is important for people differs. Maybe someone would say the device isn't working if video output and recording isn't working and that's broken again ...
[Samsung Galaxy Alpha] modpunk:
Yay, the macloader patch is upstream and bonuzzz found an issue with deferred initcalls.
[Samsung Galaxy Alpha] modpunk:
https://plus.google.com/100275307499530023476/posts/JWV46K4vVzp

Looks like it makes sense to switch to CM12 and fix video playback and recording there ...
[Samsung Galaxy Alpha] bonuzzz:
I've tried today to build cm12, but it hangs on boot. I ccant find problem yet
[Samsung Galaxy Alpha] modpunk:
Did you check /proc/last_kmsg or is adb already started so you have a log to share??
[Samsung Galaxy Alpha] neofral:
if we will switch to CM12 can we start with fresh sources? today i got a reply from opensource.samsung.com saying they will release the G850FXXU2BNK3 sources ASAP :D
[Samsung Galaxy Alpha] modpunk:
Why fresh sources? The only interesting source code is the Kernel source code. All I did was to create a correct config for it and fix the bugs so it compiles with a newer gcc version. I don't see any huge issues ...
[Samsung Galaxy Alpha] bonuzzz:
Starting kernel... That's all:))))

And i dont have any idea where is problem. I rechecked hardware folder and compiled kernel with gcc 4.7

---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------

When we've porting lollipop to p900 (exynos5420), we had issue with graphic
[Samsung Galaxy Alpha] airbus360:
Have you got device tree for cm12 available?
[Samsung Galaxy Alpha] modpunk:
Not yet, I would like to fix three bugs first:

vold - attach usb stick via usb otg cable. I can see the /sys entries vold should be looking for but it doesn't react. Mounting manually works. So I need to debug vold.

nfc - I have a patch is the TESTING branch which enables it but it isn't working yet, strace needed

voip - the mixer settings are not working, non working patch in TESTING

Feel free to pick a topic and help getting it working ...
[Samsung Galaxy Alpha] neofral:
MTP is working :D

SETTINGS>OPTION>USB Computer connestion> select MTP

edit: SETTINGS>STORAGE>OPTION>USB Computer connection> select MTP
[Samsung Galaxy Alpha] modpunk:
Then the Linux libmtp is broken. I didn't get it working. I will test in a Virtual Machine with Windoze ...
[Samsung Galaxy Alpha] neofral:
# Audio

Revisit sound recording, capture volume to low?

Check if CM DPS Manager is working.

Do we need voicefx in audio_effects.conf

CM DPS Manager working on audio playback with Apolo
[Samsung Galaxy Alpha] neofral:
i'm using ubuntu 14.04 LTS and is working after enabling it
[Samsung Galaxy Alpha] modpunk:
You were able to transfer files?
[Samsung Galaxy Alpha] neofral:
Yes of course
[Samsung Galaxy Alpha] modpunk:
An update to the ROM is available: G850FXXU2BOA2_G850FDBT2BOB1_DBT

The Device Tree Blog changed so there are Kernel changes too but Samsung did not release the Kernel for the update yet ...
[Samsung Galaxy Alpha] neofral:
I know, this version is up on sammobile for almost a month now. This is the reason why i suggested to update the sources but couldn't give the exact answer to your question "why update" so i remained quiet. Also this is the sources that i requested from opensource.samsung.com. Instead, on their e-mail of 17 Feb they said will release the sources for 2BNK3, but nothing yet.
[Samsung Galaxy Alpha] joserobleda:
Hi,

I just get my new Alpha and I want to help. I am a developer, but I usually work in web environments. If someone can point me in the right direction, maybe with a "hello world" example about how to compile and debug a ROM I'm sure I can start helping in a few days.

Thanks!
[Samsung Galaxy Alpha] neofral:
as i've been told in the beginning of this thread...

try starting with this: http://git.cryptomilk.org/projects/android/android_device_samsung_slte.git/tree/README?h=cm-11.0
[Samsung Galaxy Alpha] modpunk:
Fixed
[Samsung Galaxy Alpha] neofral:
-usb is still not working. just tested your latest work on the TESTING branch

-nfc can't test atm, i don't have another android phone with working nfc near me

-voip? are you referring to calling over apps such as Viber? if yes, just tested and your solution worked. good job maestro :good:

however, we still need to work on improving the audio quality. the outgoing sound is low while talking on viber but video is working fine :good:
[Samsung Galaxy Alpha] modpunk:
I never claimed that any of these things are working :)

Yes, we need to add much more debugging to vold to understand what is going wrong. First would be the fstab parser in vold and then the code which ckecks the path in /sys.

I'm talking about native SIP support in the phone app. It doesn't work ....

About the quality, I already said we need to check if voicefx in the audio_effects.conf fixes it. The the source code of the voicefx library in the device tree.

Pick one of the three things and work on it, the source code is available for all of these things ...
[Samsung Galaxy Alpha] neofral:
just to inform you all... new/updated sources for our devices are out. thanks to Samsung for answering my request, however the sources are not the latest.

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=850f
[Samsung Galaxy Alpha] bonuzzz:
del
[Samsung Galaxy Alpha] modpunk:
I don't have time to create and inspect the diff yet. Maybe next week or in two weeks. I'm busy with other stuff...
[Samsung Galaxy Alpha] neofral:
i just compared directories. there are changes. even though i lack the knowledge to fully understand the changes and see if they are relevant to solving any of our bugs, i think its worthwhile to try and make a build with the new kernel sources and see if any changes arise. of course this is until you have more time to look into the changes and say for sure if changes are substantial or just tweaking.

i would like to point 2 additions on the /source update/drivers/net/wireless/bcmdhd/wl_cfg80211.c file.

1. addition at line 5017
#ifdef CUSTOMER_HW4
#define LONG_LISTEN_TIME 2000
if (duration > LONG_LISTEN_TIME) {
wl_cfg80211_scan_abort(cfg);
} else {
#undef LONG_LISTEN_TIME
#endif /* CUSTOMER_HW4 */

2. addition at line 5039
#ifdef CUSTOMER_HW4
}
#undef LONG_LISTEN_TIME
#endif /* CUSTOMER_HW4 */
[Samsung Galaxy Alpha] modpunk:
As the dbt changed significantly there need to be more updates to drivers, including the modem driver.
[Samsung Galaxy Alpha] modpunk:
452 files changed, 6336 insertions(+), 5175 deletions(-)

That's quite an amount of changes ... I'm working on a new kernel after that is working I will move to cm-12.0

I think the biggest changes are in the modem and the GPU driver and ION got several fixes.
[Samsung Galaxy Alpha] neofral:
:good: yes and that gave me some build errors. it's looking for linux/videodev2_exynos_media.h i saw this file in several hardware subdirectories and couldn't solve the issue.

i also noticed some changes on the usb/gadget files and also the dwc3 driver, i think this will bring us closer to solving the USB OTG problem. i've been working on this issue for the past several days without any success and i'm very frustrated. i tried many driver configurations for mounting the usbdisk and none of them worked.

however, the app ES File Explorer is detecting the drive and i was able to copy/paste files to the usb stick. i also spent a lot of time trying to figure out how is ES File Explorer is identifying and what driver it's using to mount the usb drive. the usb is appearing as USB1002 with ES F.E., maybe you can use this info to solve this issue
[Samsung Galaxy Alpha] modpunk:
Well you need to install it ...

The USB OTG disk problem is not a kernel issue. You can mount it manually. It is a configuration issue of the fstab and frameworks resource files. It also works in the recovery, so why do you think this is kernel related?

You have to add some more log statement to vold when it parses the fstab and sets the listener to the /sys path ...
[Samsung Galaxy Alpha] neofral:
I thought this before and i still think so after i saw that in the kernel files there are changes on irq and some other things that i don't remember to list now on the dwc3 driver.

However, this is only me. I hope i'm wrong and the solution is much easier and simple and correct fstab addition will solve this issue, but i've tried at least a dousin of versions for the device address and i still couldn't mount usbdisk
[Samsung Galaxy Alpha] :
can anyone give me the rom as a flashable zip?
[Samsung Galaxy Alpha] lukrangelu:
hi modpunk have any plans cm 11 ?
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] swagking101:
ok so everytime i flash a rom my headphones stop working i plug the headphones in and the sound comes out of phone speaker i am trying to flash a kitkat rom please help couldnt find answer on phone

lg optimus l7

p705

v10k-DEC-12-2012
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] Nesh89:
you just may have the wrong baseband. Check what baseband your phone is running on, if its on v10 baseband and you have a 4.4 kitkat rom flash v20 baseband.

http://xdaforums.com/showthread.php?p=42858119

You can find the baseband here.
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] Nesh89:
You need to flash v20a
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] swagking101:
thanks got it working
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] Nesh89:
np
[7" Kindle Fire HD Q&A, Help & Troubleshooting] garnet17:
I have a Kindle Fire HD 7" (one of the two that our family owns) that is stuck in a loop where the logo screen keeps appearing at bootup. It starts as a static Kindle Fire image and then changes to an animated Kindle Fire image and then the process starts over again (and again etc...). For reference - the Kindle is completely stock and has a front facing camera, HDMI port and black stripe across the back. The second Kindle (same model, just a few months older) is working and has version 7.4.9 software on it so it is probable that the looping Kindle had the same stock version too. Our Kindles are completely stock and rooting has never been attempted. I have spent a lot of time trying to research what might have happened and how to fix the looping Kindle. Here is a description of what I have tried:

When booting up and in the looping condition the device does not show up in the Windows device manager at all. I have been able to build a fastboot cable and it does put the Kindle into fastboot mode (the logo changes to the word fastboot). At this point the device is recognized as a USB device. I have installed the Kindle drivers and the device now shows up as "Kindle Fire" -> "Android ADB Interface". I downloaded the SRT v1.3.5 and in a cmd shell run as administrator tried the options to restore the boot, recovery and system to the bundled v7.3.0 as well as clearing the cache and userdata, but the loop still occurred.

The command line "fastboot -i 0x1949 getvar product" returned a string containing "Tate-PVT-08", however the "fastboot -i 0x1949 devices" command did not return anything. I found that the size of the fastboot.exe bundled in the version of SRT had a smaller size than the one in the KFFA project I found online. I tried the exe from the KFFA project and was then able to get a response with a device ID, tried the all the reflashing steps again, but still had the looping. I also downloaded the system images (v7.2.3) used with the KFFA and flashed them, but same result. I have installed the ADB tools and the fastboot.exe it supplies has an even larger size so I tried it for the whole flash process, as well as now running all the fastboot commands manually from the command line (as administrator) instead of from bat files, but still have the loop.

Is there a way to get out of this boot loop and get the Kindle usable again?

Any help would really be appreciated.
[Moto 360] L_E_O:
I've updated to the new Connect app, and the app on the phone works fine, but none of the new features will sync to the watch. I've tried restarting the watch, resetting the watch, uninstalling and reinstalling both Android Wear and the update to the Connect app (on a Moto X, so I can't fully uninstall Connect).

Anybody seeing this? Maybe I need to do all that in a particular order?
[Moto 360] krankyjoe:
I am having the exact same issue. Using a Moto X 2014. The app updated and works on thr phone but none of the new features will sync
[Moto 360] compuguy1088:
In the same boat as well...
[Moto 360] j0hnnyn:
Same with me. Running lg g3. I've read the issue is the phone that your 360 is connected with. Some people paired their 360 with a different phone and then the new watch faces finally appeared. But once they would try to pair their 360 back to their current phone, the watch faces would still not show.
[Moto 360] ern88:
No problem here on my Nexus 5
[Moto 360] peaster3:
you won't see anything different on the phone after the motorola connect update in terms of the Body app. However, if you go into the start menu on the watch itself, you should see moto body features such as calories, steps, heart activity, and heart rate. hope this is helpful.
[Moto 360] 2crazeybolt:
Won't work on my S4 either, tried everything. Bummer!!!
[Moto 360] jeturbo820:
Works fine with my s4. Try restarting phone?
[Moto 360] jlehenbauer:
ditto

Same issue on my moto x 2013. Can't do anything to get them to show up. Done everything short of a hard reset on the phone
[Moto 360] respider:
same here, nexus 5 on lollipop
[Moto 360] mc-paulo:
I had the same problem. I use it with my Nexus 5 running an AOSP Lollipop Build.

Solved it by uninstalling the Motorola Connect App and reinstalling. After that everything new appeared on the 360.

Hope this helps :good:
[Moto 360] edbogue:
Many thanks this worked for me. I was dreading having to do a factory reset.

Edbogue
[P3300, MDA Compact III General] MrButcher:
Hi folks,

how much time to you need until your GPS link is stable and ready to use?

If i am using Tomtom 6 and starting it the first time it minimum 4 minutes until the routing can be startet.

While routing shutting down tomtom und restarting it the link is stable within 10 seconds, the same behaviour als after a tunnel.

But it is very annoying to wait that long time.

Is there a difference to other Navigation Programs?

Which times do you have?

Is QuickGPs helping you?
[P3300, MDA Compact III General] amokoma:
German (deutsch ;) ):

Hi MrButcher,

beim ersten Start überhaupt von TomTom dauerte es bei mir 2 Minuten (QuickGPS hatte schon Daten). Wenn ich jetzt normal navigieren will und ich TomTom also aufmache dauert es ca 20-60s bis ein brauchbares Signal da ist. Ich habe es noch nie ohne QuickGPS probiert, da es ja immer automatisch mit synct.

English:

Hi MrButcher,

if you start you TT the first time ever, it can take up to a few minutes, mine took about 2 minutes (i already had QuickGPS data).

In normal day use, i start TT and it takes about 20-60s to get a signal.

I never tried it without QuickGPS so i cant say anything about that.
[P3300, MDA Compact III General] debully:
Tip - if you install GPSgate (Franson) it keeps the GPS running so you get a fix almost instantly.
[P3300, MDA Compact III General] jdl1306:
What you should be getting from the other posts is that usage will determine lock times. Don't use it for too long, and the sat positions are obviously way out of where your unit last knew them to be. Use it frequently and the sat positions haven't varied that much that your device know where they are (or in the ball park)...

How it works is obviously more technical, but that's what you're experiencing, in plain english!
[P3300, MDA Compact III General] hays:
mine takes about 15-20 secs with TT6

I use the Quick GPS but ONLY when synced at home, so no extra data charges

Hope that helps
[Android Q&A, Help & Troubleshooting] ali60351:
Hi Devs

I need some apks from your system/app folder one is LiveWallpapers.apk and other is LiveWallapapersPicker.apk. Preferably from an android 4.3 rom. I could have downloaded an entire ROM but I am really suffering from a limited data connection. I need them because my device doesn't has them by default.

Huawei Ascend Y530

Android 4.3 Stock ROM

Rooted

THANK YOU !!!
[G3 General] trifos:
here in this forum has

[TEST_KDZ] LG G3 (F400K) /Android L-F400K19H_00.kzd

http://www.lgbbs.net/thread-839-1-1.html
[G3 General] Kniazkoff:
Offtopic

http://xdaforums.com/lg-g3/general/kdz-lollipop-5-0-android-l-t2931192
[Android Q&A, Help & Troubleshooting] Jack8Profile:
Hi guys.

I'm new, and im today reg on this forum for help and to solve the problem.

I have mobile: phone pad g530 (mediacom)

And i turn on device, image on startup freeze....

Okey, i go to options press down volume gumb and shutdown gumb for boot, and select factory reset.

Restart phone and my device freeze on startup -.-

Again, the same does not help me factory reset

(My english is bad sorry) xd Im from bosnian hah.

Please help me guys ?

I have question ?

How to fix this ? Download and install new android ?

Does my cell phone supports Android 4.4.4 ?

If supported, what i need to take off to install it successfully on 4.4.4 version on my device and correct this errors.

Please help me and thanks.,
[Xperia Z2 Q&A, Help & Troubleshooting] Absarock1:
hi

i own a Z2 (d6503)

-bootloader unlocked (everything else is custom) i had rooted it previously but i think i lost the root access while updating the firmware to 4.4.4 using EMma

my problems

1. Google services are not working over wifi, but there is no problem with mobile data.

i have tried clear cache method already, factory reset, date/time thing. Sometimes few retries make playstore work.

2. Phone isn't turning on in recovery mode. neither manually (with buttons) nor with quickboot or PC

everywhere i found the same method: turn off, power on and wait for led to light up then press either of the volume buttons repeatedly. But the led doesnt light up

3. I have lost my DRM keys while unlocking the bootloader. (no TA backup). my bad.

what did i looose other than xreality engine? can it be recovered? how?

4. How can i root the new version of firmware android 4.4.4 (23.0.1.A0.167)

Please help

i am familiar with rooting and know a little more than an average user. But at the end of the day i am a noob too.
[Xperia Z2 Q&A, Help & Troubleshooting] ghostofcain:
1. no idea, sounds weird that it works over data but not WiFi.

2. If your running stock rom then you don't have recovery installed hence you can't access it.

3. AFAIK The play station remote won't work, there is no way to recover DRM keys they are device specific so your out of luck.

4. Downgrade to .314 and flash a pre-rooted zip, there is currently no known exploit for 4.4.4 so no direct root method.
[Xperia Z2 Q&A, Help & Troubleshooting] Absarock1:
Although you have discouraged me completely, thanks anyway.

Can you explain the pre root zip thing? Shouldnt I just wait for the new rooting method to come up?
[Xperia Z2 Q&A, Help & Troubleshooting] nreuge:
Once rooted, you can recover most features flashing this : DRM FUNTION RESTORATION FOR UB
[Xperia Z2 Q&A, Help & Troubleshooting] ghostofcain:
AFAIK devs aren't putting a huge amount of effort into finding a new root exploit, why bother when achieving root through downgrade and flashing pre-rooted is fairly trivial.

The pre-rooted zips are just that stock .167 roms that have been pre-rooted, they can be flashed over earlier fw without data loss.
[Xperia Z2 Q&A, Help & Troubleshooting] Absarock1:
So where can i get one?

[/CODE][/CODE]

oh damn! In my first post i made a mistake i meant to say (everything is stock) but wrote custom instead.

terribly sorry

Where can i get one of these roms u just mentioned?

Even if i get it, how do i flash it? I dont have a custom recovery installed and if there is a stock recovery i cant enter it.

can u elaborate the procedure i mentioned below?

[ how to flash this kernel ] (via fastboot)

download the kernel image

save the boot.img to the folder containing fastboot binary

flash the boot.img using fastboot:

Code:

fastboot flash boot boot.img

reboot from fastboot

Code:

fastboot reboot

the device should now start booting

enjoy!
[Xperia Z2 Q&A, Help & Troubleshooting] Absarock1:
THAnks

thanks man. 3/4 of my problems are solved now. 1 is going to be solved soon hopefully.
[Xperia Z Q&A, Help & Troubleshooting] wookiee82:
Hi everybody,

My brother's Zip got water damaged so I took it apart and tried to maybe repair it.

From what I have gathered, I can say that the motherboard is still functioning because I can feel the vibration when is booting up, the led is working and also the sound. The only thing not working is the screen part which I tested with an other screen and nothing happens...

My question for you is this:

Can you come up with any idea of what I can do with the phone?

Maybe use it as a media server to attach it to a TV? Portable hot spot?

Tell me what ever come to your mind!

Thank you!
[LG G Watch] andTab:
Is there any way to get the steps from android wear into MS' healthvault?