yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] hanspampel:
New update v6.12.8 available.:good:

6.12.8 (30.01.2014)

- time and date menu text formatting and order

- version display edit

- add ntfs write support to devices using kernel modules instead of fuse

- loki: merge "Support LG Optimus F7 ZV5_02"

- zip installer: update loki binaries for LOKI devices

- zip installer: use new update-binary sources

- add NTFS kernel module support for more Samsung devices

6.12.2 (28.01.2014)

- manually set time and date in recovery

- support Qualcom time daemon to sync time with main system (credits to dougiebee)

- support RTC offset hack for Qualcom devices without a proper time daemon in system ROM (credits to dougiebee)

- option to drop to system set time and date commands (credits to dougiebee)

- set default nandroid compression level back to low

- roll out exfat-nofuse sources from dorimanx into various kernels from Samsung and other brands

- code fix and cleanup

- New: Oppo N1

6.10.6 (23.01.2014)

- update SuperSU to 1.91

- merge android_system_core changes to adb to fix push to extra storage paths

- do not use performance mode during install zip: fixes hang on unmount /system in updater-script when usb cable is connected

- i9505 ans US variants: update kernel to fix random hang on boot

- update to CWM 6.0.4.7

- merge "Fix up bu restore"

- ROM Manager: workaround to backup/restore to/from external storage

6.10.2 (20.01.2014)

- enhance touch init (fix touch on some Sony devices)

- really fix reading device max brightness value

- loki: merge "Support Open EU LG Optimus F6 and US Cellular Optimus F7"

- New: HTC One X+ (enrc2b)

6.10.0 (18.01.2014)

- read the device max brightness setting to fix brightness toggle on some Sony devices

- merge: "Populate mount menu with new mount/format matrix" - final version

- merge: "Use cat for adb backup."

6.09.8 (16.01.2014)

- merge: "Populate mount menu with new mount/format matrix"

- New: Moto X variants: US Cellular (xt1055), Sprint (xt1056)

- New: Galaxy Tab 2 P3110 (p3110)

6.09.6 (15.01.2014)

- do not error on missing sd-ext when wiping dalvik cache

- merge: "su: Update for latest su daemon compatibility"

- merge "Clean up c formatting - 1"

- merge "Remove "Go Back" option from verify root and recovery options"

- merge "Fix potential chmod failures"

- merge: "Add a copy of the updater binary to the recovery resources"

- merge: "install: Support downgrade scenarios"

- merge: "install: Fix possible overflow condition in the updater "scanner""

- merge: "minui: do not use flexible array initialization"

- merge: "correctly mount tmpfs as /tmp in recovery"

- New: Sony Xperia SP (huashan)

- New: Sony Xperia T (mint)

- New: Samsung i9192 (serranodsub)

- New: Motorola Moto X variants: VZW (xt1060), GSM (xt1058), TMO (xt1053)

- New: Samsung Galaxy Note 10.1 LTE (n8020)

6.09.2 (12.01.2013)

- TWRP: merge "support use TW_USE_MODEL_HARDWARE_ID_FOR_DEVICE_ID"

- toggle prompt on low free space during backup

- SuperSU update to v1.89

- loki: merge "Support LG Vu 3."

- code cleanup

- New: US Cellular CH-R530U (d2usc) support

Download
[Nexus 10 Original Android Development] brees75:
Anyone else having issues flashing kernels with the new version? I get 'Error Code 7' regardless of the kernel. It's definitely an issue with the latest Philz recovery because I was able to flash after I reverted back to the previous version.
[Nexus 10 Original Android Development] hanspampel:
Never tried it. But maybe I give it a go. I think the binaries of the updater_script from the kernel could be the problem. Maybe they are outdated with newest PhilZ Recovery.
[Nexus 10 Original Android Development] SpudsterZ:
No problems here on either manta or d2usc. There is information about an "assert 7" error in the FAQ on the main thread.
[Nexus 10 Original Android Development] hanspampel:
It didnt work with Trinity TX1 Kernel with the latest PhilZ. I tried ThunderKat and Francos Kernel which was flashed successfully, but with Trinity i got status 7 error on data/media/0.... With the last vesion of PhilZ the same kernel works flawlessly.

