yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] fermasia:
I've allways appreciated how solid and tidy Omnirom team codes... even when that means developement moving on a bit of a slower pace. Does anyone know who's the official device mantainer/s (if any) for our device? I was just curious, since I'm seeing that there weren't any new commits since the 8th when lolzballs made his last build, if anyone knew when was Omnirom planning to begin with official nightlies for Android L.

I'm trying to make a custom kernel for Omni L, but since I've allways built with CM bases I'm having a bit of trouble adapting things (hopefully I'll be able to solve what I need to solve to make it usable). It's nothing spectacular, I allways try to build my own kernels for my personal use, but if I achieve something decent I'll surely share if anyone's interested.
[ONE Android Development] daryelv:
Here's the KitKat Official OmniRom thread for the OPO.

http://xdaforums.com/oneplus-one/orig-development/unofficial-experimental-omnirom-t2884422

I'm waiting for Omni to get the code updated with the new modem firmware. Usually I build my own ROM and pull in a few cherry picks. I'm looking forward to see what the Omni team does with the Lollipop code. I'm already pretty impressed with Lollipop the way it is and the Omni team's tweaks alway seem to be well thought out and written. The Cyanogenmod team seems to be doing quite well with their nightlies too, I do like the implementation of root access they have implemented on a per-app basis, but I've always preferred Omni overall in the past.

-Daryel
[ONE Android Development] lolzballs:
The official maintainer for most of the oppo/oneplus devices is maxwen. He also does a ton of work on the overall rom. Never really dealt with kernel and hal stuff, so yeah. The only contributions I've made to omni are the occasional forward ports of features from 4.4.

Anyways, I've been pretty busy lately, with examinations coming up, but I'll try my best to keep this rom up to date with everything on gerrit. Feel free to pm me/tag me if I miss something big in the gerrit.
[ONE Android Development] fermasia:
Thanks for the info and for building. There's nothing merged for the opo in gerrit. after your last build. Not sure how non-device-specific stuff is handled (I'm not familiar with gerrit, to be honest). But if I can help in any way, let me know.
[ONE Android Development] lolzballs:
Hmm.. Just flashed CM12 nightly just for fun, and it seems quite a lot slower than omni...

Has anyone else tried both?
[ONE Android Development] JacK_Sparr0W:
Omni is more stable than CM12…*I tried both and I revert back to Omni after 3 days on CM12…*:good:
[ONE Android Development] K Rich:
I haven't flashed this ROM, but I remember Omni KK was a lot "smoother" than the stock ROM. May have to give this one a try...
[ONE Android Development] anishz:
Hi,

Can anybody guide me on how to build omni for our bacon from source. I have a mac, i saw the omni guide for building and have got it upto setting up repo. All required things have been installed, also created sparseimage as per instructions, now i am stuck. The next step is something about bash profile. Don't know what to do. Please help.

Will also look into installing ubuntu in VM and trying but it will be very slow to build right? Please help.

