yashsingh1/xdaforums huggingface dataset:
[X2 Q&A, Help & Troubleshooting] iDuc:
Hi There

We Have Some Problems With Gapps Since 2.1 update

can any body test any Gapps Package and tell us the result icant do it because idont have access to my pc now and if any thing goes wrong i will not be able to fix it can any body try this and reply

Gapps: http://d-h.st/3uP
[Nexus 5 Q&A, Help & Troubleshooting] albert_htc:
Hi

Widgetsoid is telling me it needs to be a system app so I can toggle data on L.

I'm rooted and have a working es file manager.. How do I move widgwtsoid to be a system app ?

Thanks

Sent from my Nexus 7 (2013) KitKat 4.4.4
[Nexus 5 Q&A, Help & Troubleshooting] Wakamatsu:
Cut and paste the apk from /data to /system/apps, set the permissions and reboot.
[Nexus 5 Q&A, Help & Troubleshooting] euqiddis:
What should the permissions be set to?
[Nexus 5 Q&A, Help & Troubleshooting] albert_htc:
I used an app to do it, but it didn't work.

I'm currently using power toggles and data toggle 5.0 as a command to toggle the data.

Seems to be working OK
[Nexus 5 Q&A, Help & Troubleshooting] Wakamatsu:
Set the permissions to the same as all the other apks in the folder.
[Nexus 5 Q&A, Help & Troubleshooting] euqiddis:
Doesnt seem to work, even after moving and rebooting,its still saying to add it as a system app.
[Nexus 5 Q&A, Help & Troubleshooting] albert_htc:
That's the same issue I had.

I'm now using power toggles abs and data toggle 5.0

That seems to work well.
[General Questions and Answers] Fharx:
Hi guys,

I've a Alcatel One Touch Tab 7HD and it is breaking up at some points and i woundered, if can i get a new rom, as lightweight as possible.

The thing is, where can i get it and how to install it or the best way to do it, safe and clean.

Any suggestions are welcome.

Thank you all! :)
[General Questions and Answers] bonds350z:
First you would haft to root it, the install a custom recovery, and install the rom in the recovery, search for a thread on rooting your device.
[General Questions and Answers] Fharx:
And then? Which ROM do you think I can use and how to do it? Ty.
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
Simce the galaxy player 4.0 has official cm11 support, i was wondering how hard would it be to port cm12 to the galaxy player 4.0? I tried to compile cm12 from source. I used beblos's ypg1 cm11 device tree/kernel, but compiling failed.

bootable/recovery/minadbd/services.c: In function 'sideload_host_service':
bootable/recovery/minadbd/services.c:55:5: warning: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'uint32_t' [-Wformat=]
printf("sideload-host file size %llu block size %lu\n", file_size, block_size);
^
target thumb C: libminadbd <= bootable/recovery/minadbd/usb_linux_client.c
target thumb C: libminadbd <= bootable/recovery/minadbd/utils.c
target thumb C: libfusesideload <= bootable/recovery/fuse_sideload.c
make: *** No rule to make target `/home/owner/android/system/out/target/product/ypg1/utilities/flash_image', needed by `TARGET_KERNEL_BINARIES'. Stop.
make: *** Waiting for unfinished jobs....
host Java: dumpkey (/home/owner/android/system/out/host/common/obj/JAVA_LIBRARIES/dumpkey_intermediates/classes)
bootable/recovery/fuse_sideload.c: In function 'fuse_reply':
bootable/recovery/fuse_sideload.c:108:21: warning: assignment discards 'const' qualifier from pointer target type [enabled by default]
vec[1].iov_base = data;
^

this is where it initally fails.
[Samsung Galaxy Player 4.0, 5.0] Meticulus:
It looks like the "utilities" in the out dir has moved... Look inside "symbols" in the out dir and change your code accordingly ;)
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
I do not have a symbols folder
[Samsung Galaxy Player 4.0, 5.0] Meticulus:
It should be here: /home/owner/android/system/out/target/product/ypg1/symbols

