yashsingh1/xdaforums huggingface dataset:
[Omni Q&A] ssuds:
Getting closer, I hope...

Now am able to get the mb886 in the lunch menu... With a catch.

If I do a breakfast command, it shows the lunch menu with only the "full-eng" option. After that, if I do the lunch command it only shows "full-eng".

However, if I setup my build environment again ( . build/envsetup.sh) and then lunch, omni_mb886-userdebug shows up... But the build breaks with that error.

shreyas@shreyas-VirtualBox:~/android/omni$ . build/envsetup.sh
including device/motorola/mb886/vendorsetup.sh
shreyas@shreyas-VirtualBox:~/android/omni$ breakfast

You're building on Linux

Lunch menu... pick a combo:
1. full-eng

Which would you like? [aosp_arm-eng] ^C
shreyas@shreyas-VirtualBox:~/android/omni$ lunch

You're building on Linux

Lunch menu... pick a combo:
1. full-eng

Which would you like? [aosp_arm-eng] ^C
shreyas@shreyas-VirtualBox:~/android/omni$ . build/envsetup.sh
including device/motorola/mb886/vendorsetup.sh
shreyas@shreyas-VirtualBox:~/android/omni$ lunch

You're building on Linux

Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_mips-eng
4. aosp_mips64-eng
5. aosp_x86-eng
6. aosp_x86_64-eng
7. omni_mb886-userdebug

Which would you like? [aosp_arm-eng] 7
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/motorola/mb886/omni_mb886.mk]]: "frameworks/native/build/phone-xhdpi-1024-dalvik-heap.mk" does not exist. Stop.
WARNING: Trying to fetch a device that's already there
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/motorola/mb886/omni_mb886.mk]]: "frameworks/native/build/phone-xhdpi-1024-dalvik-heap.mk" does not exist. Stop.

** Don't have a product spec for: 'omni_mb886'
** Do you have the right repo manifest?

shreyas@shreyas-VirtualBox:~/android/omni$

Same thing happens if I try to brunch

shreyas@shreyas-VirtualBox:~/android/omni$ brunch mb886
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/motorola/mb886/omni_mb886.mk]]: "frameworks/native/build/phone-xhdpi-1024-dalvik-heap.mk" does not exist. Stop.
WARNING: Trying to fetch a device that's already there
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/motorola/mb886/omni_mb886.mk]]: "frameworks/native/build/phone-xhdpi-1024-dalvik-heap.mk" does not exist. Stop.

** Don't have a product spec for: 'omni_mb886'
** Do you have the right repo manifest?
[Omni Q&A] ssuds:
So it looks like I'm actually missing a bunch of build directories, which totally explains why this isn't working out...

My CM directory:

My Omni directory:

Clearly this is linked to my issues with repo... So I guess the real question is, what is wrong with my repo setup that is causing these issues?

Edit: My omni directory is a mere 676 MB... I should have realized this much sooner.

Edit2: I think I'm on the right track. Starting from scratch using the repo reference flag linked to my already downloaded source. 60% of the source is downloaded so far, we will see where it goes.
[Omni Q&A] ssuds:
Update:

It builds! Finally got all my references and source synced properly. Omni is building for the MB886 currently.
[Omni Q&A] Silentwidow:
Any luck on this? I get the exact same error, except I'm building AOSP.
[Omni Q&A] Entropy512:
I somehow missed this thread.

Some of the issues I saw there look like they may have been CAF-related. With 5.0, we never completed the process of merging the CAF branches of frameworks/av and frameworks/native so they coexisted. (To make a long story short, that was primarily my task and I was catastrophically burned out and pretty much gone for 3-4 months... Then 5.1 dropped.)