I didn't want to pester lolzballs for a new build so thought of building. Failed anyways.:silly:
[ONE Android Development] CtlAltDefeat:
Bug on the version from yesterday (available on androidfilehost, you probably haven't had a chance to update this thread yet): Unable to access Phone Status within About Phone.
[ONE Android Development] JacK_Sparr0W:
Same here.. And I can't use the phone function.. I got bootloop, phone restart, and I can't receive network.. I think, the build isn't finish or I don't have chance ^^
[ONE Android Development] fermasia:
Well, maybe lolzballs kept it unpublished for a reason :p
[ONE Android Development] lolzballs:
Yeah, that's basically why.

I'm investigating this issue, but I don't have much time to. Since I haven't built in a while before this one, I can't exactly tell what date it started occurring, so I'm searching through commits on gerrit.

If you guys could provide some logs, that would be great.
[ONE Android Development] anishz:
I will do that later tonight when i get home, can't do it now as i am on CM12.

Edit:Logcat.

Baseband shows as unknown, tried flashing the latest baseband from OPO/CM but didn't work.

1st time taking logcat, please let me know if somethings wrong i will take again. Saving this as nandroid.
[ONE Android Development] CtlAltDefeat:
Just to be clear, in addition to the mentioned bugs (dialer, phone status...probably related), there's the longstanding (from 4.4) bug whereby connecting to a charger automatically tries to turn the phone on. Yesterday I got caught in a nasty "bootloop" whereby the phone shutdown to due to battery running out, I connected to charger, the phone immediately tried to turn on automatically, shut down due to no battery, and so on, etc.
[ONE Android Development] anishz:
I know you are busy lolzballs, but just wanted to know if any progress was made. Or anyone else have any insight on the issues? After jumping around on other LP roms i went back to omnirom kk. Will wait for omnirom LP build to get better. Main problem with other LP roms was the audio on poweramp.
[ONE Android Development] OmegaBlaze:
If you're talking about the audio glitching, someone made a fix for it.
[ONE Android Development] anishz:
Yes i saw the fix thing, it does reduce the glitching but doesn't remove it completely, atleast for me. Also CM does so many changes everyday, that's good, but it ends up breaking something every other day.

To be frank my flashing itch will take over and i will end up on some LP rom again. :silly:
[ONE Android Development] lolzballs:
Sorry for the delay, but I have been busy with school(exams). It seems that maxwen has fixed the baseband issue and I'll be compiling again tonight.

Cheers!
[ONE Android Development] lolzballs:
The new build has been uploaded. If there's any bugs, feel free to tell me, as I haven't had the chance to test this build yet.
[ONE Android Development] fermasia:
Many thanks for it :good:

Do yout think "layers" support could be added in future builds? It seems to be a much less intrusive way of theming than CM theme manager, and truly open sourced, but I also know Omni has allways avoided theming enginges that could cause unstability.

EDIT: there's a small derp in the link in the op, in the URL tag (but you can manually copy and paste the link, thought.
[ONE Android Development] anishz:
Thanks for the build. Downloading now. Will report later.

Sent from Bacon
[ONE Android Development] g_Four:
Thanks dev! Downloading now. :D
[ONE Android Development] fermasia:
Is it booting for you guys? I'm stuck at the bootlogo, and wanted to know how it went for you.
[ONE Android Development] lombyzgz:
Me too not booting.
[ONE Android Development] lolzballs:
Hmm, is the kernel failing to boot? Some logs could be helpful.
[ONE Android Development] fermasia:
Strange behavior... while trying to pull a logcat , on the first run, I got stuck in the bootlogo and then the device rebooted itself. Right after that, I let it try to boot once more and on this second run I got to the omni splash-logo and finally booted. Weird.

Edit: I was on SlimLP prior to flashing this build (of course, was a clean flash), and just in case I flashed the old modem (was on the aplha LP version). I think we should be using the old modem, am I right?

Edit2: Tried rebooting from the UI and everything went fine. Phone, apns, and everything else seems to be working well.
[ONE Android Development] Hzu:
It's currently in the works. They're working directly with the developer of the RRO himself to make it work.
[ONE Android Development] NikoZBK:
Has anyone with MultiROM got this to boot up fine? It gets to the OnePlus logo and reboots on secondary and primary slot.

Edit: I'm on the latest CM12 firmware.
[ONE Android Development] fermasia:
Those are good news indeed :good:
[ONE Android Development] Hzu:
I thought we're supposed to be on the latest firmwares? I'm not sure but I'm set to flash the latest CM12 nightly first before flashing the ROM and also coming from SlimLP (where before SlimLP, I was on CM12).
[ONE Android Development] anishz:
After I flashed it bootlooped once for me and then started fine. Restored apps from tibu and everything works fine now.

It was late here in India so didn't write back yesterday.

I am on latest firmware as I was on CM12 before this.

Sent from Bacon
[ONE Android Development] Hzu:
The same happened with me. I wonder if there's actually something happening behind the scene before the first bootloop. It sure doesn't look like a bootloop to me.
[ONE Android Development] g_Four:
Me too.. :)
[ONE Android Development] anishz:
Playing music doesn't skip or stutter during deep sleep, atleast until now it hasn't [30-40 mins], but it does when waking up the device [both DT2W or by pressing the power button]. But its improved than before. Its almost daily driver for me now.