If it's not there then, probably, none of the symbols have been built yet.

You probably need to modify your shbootimg.mk in your device tree.

If you have $(PRODUCT_OUT)/utilities/flash_image you probably need to change it to $(PRODUCT_OUT)/symbols/system/bin/flash_image ...

This is just a guess though... but I've had similar problems with CM12 on venturi...
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
I did the changes and I will try to compile again later. Thanks for your help.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
[MENTION=4437780]dorfd1[/MENTION] Normally the flash_image get compiled at the same time as building it. My guess it maybe the librairy isn't added yet into the CM tree so what I do as a dirty quickfix is to take a flash_image from somewhere else (I would take it from CM11 builds) and copy it to the /utilities directory.
[Samsung Galaxy Player 4.0, 5.0] Meticulus:
Forgot to fix this one:

$(PRODUCT_OUT)/utilities/erase_image

$(PRODUCT_OUT)/symbols/system/bin/erase_image ?

Also: You might need to explicitly add the recovery ramdisk too.:

https://github.com/Meticulus/androi...mmit/d10d588bdbabf9cc8480ae6b540b9ff051b718a0
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
I commented out bml over mtd and erase image. Now cm12 is compiling, I assume I can add those binaries back into the zip by using the cm11 ones?

I did have another error during compiling, but the forum was down and I was not able to share it, I am compiling again and will share the error when I get it.
[Samsung Galaxy Player 4.0, 5.0] Meticulus:
The problem would seem to be here:

ALOGV("write_int: path=\ "%s\", value=\"%d\".", path, value);

There is a space between the escape char and the escaped char. I think it should be like this

ALOGV("write_int: path=\"%s\", value=\"%d\".", path, value);
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
Are you referring to lights.c?
[Samsung Galaxy Player 4.0, 5.0] Meticulus:
Yes, from the log you posted:

device/samsung/ypg1/liblight/lights.c:41:2: error: stray '\' in program
ALOGV("write_int: path=\ "%s\", value=\"%d\".", path, value);
[Samsung Galaxy Player 4.0, 5.0] Meticulus:
You are aware that "warnings" do not stop compliation right?

The error is here:

hardware/libhardware/modules/local_time/local_time_hw.c:53:45: error: parameter name omitted
static uint64_t ltdev_get_local_freq(struct local_time_hw_device* )

And, never seen this one before but it looks like @ line 53 on char 45 of file hardware/libhardware/modules/local_time/local_time_hw.c , there is a function call to "ltdev_get_local_freq" and there is something wrong with the passed parameter....

;)
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
I do know that warnings do not stop compilation
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
I think we need to wait for official nightlies to happen for other devices. I just tried to compile cm12 for my tab 2 and one of the devs said to wait since stuff like surfaceflinger is broken.
[Samsung Galaxy Player 4.0, 5.0] Meticulus:
You can wait if you want to but I'm not going to. It is entirely possible that some older device's may not be brought up to CM 12 ;)

This means us.

This means us too.

From here: http://www.gadgtspot.com/2014/10/31/roundtable-cyanogenmod-12-roadmap-leaked-fun-times-ahead/
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
What issues so far did you have with cm12 on venturi?
[Samsung Galaxy Player 4.0, 5.0] Meticulus:
https://github.com/Meticulus/android_device_samsung_venturi/commits/carbon-l
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
During compile did it stop at surfaceflinger?
[Samsung Galaxy Player 4.0, 5.0] :
I not sure, but I don't think so... Surfaceflinger built fine... Oh, I did have to add some HAL PIXEL FORMATS ...
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
I'm sorry to ask this. Were you able to get lollipop booting on venturi?
[Samsung Galaxy Player 4.0, 5.0] :
No, not yet... Recovery is the problem... I'm still trying to get a recovery built that can flash the build... :eek:
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
What's the error when you're trying to flash the build?
[Samsung Galaxy Player 4.0, 5.0] :
Unknown function "block_flash_update" .... ( from memory )