[MENTION=4666971]Phil3759[/MENTION]

Log is attached
[Nexus 10 Original Android Development] Phil3759:
It is all in the faq

Rom maintainers should start to be uptodate with new kk standards

Else stick to older recoveries
[Nexus 10 Original Android Development] hanspampel:
Hi

Ive read your FAQ and tried it with different update_binariy files. But i wont get it to run.
[Nexus 10 Original Android Development] Phil3759:
set_perm: chown of /tmp/unpack_add_init.sh to 0 0 failed: No such file or directory

The time when cookers could just blindly copy paste their scripts is done

Script errors are not allowed as before
[Nexus 10 Original Android Development] hanspampel:
New version based on cwm 6.0.4.8 is out.

Changelog

6.26.6 (14.04.2014)

- m7 unified for m7ul, m7att and m7tmo

- CWM 6.0.4.8

- merge support for native dual boot devices

- sync sources

6.26.4 (12.04.2014)

- update libloki to latest sources

- broken root: help victims of bad custom ROMs

This adds extra code to detect if two su instances are installed in /system/bin and /system/xbin

It will kill both and properly apply SuperSU

- fixing root on exit was never done what ever was user choice

6.26.1 (06.04.2014)

- New: Note 10.1 2014 3G - SM-P601 (lt0wifiue)

- New: LG Optimus L7 P700 (p700) by @ali.filth

- New: Galaxy Grand Quatro (i8552) by @ali.filth

- New: HTC One mini (m4)

- fb2png: better error logging

6.25.7 (05.04.2014)

- New: HTC One M8 (m8)

- New: HTC One M8 sprint (m8spr)

- New: Note 10.1 2014 Wifi - SM-P600 (lt0wifi)

- derp cm_moto_msm8960

6.25.4 (31.03.2014)

- sort files using case insensitive order (adapted from @titanic-fanatic)

- use new ro.loki_disabled for unified variants not needing loki

This way, we only need to set the ENABLE_LOKI flag to have a loki enabled recovery

No more need to set an extra ro.loki_enabled property

Only modification needed now is for jflte variants not using loki

Only jflteatt and jfltevzw do

We have to set ro.loki_disabled to 1 for all other variants in libinit_jflte

- New device: Galaxy X Cover 2 - skomer

- New device: Galaxy S3 Mini - golden

- New device: Sony Xperia ZR (dogo)

- New device: Sony Xperia Tablet Z (pollux)

- New device: Sony Xperia Z1 Compact (amami)

- New device: Sony Xperia S (nozomi)

- New device: moto_msm8960 unified device (by @hachamacha)

- New device: Galaxy S Advance (janice)

- New device: Galaxy Ace 2 (codina)

- New device: Samsung Galaxy Tab 3 7.0 SM-T211 (lt023g)

Download
[Nexus 10 Original Android Development] Khaon:
[MENTION=4373586]hanspampel[/MENTION] [MENTION=4666971]Phil3759[/MENTION] hello, is this recovery including f2fs formatter ?

Envoyé de mon Nexus 10 en utilisant Tapatalk
[Nexus 10 Original Android Development] hanspampel:
No, or did you you read something else in the changelog ill posted above your post?;)
[Nexus 10 Original Android Development] Koopa777:
F2fs is in PhilZ for hammerhead, and the commits are available to compile from. I'm not sure if it would work with manta yet though.
[Nexus 10 Original Android Development] Khaon:
Should be, just need to ask f2fs too!s to be built but it requires few lines to be added. I ll take a look . sry Hans was kinda tired and could just drop the Q didn't even notice your post :D

Envoyé de mon Nexus 10 en utilisant Tapatalk
[Nexus 10 Original Android Development] Phil3759:
no, it's just a flag

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/boardconfig/BoardConfig.mk#L427