I flashed the older modem from previous omnirom as i had sleep of death after a phone call, now it doesn't happen anymore.

:good:, Thanks for the build lolzballs, this has been the most bug free lollipop rom.
[ONE Android Development] fermasia:
Could anyone grab a logcat from this behavior? My adb is failing during bootup (I've reinstalled my distro and I'm struggling to make the sdk work as it should).
[ONE Android Development] nadiros:
Getting that double boot that others speak of every time I reboot.... ROM runs great though besides some reboots when I load certain apps. These are apps that run fine on any other Lollipop ROM I've tried. I know Omni is a little different and figured this is why. Will grab a log next time. Thanks a lot for the builds. I would like to remain on Omni.
[ONE Android Development] venturizhou:
Is tap and pay working for people? My cards are not showing up in Google Wallet and I do not see the tap and pay option in my settings. Yes my NFC is on. Thanks.
[ONE Android Development] nadiros:
I don't see the option either...not that I use it, as I'm in Canada.

Edit* update - running the 1/31 build and its stable and has the extras that I like. I do flash the on screen button enabler/capacitive button disabler zip though. Does Omni not do the onscreen button thing?
[ONE Android Development] rothod:
Is this ROM correct?

When you try downloading the files says xxxfind7Opxxx. Is not Find7Op a different phone from ONePlus+? :confused:
[Galaxy S 5 Q&A, Help & Troubleshooting] akamorning:
My model is

Galaxy S5 New Zealand SM-G900i( kltedv).

Can I flash the klte's official CM11 rom?

If not, which type of CM11 rom should I flash? Since I keep looking for a CM11 rom for my device, I couldn't find it.

Please help me out.

Thanks !!!!!!!!!
[Galaxy S 5 Q&A, Help & Troubleshooting] qubbus:
Yes, you can, but NFC might not work at all :( I have tried CM12 KLTE and NFC did not work, on KLTEDV unofficial build NFC worked.
[Galaxy S 5 Q&A, Help & Troubleshooting] binhad:
I got same version in Australia SM-G900i( kltedv).

I have

BlissPop-v3.9-kltedv-OFFICIAL-20150831-0417 it is the best rom I have tried so far

there is version BlissPop-v4 now had a couple issues so went back to 3.9 has been a few more updates might sorted it now

http://xdaforums.com/galaxy-s5/unified-development/rom-wip-27-9-14-t2889474
[Huawei Ascend Mate 2] cameron3200:
Hello everyone,

I've read in a few different places that HiSuite has an Emotion UI tool that allows users to create and edit .hwt themes. However, I can't seem to find this functionality in HiSuite anywhere. Has anyone been able to do this? If so, which version of HiSuite were you using and where can I find these options?

Thanks!
[Huawei Ascend Mate 2] MikeyLee:
I can't even find the HiSuite app or software
[Huawei Ascend Mate 2] kimtyson:
There's this really cool thing called Google.

http://consumer.huawei.com/minisite/HiSuite_en/
[Nexus 6 Q&A, Help & Troubleshooting] Tauk:
The ATT vs of the N6 doesn't have "Network operators" as an selection. Under Setting...More...Cellular Networks, I have Data roaming, Preferred network type, and Access Point Names. On my N5, Network operators could be selected to scan for other carriers' networks. Is there a change to build.prop that would enable this selection? Or is this not possible?
[Nexus 6 Q&A, Help & Troubleshooting] chemguru:
N6 Moto version doesn't have that either, and I don't recall seeing that option prior to inserting the ATT SIM. So, I'm not sure that particular option is available.

--JamesT
[Nvidia Tegra Note 7] NCSUZoSo:
I am sitting dead in the water with an EVGA Tegra Note 7 that can't turn on Wireless and won't let me install drivers to move further or even do a restore.

First off I am using Tomsgt Super Tool: http://xdaforums.com/showthread.php?t=2627654

So my device was continuing to fail an OTA update so I was going to use this device to reinstall the basic 4.4.2. However during the process Fastboot.exe gave a failed message in Windows, but it showed fastboot after the device name. I continued to let it Restore Tegra Note 7 to Android 4.4.2 and first of all it did it way too fast and once it was finished I couldn't get the Wireless to enable. I read another person with the same problem that had to redo the process. Well I can't get past reinstalling ADB and Fastboot, now not even ADB..

I tried uninstalling the device from Windows letting it reinstall and then checking it again. No matter what I do the USB Driver Scan fails over and over. I got this issue the first time, but somehow I got it to catch the device once and install ADB.

1) Yes USB Debugging in Enabled