As of today, working on a CAF device requires syncing the android-5.1-caf branches of frameworks/native and frameworks/av - Also, we use a different naming method for determining which QCOM CAF variant of display/audio/media HALs to use. You might want to try finding a device with a similar CPU to get ideas of how that was brought up. I remember when bringing up falcon in 4.4, I also had to add some oddball Moto-specific patches that aren't in our 5.x branches because I never had the time to resurrect that device. (I have more time now, but I've got a LOT of catching up to do...)

Right now:

CAF "b-family" (8226, 8974, etc) devices are current focus, especially 8974s, I'm going to be working this weekend on getting the CAF branches of av/native to coexist in our tree without syncing funky branches

CAF "a-family" devices (8960, 8064, etc.) are "here be dragons" - The Sony guys have them semi-working I believe, but the a-fam stuff needs a LOT of work. Getting a bootable device is feasible, but getting a usable device (especially media/AV stuff) requires us to fix a bunch of stuff
[Omni Q&A] ssuds:
Awesome, thank you for the direction [MENTION=591147]Entropy512[/MENTION]! I've been kinda busy with other stuff recently, but when I get the chance I'll definitely try again to spin this up using that set up!
[Omni Q&A] Ano11:
Hi there,

How did you get rid of these errors?

I use these commands but get the above errors all the time:

repo init -u https://github.com/omnirom/android.git -b android-4.4

repo sync -j4 -f --no-clone-bundle

I am just a beginner so help will be appreciated... ;)

Thanks!
[Omni Q&A] mikeysteele:
ssuds, Did you ever solve this problem?
[Omni Q&A] Ano11:
No... I gave up.
[Omni Q&A] jasonhosu:
jhelp

same with me:silly:
[Omni Q&A] poppy22:
[ 99% 1587/1588] glob vendor/slim/build/soong/Android.bp
ninja: error: '/home/ubuntu/slim/out/target/common/obj/JAVA_LIBRARIES/telephony-ext_intermediates/classes.jar', needed by '/home/ubuntu/slim/out/target/common/obj/PACKAGING/boot-jars-package-check_intermediates/stamp', missing and no known rule to make it
11:30:29 ninja failed with: exit status 1
[General Topics] Menneisyys:
acbTaskMan (see review HERE) is no doubt the BEST CPU usage charter utility for Windows Mobile. Now, with the new, 1.4 version, it has received network monitoring features. Make sure you upgrade to the new version – it’s really worth it!
[General Topics] xplode:
Well i will not question its funkcionality, but more can be done to the UI.

Overall this is a great app, light memory print, fast work, it does what it suppose to do.
[General Topics] privard:
Bug

Doesn't work with the localization set to Japanese. Changed it to English and it worked, but that means I can't use it with programs that require the localization to be set to Japanese.
[General Questions and Answers] droidsaill:
Hi,

In MTK device [MT6572] I want to change apk e.g. Camera app or Keyboard app from a custom rom. How can I change it?

If I just paste a camera app from another custom rom is it will work? if not then how can I make it work.

I also want to change Keyboard of custom rom.

Please help me to do this.
[General Questions and Answers] pushkardua:
not sure.. no idea about it..maybe just changing the apk should wokrd for keyboard??

i don't know why but i think camera should not works by just changing an apk
[Huawei Ascend P7] car109:
Hello everyone , I can not understand why I do not get on my p7 never updates ota ( H3G ) , someone can explain ?
[Huawei Ascend P7] ibeqa:
Here's your Emui 3.0 update:

http://xdaforums.com/ascend-p7/general/ota-update-b615-t3033061
[Greenify] arpanbag1996:
I'm using greenify on CM11 (android 4.4.4). I have xposed modules installed. I want to know what is the difference between Root mode & Boost mode... And also is there any disadvantages of using experimental features?
[Greenify] Wycer:
If you are using the beta build, maybe, otherwise not.

Boost mode requires xposed to be active, where root mode only needs root permissions.

Boost mode is more powerful

Tapatalked from my D802 - CM12
[Greenify] arpanbag1996:
I'm using v2.5.2 downloaded from play store
[Greenify] Wycer:
Yeah that's the normal version, everything will work fine