However, you must add f2fs drivers into kernel
[Nexus 10 Original Android Development] Khaon:
Hello, thank you! for answering! Seemes easier than TWRP then :D:D. Needed to add same flags but add in device.mk this maybe it is even useless didn't even try w/o :P

# Utilities : f2fs

PRODUCT_PACKAGES += \

mkfs.f2fs \

fsck.f2fs \

fibmap.f2fs

Well will you set the f2fs flag for next builds?? I think CWM is built with cyanogen right? I haven't cm sources atm.

About f2fs, it is included in KTManta kernel, plus I submitted/pulled him lastest official fs sources as now it has 3.4 support!
[Nexus 10 Original Android Development] Phil3759:
Do not add those lines in device.mk

Recovery is built with lib f2fs support
[Nexus 10 Original Android Development] Khaon:
Yeah, I wanted to try out w/o just before .. Is that it was a pain in the ass to find help... Neither on irc of big team, neither on topic. Neither from dev who did that already. And after a while when I learned moto x was f2fs , I could find out was just adding this flag the flag you gave. But 75% of source code was adding those line in device.mk so did it. But can you tell me how f2fs tools compiled bin are exported to out folder?

Furthermore, I did autoreconf and configure in f2fs tool folder, was that even required? To bad it lacked of information anyway now team seems to incorporate??

Will you in next update incorporate it? , it is true your recovery is quite amazing ;). I have only omni et slimkat build seems to get errors, I guess I could make a workaround but I ll just get the whole repo. You are compiling with CM? Or using fools of your own repo on github??

Thanks for answers btw!
[Nexus 10 Original Android Development] Phil3759:
You only need the flag, nothing more

f2fs tools are linked to recovery. As i said, we use it as built in lib

Compiling is very easy. Read main thread. It is well detailed
[Nexus 10 Original Android Development] Khaon:
Yep I have compiled the whole stuff, atm running twrp edited by Ktoonsez. I have the tools required to format, just few people asked me to compile for Philz as they prefer your ;). Was lacky just a lot of information just for some flag hehe. And as I told you many repo( such from big one teams are adding the lines i put or some other stuff that was irelevant for me).

But in order to compile just the recovery, do we need the full repo sync? Or what would I need, I saw you got few projet in your git.

I ll read main thread, right now, just I was told only hammerhead was having f2fs so I didn't went check, I should have :P

---------- Post added at 01:56 PM ---------- Previous post was at 01:46 PM ----------

Thank you found everythign I needed but have bandwitch enough to have fun recompiling with 2fs. Altough last question- well I am on your irc if you can come by later on. Shouldnt take long. It is about mounting device either with mount or sbin/busybox, it is not working maybe you could help somehow tell me where does it comes from, using proper fstab ( i think) heh and when i want to mount with busy box he cannt mount the actual partition mmcblketc.
[Nexus 10 Original Android Development] Phil3759:
For mamta, you shouldn't need any changes except f2fs flag (and f2fs hack the kernel obviously) since it is an officially supported device
[Nexus 10 Original Android Development] Khaon:
I was just reading my message Lol it has no sense. To summarize . on TRW you need to add this flag but add in devic.Mk the libs and that was the damn issue I ran into . kt kernel supports already f2fs and I pulled to his git updated sources. As I said I run already data and cache with f2fs. Some people however asked for your recovery instead of twrp that's why I asked and if only a flags is required it is much more smart.

My last question was if I want to compile your kernel is your repo is enough ? Or I ll need full cm with your sources to compile recovery supporting f2fs formating.

Anyway your work is amazing and if you plan to release soonish your recovery with f2fs say : don't to be thanked when I just compile amazing work from other even if I credit them

Envoyé de mon MI 2S en utilisant Tapatalk
[Nexus 10 Original Android Development] Phil3759:
You cannot compile any recovery without a full repo sync