It seems there is a OTA flash method, introduced in lollipop. So an updated recovery is necessary.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Hmm when do you check the zip file, do you see a system.dat file or it's the regular zip format? Because indeed in lollipop they introduced OTA updates check by a block instead by checking the apps signature.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Samsung Galaxy Player 4.0, 5.0] :
Thanks [MENTION=4217103]zaclimon[/MENTION], I think I have figured out how to revert back to the old file based recovery installation ;)

Removing this line should do it:

https://github.com/CyanogenMod/android_build/blob/cm-12.0/core/Makefile#L1616
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Yep that's exactly this line. (I thought CM would have removed it though..) You should have no problem flashing the zip. :)
[Samsung Galaxy Player 4.0, 5.0] daniel644:
just read about this, http://xdaforums.com/galaxy-s-i9000/i9001-development/gt-i9001-cyanogenmod-12-0-adc-team-t2971987 how similar is the SGP 4.0 to that device? perhaps some of the hurdles they had to work thru could help here.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Aside from design, everything is different about this device from the SGP 4.0. The most important parts (which are the CPU/GPU) are Qualcomm's and we use Samsung/Imagination stuff. The closer we could get is with the original Galaxy Tab in which we share some simillarities, the Nexus S and the Original Galaxy S I9000.
[Samsung Galaxy Player 4.0, 5.0] FlinderMouse:
Not to be a nuisance or anything, but what kind of progress has been made on this? The thread just sort of died...
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Nothing on my end so far because I wait for my CPU to get shipped. (sorry about it) Then once my new computer gets built, I'll go through this.
[Samsung Galaxy Player 4.0, 5.0] storm31:
Still same fails with ../out/utilities/.. I try to compile for old Galaxy Tab 1. We have same kernel now and similar device trees. I got now a compiled build (with manual copying of utilities from cm 11.0 and selinux things are disabled for now), but it doesn't boot.

we can try collectively to get it ready..
[Samsung Galaxy Player 4.0, 5.0] :
It seems that the "flash_image" project has been changed/removed in cm12

It's here in cm-11.0:

https://github.com/CyanogenMod/android_bootable_recovery/tree/cm-11.0/flashutils
[Samsung Galaxy Player 4.0, 5.0] storm31:
Yes, you're right. I have seen make_ext4fs is now in /system/bin: https://github.com/Meticulus/androi...mmit/78ed9f9ba52c44449b8ce2a838e8c869c141c034. Is this your solution or from cm team?
[Samsung Galaxy Player 4.0, 5.0] :
It's mine, but I have just recently learned that binaries in the "symbols" dir are unstripped and therefore much larger in size.... The way it is now does work, but the binaries are much larger than they need to be...
[Samsung Galaxy Player 4.0, 5.0] storm31:
Seems omni for GTab doesn't have these problems...

I haven't much time for developing Android and cm gurus aren't particularly talkative (to noobs:)). It's really very difficult to find why some things do work or don't work:)

Here is my repo: https://github.com/storm31. I hope you find anything what you helps:)
[Samsung Galaxy Player 4.0, 5.0] :
I made some notes for you on your github of stuff that I think is not working... Hope it helps.. :D
[Samsung Galaxy Player 4.0, 5.0] storm31:
Thank you for commits!

I had one problem with block based ota and have found this here: http://help.howproblemsolution.com/1285723/cm12-and-lollipop-mount-point-fix-zip-fix..

Now i have switched recovery to TWRP - no problem with flash_image and so one. I must copy only make_ext4fs manually.

This commit does brick my kernel compilation: https://github.com/CyanogenMod/android_build/commit/97ce0744766db922c216a3ef4b48226f069ad66e - your too?

My compiled build still stays on Samsung logo and i can't into recovery.. I must flash old boot.img (4.4.4) with heimdal.. selinux? I have no idea at the moment..
[Samsung Galaxy Player 4.0, 5.0] :
You need a patch for non-pie -- that flag does nothing.... in CM.:good:

EDIT: OTA releasetools messes up my boot.img but I just replace it with the one directly in the $(PRODUCT_OUT) dir and it's fine...
[Samsung Galaxy Player 4.0, 5.0] storm31:
Have found this flag on gerrit: http://review.cyanogenmod.org/#/c/84785/1/BoardConfigCommon.mk. I think it should work for me too.. Or not?

EDIT:

Which one do use your builds?

Other thing: my recovery seems to lose root. I have reverted one commit in vendor/cm, but still no success..
[Samsung Galaxy Player 4.0, 5.0] :
I use this one:

https://raw.githubusercontent.com/d...eenable-support-for-non-PIE-executables.patch
[Samsung Galaxy Player 4.0, 5.0] storm31:
I try tomorrow this one too : http://review.cyanogenmod.org/#/c/81758/1/core/combo/TARGET_linux-arm.mk

Other thing: my recovery seems to lose root. I have reverted one commit in vendor/cm, but still no success..
[Samsung Galaxy Player 4.0, 5.0] :
I'm sorry man, I'm a developer. If you want my help, you have to describe problems in detail. I don't have time to play 20 questions... ;)
[Samsung Galaxy Player 4.0, 5.0] storm31:
No problem, I must apologize. If i need tips or help, i will be more specific. Thank you for your time, time to sleep for me:)
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
[MENTION=3380725]storm31[/MENTION] I will receive my new CPU monday so the least I should install it by next friday and I hope to work on it by next sunday. (I know I'm pretty late... -.-) Where is your progress so far?
[Samsung Galaxy Player 4.0, 5.0] storm31:
I got some hints from Meticulus (thanks!) - about bionic, selinux, device flags and so one, but have current no time to try it. I have some compilation error with selinux in device tree - i think i will have a little bit time on week end.

Greetings
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
[MENTION=4400604]Meticulus[/MENTION] I'm trying to get CM12 working and I was wondering if you used the re-implementation of pvrsrvinit here:

https://github.com/omnirom/android_device_samsung_aries-common/commit/885716d71361f39376318e3e1a6ad511189277ee

I suppose that with the Non-Pie patch, it would work without it but we never know. ;)

Also is using the block OTA method does something?
[Samsung Galaxy Player 4.0, 5.0] :
Nope, just using that patch.... :good:
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Alright! Also you may have found yourself that at some point the build just doesn't make the recovery-ramdisk. I guess what you did were only to cpio manually the recovery ramdisk inside /recovery/root? (well that's what I was doing because the build do inflate my boot image size strangely.)
[Samsung Galaxy Player 4.0, 5.0] :
Yes, in lollipop, including the recovery ramdisk causes the boot.img to be to large so I am using this:

https://github.com/Meticulus/nutell...mmit/027d95bb558d2de6f5c1dad0e78108043f512cfe

to load recovery ramdisk from /cache

This will build recovery ramdisk but for me new recoveries are still not working anyways:

https://github.com/Meticulus/androi...mmit/d10d588bdbabf9cc8480ae6b540b9ff051b718a0

Luckily for me, I started building "alternative" recoveries using my new system when I was building KitKat...
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Ohh well, looks like I'll pick an old recovery-ramdisk.cpio if ever new recoveries doesn't work. -.-
[Nexus 5 Q&A, Help & Troubleshooting] qorron:
hi there

n5, cwm/twrp recovery, root

installing the ota via recovery does not work because the install script complains about the fingerprint.

responsible statement in the script:

getprop("ro.build.fingerprint") == "google/hammerhead/hammerhead:4.4.4/KTU84P/1227136:user/release-keys" ||
getprop("ro.build.fingerprint") == "google/hammerhead/hammerhead:5.0/LRX21O/1570415:user/release-keys" ||
abort("Package expects build fingerprint of google/hammerhead/hammerhead:4.4.4/KTU84P/1227136:user/release-keys or google/hammerhead/hammerhead:5.0/LRX21O/1570415:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");

line in my build.prop:

ro.build.fingerprint=google/hammerhead/hammerhead:4.4.4/KTU84P/1227136:user/release-keys