Tapatalked from my D802 - CM12
[Greenify] arpanbag1996:
I switched to BOOST mode. Everything was working fine, then I noticed that greenify is unable to hibernate facebook automatically. I manually hibernated facebook. Then opened facebook again & after sometimes noticed that greenify has hibernated facebook. My question is why did it fail?
[Greenify] Wycer:
Sometimes apps uses some ways to stay in Android system memory, greenify can't freeze those

Tapatalked from my D802 - CM12
[Greenify] arpanbag1996:
Any solution?
[Greenify] Wycer:
Freezing them through a Tasker plug-in or a greenify shortcut will help I believe, at least does for my aps

Tapatalked from my D802 - CM12
[Greenify] arpanbag1996:
Sometimes hibernated apps are waking up automatically! Is it a bug of Greenify?
[Greenify] NickosD:
No, some other apps might waking them app. Enable the cut off thing and go over the app that wakes up and a pair of scissors will appear.

Sent from my bacon!!!!!
[Greenify] arpanbag1996:
The problem is happening in BOOST mode but not happening in ROOT mode. Should I revert back to ROOT mode?
[Greenify] NickosD:
If you don't have xposed installed, yes.

Sent from my bacon!!!!!
[Greenify] arpanbag1996:
I have Xposed
[Greenify] TNSMANI:
It is not a problem. Boost mode detects it, Root mode does not.

Since you have Xposed, it is for you to decide whether to use Boost or Root mode.
[Greenify] ek69:
I don't see where this "cut off thing" is?

Can you clarify plz?

In using 2.6 beta 4
[Greenify] TNSMANI:
Go to "Experimental Features" and enable "Wake-up Tracker and Cutoff".

Then when you click an app in Greenify which is pending hibernation (which was woken by another app), one of the options you will get is the "Scissors" icon.
[Greenify] ek69:
I don't have that option ( "Wake-up Tracker and Cutoff") in my list. I am on the beta version though, maybe it's not in that one?

Attaching images of my experimental features list
[Greenify] TNSMANI:
In Greenify beta, 'wake up tracker & cut off' is stated (by the Dev) to be built in, which means when an app is greenified, all its links are cut off automatically. That is why you don't get that option in beta.

However I have no idea whether that is working correctly since I have gone back to the stable version and not using beta since I found this feature not suitable for my needs.
[Greenify] ek69:
I found that when you click on some apps that are currently not in hibernation mode, sometimes a scissors icon appears in top left and you have to click that to enable that feature. Not all apps get that icon when clicked on though.

Tapatalk is one example, see attached screenshot
[Greenify] Raziel7:
After two pagesin this thread i don't say what is the difference between root and boot mode.... :D

I understand Boost mode with an experimental feature (with donation and xposed) it's capable to block any "push wake up" by other application....

There's other?
[Greenify] TNSMANI:
Tapatalk gets that scissors option as seen in your screenshot.

You might not get it for some apps if they are not woken up by another app. For instance, those which the UI or you wake up.

Be careful using the scissors icon because using it for an app will result in that app not being woken up by any other. For instance, if you cut off the wake ups for Google Play Services, it will not be woken up by others resulting in your losing half the functionality of your phone. Some actions can also brick your phone.
[Greenify] :
Boost Mode is more powerful

You can hibernate many apps for less than 2s with boost mode.

But it may take more time too hibernate apps with root mode.

These two mode can both hibernate apps automatically.

PS: On Boost Mode you don't need to enable device manager for greenify to get the long-touch to sleep feature.:cyclops:
[Moto X Q&A] numanair:
I have a moto x 2013 with an unlocked bootloader. I was on 4.4.2 and I decided to take the OTA. After flashing stock 4.4.2 and updating I flashed TWRP and my custom boot animation. It would no longer turn wifi on which I had solved in the past by reflashing stock. I stupidly tried to do this, and realize now that I have the 4.4.4 bootloader with 4.4.2 images. Is there anything I can do? Is there any way to flash 4.4.4?