They rely on external libs
[Nexus 10 Original Android Development] Khaon:
Ok i thought there might be some folder that could be ignored since i just use the make recovery command.

QQ in my country we got a download limit, and it is 100 GB for me
[Nexus 10 Original Android Development] Phil3759:
if you are already compiling twrp as you say, just replace bootable/recovery

Why download again cm?
[Nexus 10 Original Android Development] Khaon:
Omni files miss some files. I tried already.
[Nexus 10 Original Android Development] Phil3759:
ah

in that case you should sync to cm

Sad that omni and cm started to diverge in an incompatible way for recoveries
[Nexus 10 Original Android Development] Khaon:
But error I get is missing libs, maybe by just adding them it would work... But I have no idea how it might be painfull as I get just an error ofc when compiling.

So yeah sync full repo is easier. That's why I asked if you could release with the flag f2fs to true. I guess you build quite often and not even on your computer. But thats to have told about flag.

Thanks to [MENTION=4243514]Hashcode[/MENTION]

Here is how you add f2fs in TWRP just to show you difference : thanks otterx to share

When I think none of the dev that had ff2fs enabled were ignoring me, super sadly :D. Eventually I found out thanks to moto x ;o
[Nexus 10 Original Android Development] jblaylock:
Is this working with 4.4.3?

sent from the Paranoid Manta
[Nexus 10 Original Android Development] sash13:
Yep its does, CM11
[Nexus 10 Original Android Development] Izeltokatl:
Works on 4.4.4
[Nexus 10 Original Android Development] aheeejd:
No comments in 3+ months, I just wanted to check in & ask if this is still the greatest recovery & work if I want to flash 4.4.4 & then when I feel like it, if I wanted to flash back to 4.2, that will be fine to do correct? I used philz on my Nexus 5, & still use it on my l900 note 2. And on the l900 I have to drop to an older twrp if I want to flash, say, Rootbox 4.2.2, that's why I ask. Love this recovery, been using long long time, but totally new (2 days old) to manta device. Thanks for this phil, & tia to whoever replies.

Sent from my Nexus 10 using Xparent Red Tapatalk 2
[Nexus 10 Original Android Development] Izeltokatl:
I'm still using the recovery, and have been flashing a few 4.4.4 Roms just fine. Not entirely sure about 5.0, but a soon as a flashable version comes out, I'm trying it.
[Nexus 10 Original Android Development] aheeejd:
Cool thanks for that. I ended up changing to philz probably 2 weeks or so ago & its been fine.

Sent from my SPH-L900 using Xparent Red Tapatalk 2
[Nexus 4 Q&A, Help & Troubleshooting] razvanwin95:
What happened:

I am using a new Nexus 4 in various buildings on a campus (specifically, the University of Washington). For simplicity, let's assume that there are just two buildings, Building A and Building B.

There is a strong WiFi signal within both buildings, and I can connect to the WiFi network in either one. When I walk between buildings, the signal drops outside, and the phone switches to 3G networking (as expected).

Once I'm inside the other building, however, the WiFi does not always automatically reconnect. Instead, the phone will often remain on 3G mode, despite being in the presence of a strong WiFi signal.

If I restart the phone, the phone will then reconnect to the WiFi signal. Unless I do this, however, the phone will remain in 3G mode indefinitely. This drains the battery and results in high data usage with my phone plan.

Steps to reproduce the problem:

1. Connect to campus-wide WiFi.

2. Walk outside. WiFi connection will drop, and phone will switch to 3G.

3. Walk inside another building. Phone will remain in 3G mode, rather than switching back to WiFi, despite being in the presence of a strong WiFi signal.

4. Restart the phone. After rebooting, the phone will now connect to the WiFi network.

What you think the correct behavior should be:

The phone should automatically switch back to WiFi when in the presence of a suitable WiFi signal. A manual restart or manual reconnecting to the network should not be necessary.
[Nexus 4 Q&A, Help & Troubleshooting] Jsparta26:
What kernel are you using?
[Nexus 4 Q&A, Help & Troubleshooting] razvanwin95:
stock kernel from paranoid 3.50