2) Yes Anti-Virus is Off

3) Bootloader unlocked

4) Tried Different USB Ports

So what the hell is going on here?? All I wanted to do was run a damn OTA update.. Now I have a tablet with no wireless and I obviously can't do an OTA update now.

[IMG="error"]http://www1.picturepush.com/photo/a/14460864/800/Anonymous/ADB-Error.jpg[/IMG]

I was thinking about not using the tool and doing it all manually like I used to do, but all the tool does is auto execute files/folders in specific orders, basically an elaborate .bat file. So if it is failing at ADB, it is going to fail for me manually too.

Please give me some idea of what to do. I don't see how relocking the bootloader would do anything, but aside from that it was a non-rooted stock 4.4.2 OS running.

Is there something I need to do in order to get Impactor to work?

So then I plug the device into a 9 year old laptop with Windows XP and Impactor sees the device on the first try and installs the driver (it takes 2-3 minutes). Then it finishes and I close impactor, but I get an error next saying device not found. I restart the machine and now it is exactly like my desktop, Impactor can't see the device at all.

What in the hell is going on here? If I had known all this was going to happen I would have skipped their damn OTA update that continued to fail.

BTW with XP I can prevent Windows from installing any type of driver, so I did. Should I let XP search for a driver and see what happens?

Someone throw me some ideas, you can see a full explanation of what is happening if you scroll up to my screenshot. I basically have a dead device because I wanted to use this tool to do a recovery...

Wireless refuses to turn on, it just sits there for hours if I let it.

Someone please give me guidance, I was out of the Android scene for a while and I've forgotten a lot of the tricks I used to know.
[Nvidia Tegra Note 7] share_needles:
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.

Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.

If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"

Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img

You have to make sure the filename is correct with the custom recovery you downloaded.

At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.

It sounds complicated but it isn't.
[Nvidia Tegra Note 7] NCSUZoSo:
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again. I believe there is a quick message that flashes the first time I try to select Fastboot, however it's way too fast to read. When I do it again after that is when I will see a black flash, but apparently from what I have heard that is all Fastboot kernel is supposed to do??

How do I verify Fastboot is working before I flash the damn thing?
[Nvidia Tegra Note 7] share_needles:
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode. :eek:

You can verify this by running your super tool and it will say "fastboot device"

Do you know how to use the ADB command prompt?

Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.

I used this old backup of 4.3:

Forum post and links: xdaforums.com/showthread.php?t=2580287

Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip

FYI,

I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
[Nvidia Tegra Note 7] NCSUZoSo:
Can I get some official links for the newest/compatible versions of TWRP and the latest stock ROM I can install that is the most up to date (with Google Apps)?

Sorry to ask, but I am short on time most of the time and I might have an hour or so to work on it tomorrow.
[Nvidia Tegra Note 7] share_needles:
Sorry I don't have official links but it would take you 10mins to find them through google. Good luck.
[Nvidia Tegra Note 7] NCSUZoSo:
I have two files which I believe are correct except the TWRP file has an odd extension..

"Shaky156-TWRP-recovery.img.exe"

the other that is supposed to have GApps is: Stock-4.4.2-2.5-TegraNote7.zip

If that zip is only like 440 MB is that even possible? Can someone point me in a better direction if this sounds wrong.

Sources, TWRP: http://xdaforums.com/showthread.php?t=2586432

Actually thinking about it and I bet with having things specific to img files like IMGBurn and other software it may create a .exe so it's easier to emulate it as a disk.

Do we have any good custom ROMs these days you'd suggest over stock? Are any that stable yet? If not can anyone find me a complete download if a 440MB zip is too small to have GApps in it.
[Nvidia Tegra Note 7] NCSUZoSo:
I used Fastboot commands to get TWRP installed and Android is "upgrading.." now, so hopefully this will fix it.

I have the tablet up and running going into Google Play now.

I used this thread's link for the latest TWRP (2.7.1.0): http://xdaforums.com/showthread.php?t=2586432

I got a completely stock version of 4.4.2 and OTA shows this as the most up to date version. I got my copy of the 4.4.2 ROM out of the Super Tool's folder that you can find here: http://xdaforums.com/showthread.php?t=2627654

The tricky part to this my first time was I forgot you can open a command window inside the folder that contains TWRP/Fastboot/etc. (hold Shift and Right Click in the folder where all the data is and hit open command window)

Obviously everything came off a SD Card installed into the TN7.
[Nvidia Tegra Note 7] aimeymarie:
answer for dummies

Hi

Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?

I am not a tech pro and am unsure what to do

All of the above answers are like a different language to me .

Thansks
[Nvidia Tegra Note 7] NCSUZoSo:
Your best bet is to find someone you know who the above is not a foreign language to. I mean it could be broken down step by step as basic as possible and you may still not understand parts.
[JAMin, XDA Neo, S200 General] 0blivious:
Maybe i should shorten my first message:

Bluetooth drops the connection constantly, when i search to pair a device on the s200, when the search is over, the bluetooth shuts down (blue led stops flashing) and i can't add the devices it found, wich is logic, how can you make a connection when bluetooth is disabled? How do i keep bluetooth enabled no matter what? While still being able to shut it down manually.

Comm Manager doesn't work properly (bluetooth shows on when it's off and vice versa)

My SD card reader suddenly doesn't want to work, tried multiple cards, and simultaniously checking them on my computer card reader.

Sometimes slow respondtime.

I've tried everything multiple times, with multiple hard resets.

There's no software installed, everything been tested on a 'clean machine'.

Would upgrading the ROM (wich rom?) solve my problems? And how would i go about that? I've read the wiki but i'm none the wiser (half of the links don't work, i've read the post that everything's been taken down)
[JAMin, XDA Neo, S200 General] 0blivious:
Why thank you for all the help. Thought i would at least get a "sorry but it seems your ... is defect you will have to replace it" or "here [link] you will find similar stories with a possible solution"
[JAMin, XDA Neo, S200 General] 0blivious:
anyways, to update my post, i rma'd my s200 and it's been two months and two weeks since.. is that normal?
[Nexus 6  General] elpeterson:
Reddit Thread - http://www.reddit.com/r/nexus6/comments/2orklt/spreadsheet_to_track_bugs_and_manufactured_date/

Spread Sheet - https://docs.google.com/spreadsheets/d/1-a4wwAeaE01D_tS09PnO9GMYH5Ol90fZDnabwEB85GQ/edit

Cross-posting this from Reddit to get more data. Here is the post text:

I put this spreadsheet together after /u/rchallender helped me figure out how to get the (assumed) manufacture date of a Motorola device.

Boot to Bootloader

Scroll using Vol Down to Barcodes

Select with Vol Up

Date (bottom barcode) lists the (assumed) manufacture date

So far the columns are:

Username

Color (Midnight Blue, Butt White)

Size (32GB, 64GB)

Purchased From (Play Store, Motorola, T-Mobile, Sprint, AT&T, other)

Purchased Date

Manufacture Date

Burn In (Yes, No)

Defective Display (Yes, No)

Lag Issues (Yes, No)

Encrypted (Yes, No)

Defective Vibration Motor (Yes, No)

Other hardware issues (provide steps to reproduce if applicable)

I'd love any input regarding if more or less information is needed. I neglected to put battery performance because everyones usage is different and it would be really tough to determine if its personal usage vs battery issue.
[Nexus 6  General] GPS3:
Looks like I got an early one. 10/28/2014 build.
[Android Q&A, Help & Troubleshooting] QA Bot:
Q&A for [Rom][[Allwinner-A13]]UNOFFICIAL Cyanogenmod 10.1

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [Rom][[Allwinner-A13]]UNOFFICIAL Cyanogenmod 10.1. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)