Edit: I flashed TWRP and copied the ota to the sd card from a otg drive. I then flashed back the stock 4.4.2 recovery and used it to install the ota zip. I do not recommend others try this as I have no idea how safe it is. Avoid getting in this situation to begin with.

Now I need to know if I can try flashing TWRP again and what I did wrong with that last time? Or was it the boot logo/animation?
[Moto X Q&A] coles427:
You're fine to flash TWRP. The issues was you re-flashed it before taking the update last time. To update to 4.4.4 you have to do a stock restore to 4.4.2 first then install the update.
[Moto X Q&A] numanair:
I am almost certain that I flashed it after taking the update. The update won't flash with anything other than the stock recovery. It was probably user error of some sort when flashing.
[Android Q&A, Help & Troubleshooting] Zunera M:
Any guys know what languages does Huawei Honor 6 H60-L01 and H60-L02 support? For full LANGUAGES. Thanks in advance.
[Android Q&A, Help & Troubleshooting] Krystyna:
[IMG="huawei honor 6"]http://www.huaweimobileshop.com/media/wysiwyg/Honor/Huawei_honor_6_25.jpg[/IMG]

[IMG="huawei honor 6"]http://www.huaweimobileshop.com/media/wysiwyg/Honor/Huawei_honor_6_26.jpg[/IMG]

[IMG="huawei honor 6"]http://www.huaweimobileshop.com/media/wysiwyg/Honor/Huawei_honor_6_27.jpg[/IMG]
[XDA Assist] nitin_matrix:
What would be the best sub forum to talk about android based projectors?
[XDA Assist] Heisenberg:
Hi :)

Thanks for writing to us at XDA Assist. The General Discussion section is probably the best place for general discussion about the device.

General Discussion > General

Transmitted via Bacon
[Xolo Q3000] sachin.r.fulzele:
Found an easiest way to install custom recovery on Xolo Q3K with KitKat/Jelly bean, without using PC.

Things needed:

1) A rooted device

2) Flashify.apk ( u can download it from playstore)

3) Patience and .........

Procedure:

1) Download and install Flashify from playstore

2) Open flashify app, a prompt will appear, click accept, then it will ask for root permission, grant it and click ok.

3) Go to backup/restore tab and backup recovery, wait till backup completed.

4) Now, open file manager/explorer, copy your custom recovery.

5) Paste the custom recovery to folder: Android\com.cgollner.flashify\files\flashify-backup\recovery

6) Go back to Flashify app, click backup/restore tab, you will see your custom recovery listed there alongwith stock recovery.

7) Click on custom recovery, it will ask, Restore this recovery image, click yup!

8) Wait for restore to complete, a prompt will appear, click reboot.

9) It will reboot to recovery.

10) and surprise, you have custom recovery installed......

Procedure is universal and I guess it would work for all rooted android devices

Do it at your own risk, I'll not be responsible for bricked devices. It's tested lot of times and 100% successful, but still, you face any problem I'm here to help you....

:good::good::good::good::good:
[Xolo Q3000] sachin.r.fulzele:
Screenshots

Here are some screenshots....
[Xolo Q3000] avi3230:
Sorry to say [MENTION=5287331]sachin.r.fulzele[/MENTION] Sir,

no offense

U havnt seen this i think

VISUAL GUIDES - PART 1

VISUAL GUIDES - PART 2

03 - Flash custom recovery using SP flash tools

[YOUTUBE]ey_-3YT-h0U[/YOUTUBE]

VIDEO LINK******PPT LINK******​

06 - flashing custom recovery using app
Flashify
Mobile uncle tools

[YOUTUBE]05keW_WrUlA[/YOUTUBE]

VIDEO LINK******PPT LINK******​

:cool::cool:

its in my signature too
[Xolo Q3000] sachin.r.fulzele:
First of all, sorry Dr. Avi sir, because I haven't viewed these guides before. Today I've seen both ppt, but sorry to say that neither mobile uncle tools nor flashify worked for me on kk_s005, as mentioned in this method, it always reboot to stock recovery. One day I tried this & got success, so I thought, it could help others, That's why posted it here, still if you feel it's offence, then I'll delete the thread.

Sorry again.....
[Xolo Q3000] avi3230:
[MENTION=5287331]sachin.r.fulzele[/MENTION]

Ohhh don't feel bad anyways Sir. :o:o

I just made u aware of it that its already on the thread nothing else.;);)

And for me both mobile uncle tool as well as flashify worked well as u can see in guides.

U can go through all the guides when u have time and help me to improve them:good::good:

keep up the good work.
[Xolo Q3000] sachin.r.fulzele:
I think, you haven't pointed out the difference between your procedure and what I've written?????

Anyway, I've searched to delete the thread, but can't find. So, please, will you report to admin to delete this thread????

:good::good::good::good::good:
[Xolo Q3000] m0han:
same was my experience, as i'd posted in other threads. but some flashable zips did the trick - after a few tries. :D

haven't tried this method, though. good if "procedure is universal and would work for all rooted android devices". :good:
[AT&T HTC One (M8)] rafaelagp:
So here is my getvar all:

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 4.0.U606061@41216A

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 3.42.502.1

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: MOD EDIT

(bootloader) imei:

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul_ca

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B12000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 56f9ae32

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

What I want to do is flash a 4.16 firmware to run Android Revolution Lollipop, is it possible without changing radio bands?

Which firmware would do?
[AT&T HTC One (M8)] redpoint73:
You can always flash the radio of your choice manually after you install the entire firmware package.

Yes, it is possible to remove the radio from the firmware package (which should leave your current radio intact). But personally, I don't like to mess with firmware packages unless you really know what you are doing. Its one of the few ways to actually brick the phone.

Also if you are thinking about using a KitKat radio (such as the AT&T specific radio deployed with 4.4.4), with a Lollipop ROM, they might not play well together.

You might consider flashing the firmware package included on the following thread. Its the Dev Edition LP firmware, which is intended for use on AT&T's network (assuming that is your case). For that matter, if you are looking for a LP ROM on the AT&T network, you might consider the ROM itself. Some folks have had various issues running "Euro" based ROMs on AT&T's network.

http://xdaforums.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
[AT&T HTC One (M8)] rafaelagp:
thx for the reply, bro!

i won't be running it on at&t's network, i'm located in brazil, what i actually need is LTE 2600 (B7).

and from what i gather, i gotta go with either Euro WWE 401, Asia WWE 707 or unlocked, which are the ones that work in that frequency.

so, 401 it is.

i think i got the hang of it now, there were too many variables to understand at first :p

cheers.
[XDA Assist] thams001:
Mod Edit: Removed guide and info.
[XDA Assist] suresh.anthati:
Thanks
[XDA Assist] blaze_aura:
Thank

Thanks !
[XDA Assist] Speedygaurav26:
thanks
[XDA Assist] ritesh.aher:
Thanx
[XDA Assist] wilbur2brooks:
worked perfectly thanks
[XDA Assist] Asif_Awan:
Thanks :D
[XDA Assist] M Asad Khilji:
Thanks Dude
[XDA Assist] thams001:
message me on whatsapp guys!!!! Don't sms me
[XDA Assist] maoumushi:
Thanks
[XDA Assist] Sloth:
Greetings,

This is not the correct forum for this, please re-post in the correct forum..

Thread closed.

Thanks,

BD619
[Galaxy S 4 Q&A, Help & Troubleshooting] timonoj:
Hi guys,

After updating my modem with ZHUFNL1 (GSM_Modem_ZHUFNL1_and_LTE_Modem_ZHUFNL1.tar), the camera stopped working. I tested multiple different ROMs, and a full system wipe, with no luck. I have a Knox free bootloader, that means I don't even have the Knox warranty 0x0 message. Never upgraded to Knox roms. I saw in a post about installing a full ROM (bootloader and all) in order to get the camera fixed, but not sure if that would also get me knoxed? What are my options here?

Thanks!
[Galaxy S 4 Q&A, Help & Troubleshooting] Rhoban:
You will receive knox if you update.

But it can be removed if you have root. Or you can flash a stock rom that has knox removed.

I assume you don't have anymore warranty since the latest versions of the s4 come with the knox bootloader.

So it won't matter if you get knox and root the phone. There's no warranty to lose.
[Galaxy S 4 Q&A, Help & Troubleshooting] timonoj:
Thank you...I'd like to try first without knox. What do you mean it can be removed if I have root? I don't quite understand that.

Could you point me to a stock ROM with no knox?

EDIT: Oh I see, you talk about removing the app part from the ROM, but not the bootloader, right? Still, I'd like to install a knox-less ROM first...
[Galaxy S 4 Q&A, Help & Troubleshooting] Rhoban:
http://xdaforums.com/galaxy-s4/i9505-develop/rom-bhp-rom-v6-supercharged-t2833146

That is a knox free rom.

I haven't used it personally. though.
[JAM, MDA Compact, S100 Software Upgrading] FroZenFiRe:
is it possible to instead of making the whole 20 mb to Storage do only 19 MB so that i keep 1MB of Extended ROM? because i want to put the anti-theft thing on it.

Or is it impossible?
[G3 General] gianrond:
Hi guys,

I have the 855 version of this phone, and I have noticed that, even if Antutu scores are spot on (44k), in games such as GT racing 2 or similar I get a lot of lag.

Now, everyone will think "there are 1000 threads about lag, stick to those". Unfortunately, tricks such as getting rid of the thermal protection are really not good options, as the phone temperature will start to skyrocket.

There's a much easier and safer solution: root the phone and change the governor from interactive to conservative.

With interactive gov and CPU temp open in the background, I have noticed the CPU frequency bounces continuously up and down between 300mhz and 2400, even if the CPU temp is only 55c or so. This is causing the lag! Interactive governor is severely bugged, and this happens with any rom (I have tried both the stock 20h and the ChupaChups 4.2) and kernel (non AOSP at least).

Then, I switched to conservative, launched the game again, and guess what....now the frequency is nicely stable at 2457mhz throughout the entire gameplay and lag is gone completely. Temperatures? Totally fine: max 60c while playing and usually between 35 and 40 while whatsapping.

I literally tried everything to get rid of this damn lag, and the only thing that worked before this solution was to use a different kernel (chupa chups 2.1) and changing the governor...but I was getting crazy high temperatures, that sometimes touched 80c, and this was with a very heavy undervolt too! So I recommend to use the stock kernel, because it's the only one - for me at least - that grants good performances (and by that I mean no lag in games whatsoever and constant 2450mhz while playing) with good temperatures.

Any other option, including undervolting and trying different kernels didn't work for me, because either the CPU frequency kept shifting up and down every second causing lag, or - when I managed to keep it stable using different kernels and undervolting - the CPU temperature while playing got way too high (70c+, touching 80c sometimes).

To sum it up

1) Stick to stock rom and stock kernel (because of temperature issues)

2) Root

3) Change governor from interactive to conservative with Trickstermod (busybox required)

4) Enjoy smooth gaming experience and very good temperatures, with no significant throttle whatsoever!

Hope this helps!
[G3 General] superbonto:
as far as i know, conservative puts the cpu speed into the lowest possible, thus i thought won't be good for gaming performance.

nevertheless, i'd try for a few days and see if there's any noticeable difference.

thanks for sharing the knowledge, OP!