(molesarecoming)
[Nexus 4 Q&A, Help & Troubleshooting] scream4cheese:
Did this issue occur before you were on PA rom 3.5?

If it didn't then I think it could be the rom if it's not then it's the school's wifi. It happens to me when I'm on campus too and I found out it the school's WiFi network was getting hammered and the signal was disrupted. No clue how that any of that happened.
[Nexus 4 Q&A, Help & Troubleshooting] svandys:
Hi, I have the same problem. Did anyone manage to solve it? I have my Nexus 4 since yestereday and it's not reconnecting to my home wifi. Previous phone HTC Incredible S didn't have this issue and since that phone my wifi settings wasn't changed. I have AirLink AP, no name router and wifi is encoded with WPA. But i don't have to restart the phone to reconnect. It's enough to turn wifi on the phone off and on in settings. But it's really annoying. Thanks for hints.

And please excuse wrong expressions, I'm from Czech republic ;)

Edit: I have stock rom, JB 4.2.2
[Android Apps and Games] firered365:
How about Jump VNC.
[Android Apps and Games] Shubham87:
Added. :)

Lemme know if there are any more..
[Android Apps and Games] zYmJ4:
vnc or ms rdp - very nice.
[Windows Mobile Development and Hacking General] new_to_imate:
Trying to write a program to record phone calls and act as answering machine. I'm initializing TAPI, opening the cellular line, then trying to use lineGetID to get the "wave/in" and "wave/out" devices id's, this last function call always returns the same error "the operation failed".

Any thoughts???
[Windows Mobile Development and Hacking General] mamaich:
as I've wrote before it is impossible to make an answering machine. You can record phone calls, but cannot play anything to the line. It is a software limitation in CE 4.20
[Windows Mobile Development and Hacking General] edsub:
HOW can you record phone calls

(sounds handy when certain callcentre agents make promises)
[Windows Mobile Development and Hacking General] mamaich:
built-in recorder can record calls. You may decompile it to find how it is working. I think that code used to record calls is the same as recording from a device microphone when the call is not active.
[Windows Mobile Development and Hacking General] nutitija:
How would you use LineGetId in order to recieve data calls through TAPI ?? I'm struggling udnerstanding where this function should be implemented and what it actually does.

Thanks for all your help !!!
[Windows Mobile Development and Hacking General] IIIu30uD:
After you catch CONNECT event (media type is datamodem) you must get handler of opened serial device for data transmition

1)LPVARSTRING lpVarStr;

2)Allocate memory for lpVarStr;

3)Call lineGetID

for example: lineGetID(0, 0, hCall, LINECALLSELECT_CALL, lpVarStr, TEXT("comm/datamodem"))

4-th parameter means how call will be selected

LINECALLSELECT_CALL - select by specified call

also you can select by deviceID, address, line etc

last parameter specifies device class (look msdn for possible values)

4)check lpVarStr->dwNeededSize

5)Realloc lpVarStr

6)call lineGetID

7)get handle of serial device *(LPHANDLE)((BYTE*)lpVarStr + lpVarStr->dwStringOffset))
[Windows Mobile Development and Hacking General] OdeeanRDeathshead:
I think you will find that the ability to record the incoming audio is only as a result of the microphone picking up the audio from the speaker. I have tested everything I can think of to do this and hit a brick wall. firstly if you check the linedevcaps for each line device, non support the "wave/***" classes needed. Secondly the linegetid will always fail because of the way the line is being opened. To open a line correctly to use "wave/***" in linegetid, the dwmediamodes flag of lineopen needs to be set to LINEMEDIAMODE_AUTOMATEDVOICE. If you did not an error of LINEERR_INVALMEDIAMODE returns. If your error is LINEERR_OPERATIONFAILED, I think it could be coming from your timing of when you call linegetid. This will not work on any device I have because the hardware will not support it.