here's the catch:

in cwm recovery it claims I have some old android 4.4 version, with twrp it believes it is 4.4.4 but with test-key, not release keys.

usually I upgrade my nexus devices by installing the otas via a custom recovery and reroot after that. this has worked fine so far (since the days of the nexus s)

perhaps someone could provide some insight.
[Nexus 5 Q&A, Help & Troubleshooting] upndwn4par:
First off, questions go in Q&A. And realistically, this should go in the OTA Help Desk thread.

As for your issue, you can't flash an OTA from a custom recovery any more. You must be 100% stock for the OTA to work. I read about it this recently. I'll update this post if I can find the link.

Edit:

Here are some links:

http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/

https://source.android.com/devices/tech/security/dm-verity.html#block-otas
[Nexus 5 Q&A, Help & Troubleshooting] Darth:
This guy ^^^^ knows his stuff.

And he's right, There's a thread about OTA's...

http://xdaforums.com/showthread.php?t=2523217

Good luck!
[Nexus 5 Q&A, Help & Troubleshooting] upndwn4par:
This guy ^^ too. ;)
[Nexus 5 Q&A, Help & Troubleshooting] Nitemare3219:
I still got this error with the stock recovery. Flashed the system, recovery, boot, and radio images of 4.4.4 and all was well.
[Nexus 5 Q&A, Help & Troubleshooting] Darth:
Delete
[Nexus 5 Q&A, Help & Troubleshooting] XeLLaR*:
Just flash the factory image through fastboot! But dont flash userdata.img, otherwise it will wipe your data partition.

Performing this task is basically the same as an ota.

Gesendet von meinem Nexus 5
[Nexus 5 Q&A, Help & Troubleshooting] gregbradley:
Please use the QUESTION and ANSWER section to ask QUESTIONS that you want ANSWERED

Thread moved
[Nexus 5 Q&A, Help & Troubleshooting] qorron:
I'm sorry, but these hints must be for a different ota.

just look at the script for yourself and you will see that there is no direct partition patching going on. first of all, the first command mounts the system partition. we all know that directly modifying a mounted fs is a bad idea. and then the patch lines. they all patch single apk (or other) files. one at a time.

the ota I'm referring to is "c1a33561be84a8a6a7d5a4c8e3463c4db9352ce6.signed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip" maybe there are different versions.

never the less, the articles about patching whole partitions are insightful.

as for the os fingerprint, I believe that the recoveries somehow have a fingerprint too which was ignored in the past but is now used for comparison.

I'll flash the factory images once I get a round tuit.
[Nexus 5 Q&A, Help & Troubleshooting] J.Diogo:
Hey guys.

When I receive a notification and it pops up as a headsup notification I can't press it or pull down the notification bar. The only thing I can do is swipe it away.

By HeadsUp notifications I mean the new notification card that appears when in full screen.

[IMG]http://img.wonderhowto.com/img/90/97/63539367470020/0/get-new-android-l-heads-up-notifications-your-nexus-5-other-android-device.w654.jpg

When these appears I can't press neither the notification nor the quick action buttons[/IMG]

Is this also happening to you?
[Nexus 5 Q&A, Help & Troubleshooting] Raistlin1:
Deleted, my mistake.
[Nexus 5 Q&A, Help & Troubleshooting] MarcoMontreal1:
This is a bug in heads up app , developer is aware and should be fixed in next update, for now , stop using it . Wait till it updates again to try it again
[Nexus 5 Q&A, Help & Troubleshooting] J.Diogo:
But isn't there a quick fix for it? Apparently it doesn't affect everybody.
[Nexus 5 Q&A, Help & Troubleshooting] MarcoMontreal1:
I don't think there is a quick fix , if there is i don't know what it is. What i can tell you it affected me, the app would work but it would freeze the top of my screen, just under the status bar and the only temp. fix would be reboot the phone, but the problem comes back . Only thing i would suggest, is don't use the app till the developer updates the app and has the problem fixed . If you don't want to wait , you can keep restarting your phone , every time the bug happens , which is annoying
[Nexus 5 Q&A, Help & Troubleshooting] J.Diogo:
But for me the problem isn't just in a specific app. It's system-wide I think.

For example when the low battery warning pops up I can't even press the button to turn on battery saver.
[Nexus 5 Q&A, Help & Troubleshooting] MarcoMontreal1:
yes the freeze at the top of the screen , is there all the time , which the headsup app is causing part of your top screen to not be responsive to touch. Try turning the headsup app off , stop it , don't have it running. Once the app is no longer running and is off , reboot your device , then see if the problem comes back or not. ** Don't use the app at all once you reboot **
[Nexus 5 Q&A, Help & Troubleshooting] J.Diogo:
What app?
[Nexus 5 Q&A, Help & Troubleshooting] MarcoMontreal1:
the headsup app, thats the only app , I have been talking about this whole time lol . Turn off the headsup app , reboot your phone , and dont use the headsup app at all . See if your phone is fine and the problem goes away
[Nexus 5 Q&A, Help & Troubleshooting] J.Diogo:
Maybe I didn't explain myself very well, I apologize.

By HeadsUp notifications I mean the new notification card that appears when in full screen.

When these appears I can't press neither the notification nor the quick action buttons.
[Nexus 5 Q&A, Help & Troubleshooting] MarcoMontreal1:
ya that is a bug with headsup app , turn the headsup app off , dont uset it . That is whats causing you to not able to press the card . Don't use the headsup app no more , wait till it updates , then try it again
[Nexus 5 Q&A, Help & Troubleshooting] jericho7:
In having the same issue, can't action the notifications, just swipe them away
[Nexus 5 Q&A, Help & Troubleshooting] Lokke9191:
Lol. This thread is hilarious. There is no "heads up app". My heads up notifications work fine. How did you install 5.0? I installed via fastboot, flashing the images one at a time, while rebooting the bootloader in between each image. I have none of the problems all these people in different threads are complaining about. Everything works perfectly, battery life is greatly improved from kitkat, no issues. Reinstall that way, cleanly, erase everything first, bootloader, radio, system, cache, userdata, boot, everything. Then install all the new images. The Google script for 5.0 is buggy, and these dirty installs are giving people problems.
[Nexus 5 Q&A, Help & Troubleshooting] Slavor:
I too, have this problem, and I did a clean install using the Nexus root toolkit.

This problem disappears after I do a reboot, and resurfaces when I get a message from either hangouts or messenger (so far). This bug doesn't appear even after I repeatedly call myself (because I still can decline or accept the call), but only appears when I get a heads up notification of messenger or hangouts.

Anybody manage to solve it yet?
[Nexus 5 Q&A, Help & Troubleshooting] mayurh:
I've got the same issue. Very frustrating, doesn't work even after reboot .I also started with a clean install via factory Image
[Nexus 5 Q&A, Help & Troubleshooting] Slavor:
Is there any pattern to it? Like I mentioned in my post, this problem only seems to pop up once I get notifications from Hangouts or Messenger. Calls seem to be fine (after a reboot).
[Nexus 5 Q&A, Help & Troubleshooting] tahsin.ahmed:
I can assure that same bug presists on nexus 4. Flashed everything cleanly.
[Nexus 5 Q&A, Help & Troubleshooting] alcurtis93:
I have this issue too. Its incredibly annoying! Anyone found a fix? I installed using nexus root toolkit
[Nexus 5 Q&A, Help & Troubleshooting] Lokke9191:
It seems all of you with this problem have installed using a toolkit. Try a clean install, erase everything, using fastboot. And stop using toolkits, and wondering why you have problems and bugs.
[Ascend Mate 7 Q&A, Help & Troubleshooting] ipmanwck:
As the title indicates please feel free to post questions
[Ascend Mate 7 Q&A, Help & Troubleshooting] thering1975:
How's the network speed with the device both LTE and HSDPA be interested to know how it handles on UK network