There is a physical seperation between the hardware that picks up and sends voice, and the computing hardware. I first encountered this while using an audiovox rtm8000 card in a toshiba e570. The modem built into the card can communicate data over the port but dose nothing with audio. That may sound irrelivant exept that later audiovox started selling the hardware combination built together under their brand as a pda phone to compeat with xda. They modified it by hooking the system speaker and mic up to the card with extra wires internally. All pda phones are arranged essentially like this. the fact that you cant see a seperate "phone card" makes it deceptive.

.

.

.

.

.

loose end. How dose my bluetooth wireless earpeice get the audio from my xdaII. Explore that, I am.
[One (M7) Android Development] cschmitt:
Updated 05/23/2013:

Stock base ROM that anyone can use for mods, cooking, theming, etc.

Download: m7_stock_dev_1.29.1540.16_signed_052313.zip (now includes /data/preload apps)

Base rom: HTC One Developer Edition v1.29.1540.16

- Stock Kernel + mods:

- /system/etc/init.d support

- Disabled /system write protection via init.rc call to insmod /system/lib/modules/wp_mod.ko

- /data/preload apps included and flashed with rom.

- Stock ROM + mods:

- Deodexed, zip-aligned

- Rooted with SuperSu apk and su binary.

- /system/lib/modules/wp_mod.ko included.

- Busybox, with symlinks in updater-script

Please don't ask for additional mods or features, it won't happen (at least not by me). I'm only providing this as a stock base rom for other's to customize as they see fit. It's the base for my current daily driver.

FAQ:

1. Can I flash this on an AT&T, T-Mobile, etc. One? Yes, any GSM model will do (NOT Sprint or VZW). Just unlock bootloader, install custom recovery, and flash away.

2. Will I get Dev Edition OTA updates? Yes and no. Yes, you will receive notification of updates and they will download and attempt to install, but the installation will fail because (1) you're running a custom recovery and (2) the OTA updates do a CID and MID check and anything other than CID BS_US001 (or super cid) and MID PN0712000 will fails this check, and (3) this rom is deodexed so OTA's can't be applied anyway (OTA's do binary file patching of .apk and .odex files.)

But, fear not -- if an OTA for the Dev Edition is released then this thread will be updated to that release in short order.

3. Can I ask the OP stupid, lame questions without first reading the entire thread and searching for a solution on XDA? No, you can't. I'll just ignore them. (but relevant questions from reasonable people are always welcome!)
[One (M7) Android Development] wmg316:
Thank you!! Is this scripted to flash the boot.img? Or do we need to flash via fastboot?
[One (M7) Android Development] cschmitt:
It will flash boot.
[One (M7) Android Development] CheesyNutz:
Other than this being a dev 64gig room would this flash on a normal 32 att phone?
[One (M7) Android Development] NJGSII:
Should work just fine.
[One (M7) Android Development] jacksonj51:
Excellent! Thanks for this... and no crappy ass Aroma installer
[One (M7) Android Development] cschmitt:
NP, and thanks for shopping with us!
[One (M7) Android Development] wmg316:
Is there any way to get the missing apps that disappeared during deodex? Like calculator, flashlight, and voice recorder?
[One (M7) Android Development] cschmitt:
They are in /data/preload, I'll create a zip of them when I get a chance.
[One (M7) Android Development] can7:
just checking do you flash through recovery ? :good:
[One (M7) Android Development] wmg316:
Lost Data Apps

Here is a flashable zip (through recovery) for the "lost" data apps from the deodex process.

Contains:

Calculator, Flashlight, HTC Ringtone Trimmer, HTC Sound Recorder, PDF Viewer
[One (M7) Android Development] npalmy:
I can not download? Maybe Dev Host

Anyone have a link?

Nevermind .... this morning I can download

Thanks
[One (M7) Android Development] lupin_iii:
I just flashed this on my AT&T version 64Gig HTC ONE and all is well.

Big thanks to cschmitt!! :good: