yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Phil3759:
ended up with

Did not note it was an arm v6 :p

Guess it would need a deep hack into the repo, which I cannot afford time and resources wise

Dropping this for now. Next please, only provide complete dependencies and needed patches so that I can have a general view before wasting time! Ideally a local xml or link to all git merges needed

Soon, when I release a lib touch redistributable, you could go with full gui too, hopefully
[Android Software Development] Phil3759:
mokee hacks every thing from cm_device to mk_device

That breaks all my custom generic builder

I do not plan to make it mokee friendly for now!

But, I see the d710 has a cm-11.0 CyanogenMod device tree and it inherits all the galaxys2-common device tree, which is actively maintained

I guess I can just build on CM git if you test and report it is fine
[Android Software Development] Bhargav97:
Thanks for your effort into it. I will try to get you all the complete dependencies and needed patches asap. Hope you release your lib touch redestributable soon...
[Android Software Development] tvm2487:
Yes you can build using the cm stuff and it will be fine for mokee the only changes in mokee is the kernel and the proprietary files because the graphics update killed signal on cm-11 so the recovery should be fine and ill test as soon as you have a build ready
[Android Software Development] chraso:
Thanks for reply and your quick effort.

1 more thing I would like you to know is our phone has diagonal pad with 5 buttons for navigation.

Can we compile it fully functional other then touch function with your permission?
[Android Software Development] Bhargav97:
Yes...we have enough hardkeys (total 13, counting 5 for one d-pad) and even without touch it'll be all fine. Can we fully compile with your resources included, if you permit?

You can see this image below:-
[Android Software Development] drraptor:
Tried to flash Philz touch recovery on i9500 downloaded from this link http://xdaforums.com/showthread.php?t=2280457

get this error.

"E:failed to verify whole-file signature"
[Android Software Development] Phil3759:
Sure you can

It is on github for that

Would be great if you can link me to all needed patches to compile it under cm11 repo as it seems to have dropped armv6 support
[Android Software Development] Bhargav97:
Okay...I am trying to get those patches asap. And...about which source you saying at Github? I was asking about GUI options (themes and all that).

EDIT: Can you please tell me a bit in detail about the patches that you need? Thanks in advance...

EDIT: Will you get any help from here:-

https://github.com/androidarmv6/android_kernel_samsung_msm7x27

Sorry...but I haven't actually understood what you want.
[Android Software Development] chraso:
thanks bhargav

he may need this also

https://github.com/androidarmv6/android_device_samsung_galaxy5
[Android Software Development] Bhargav97:
Thanks for this.
[Android Software Development] Ripshock:
Is it possible to support an official philz touch cmw for sm-t210/r? If yes how can i help?

Sent from my SM-T210(R)ocketTab 3.1 $up€R_f@$T
[Android Software Development] Isuru cs:
i 'm noob to samsung mobiles, i want to know all newer version for s3 include the "SDS Patch"????? plz tell me :confused:
[Android Software Development] Bhargav97:
It's all mentioned in posts by OP. Read all the posts on the first page. Your answer is in post #2.

[MENTION=5018993]Isuru cs[/MENTION],

Read the first post on first page.
[Android Software Development] Ripshock:
The bad thing sadly cm does not support my device :(

Sent from my SM-T210(R)ocketTab 3.1 $up€R_f@$T
[Android Software Development] Phil3759:
It is easy: try to start on a clean cm repo, sync your device to the androidarmv6 git

Now try to compile

You will understand what i mean. Merging device/device-common/kernel/vendor and other dependancies is not enough. He probably added changes to build/core or else...
[Android Software Development] Bhargav97:
We have already compiled a recovery from your philz_touch source at Github. Everything is working perfect. Just missing GUI options and mainly TOUCH.

The actual work you'll have to do:-

This device is not built using the CyanogenMod source. The

device uses the androidarmv6 source,

which is a heavily modified fork of the

CyanogenMod source. You'll have to download the whole androidarmv6 repository and adapt your own private code to it.

I know this procedure is time-taking and painful but once you do this, it will be helpful for all the armv6 devices. And, you can then make philZ recovery for all armv6 devices (there are many...listed below currently active devices dependant on androidarmv6 source) and you can expand spread of your recovery. A huge number of members will be added in the list of people using your recovery. :)

List of armv6 devices that'll be benefited mainly (it will even help other armv6 devices than listed below)

-galaxy5

-p500

-p505

-p506

-p509

-beni

-skate

-tass

-gio

-cooper

-callisto

-u8150

Are you up for it?

Thanks...
[Android Software Development] Phil3759:
That's what I was suspecting

Sadly, I have no time or local resources for that

Wait for upcoming redistributable libtouch that hopefully would work cross plateform
[Android Software Development] Phil3759:
Galaxy S2 Epic 4G Touch - SPH-D710 (d710)
[Android Software Development] Bhargav97:
Okay...Thanks. I'm excited to see the libtouch. Just a question, Will that libtouch include all GUI & Clone to update.zip (In short a full version) too?

"redstributable" means you're kind of making your touch & GUI options Open source?
[Android Software Development] cooldudezach:
Took me long enough to get back here! I updated the repo for the ZTE Awe (Previously requested here by me, needed some minor work, all done now).

Repo: https://github.com/zte8930/android_device_zte_nex/tree/cm-11.0

No changes are needed, should build just fine from cm11 source.

I do have one question regarding a unified device tree. The ZTE msm8930-based devices are all similar enough to use the same(ish) boardconfig, but they currently require different kernels. How would I go about unifying the device tree for a universal ZTE msm8930-based recovery? Only one of the devices (so far) requires any changes to the boardconfig, due to it has an actual partition for the internal sd, rather than a /data/media one. Would I first need to get the kernel to work cross-device? (On my to-do list. woo)

edit: another question you may or may not be able to help with. On some of the zte-msm8930 devices, while in cwm/philz, the screen will jitter back and forth when the screen updates (scrolling through menus, changing screens, updating progress bar, etc). By jitter, I mean the screen will alternate to looking fine, and then being offset by half (but the half that goes offscreen is just on the other side of the screen instead.) it's very jarring, especially when installing something. I presume it's a framebuffer issue, but haven't had much luck fixing it. I did so on one, by changing the pixel_format, but that hasn't worked on the others. Any ideas?
[Android Software Development] jetx2x:
hello there... looking to get official support for the zte warp sequent... my device tree may be found here

https://github.com/jetx2x/cm_android_device_warp2/tree/PhilZ

your non touch recovery is fully functional

http://androidforums.com/warp-seque...y-6-12-8-non-touch-recovery-touch-coming-soon.
[Android Software Development] Phil3759:
closed source parts are what is retail/commercial in CWM by Koush

I do not plan to compete his commercial products

The lib will be pre-compiled and included in the repo, not its sources though, at least for now

Yes, all is done at the init binary level, so you need a common kernel

If the kernels are so different, you'd better stick to separate device trees. Else, every bootloader / kernel update to a device could get you in huge maintenance work

About graphics, you probably need to fix your graphics.c first by disabling double buffer maybe or enabling the BoardConfig flag for the fb_blank

There are many graphics.c in some devices to avoid using double buffer

Let me know when you fix it please as it is useless to compile a recovery with broken graphics

will add to my todo list
[Android Software Development] aosp:
[MENTION=4666971]Phil3759[/MENTION]

Thanks
[Android Software Development] Bhargav97:
Hi phil3759,

I just want to ask you...in about how much time approx. would you be releasing your libtouch re-distributable. Sorry...I know the forum rules and not asking about ETAs but I'm excited to see it, hope you can understand my feelings. I am missing the extremely useful features...I know that you've got too many device requests and you have your personal life, so nothing is definite but atleast you can just give me a rough idea...like - 1 month, 6 months, 1 year...like that if possible.

Thanks & Regards...
[Android Software Development] gr8nole:
Phil,

I see you have a few requests for support on the Samsung Galaxy Tab 3 7inch version (SM-T210 & T210R).

I made an unofficial port of version 5 a few months ago with the help of [MENTION=4021423]ketut.kumajaya[/MENTION] and he continues to maintain kernel source for this model.

We do not have a complete device tree for building CM11 yet, but we do have enough to build a fully working recovery. I have compiled the non-touch version of your Advanced CWM 6 and it works great.

Please consider building an official version for us when you get a chance. Thank you.

Device source

https://github.com/gr8nole/android_device_samsung_lt02wifi

Kernel source

https://github.com/kumajaya/android_kernel_samsung_lt02

Module source (if necessary)

https://github.com/kumajaya/android_kernel_samsung_lt02_modules
[Android Software Development] HippoMan:
Printing a "Done" message in the log?

Would it be possible in a future release to print some sort of "Done" message in the log after flashes and other similar operations complete?

After flashing a ROM just now via 6.15.4, the last message showing in the log is this:

Creating Symlinks...

I'm pretty sure that the flash finished OK, because there is no error message and the menu redisplays, and I've never had a post-flash problem in cases like this. However, the lack of a "Done" or "Success" or other similar message in the log always leaves me with an uneasy feeling that the flash might not actually have completed properly.

Of course this is a very minor issue and there is certainly no urgency. It's just something that I'd like to suggest for your (undoubtably long) list of feature requests for a future release.

Thank you very much.

.​
[Android Software Development] Phil3759:
There is an option to prompt you after install and pause in full screen. Other blah blah must be added by your rom cooker not recovery

Sure, will do
[Android Software Development] HippoMan:
Thank you, but I already have "Pause on Logs" enabled. The final message showing up in the log after flashing that ROM is still Creating Symlinks...

There are hundreds of ROMs out there, and each one may or may not print some sort of "Success" message as part of their installation scripts. On the other hand, there is only one PhilZ recovery to use with all of these ROMs, and IMHO, it would be desirable in a future release if it printed a simple "Done" or something similar in the log, after an installation completes.

.​
[Android Software Development] Bhargav97:
Hello phil3759,

You should correct it up...

In the post #5 (Changelog post), you've written version 6.15.3 and here in discussion you've written 6.15.4. Changelogs are same for both. Which one is true? I think 6.15.4 is...
[Android Software Development] Bhaskara Rao:
Please provide me link to Philz Touch Blackhawk's Repack Recovery for Dual Booting with Blackhawk's Kernel. I could not find it.
[Android Software Development] Phil3759:
If it fails, you will get a clear message with dead droid background icon

For me, it is enough. I see no reason to say that the script reached its end when you got your menus back. We could add a ringer though, if we get sound once in recovery :D and no, I am not joking here ;)
[Android Software Development] Phil3759:
I am already on 6.16.0 and many devices on 6.15.7

Most are non relevant changes any mainly device porting or small maintenance
[Android Software Development] HippoMan:
OK. I'll offer one last argument, and then I'll give up. :)

If I successfully install a zip from the sdcard or exit from aromafm, I get this message:

Install from sdcard complete

Why print that message at all, given that I am returned to the menu and no dead droid background shows up?

However, after a successful sideload I get no message. I forgot to mention that the install I referred to in my earlier post (the install that ended with Creating Symlinks...) was performed via sideload. I sincerely apologize for not making that clear before.

.​
[Android Software Development] Phil3759:
If you mention things at half, then do not expect me to understand :)

I see better now. It's only affecting sideload, not install zip from menu, that's it?
[Android Software Development] Phil3759:
delete
[Android Software Development] HippoMan:
Yes, I only mentioned by half, and again, I apologize. I habitually do all my installs via sideload these days, and I forgot to be clear about that.

Yes, it seems to only be the case with sideload, although I haven't tested all possible cases besides the ones I mentioned.

.​
[Android Software Development] Phil3759:
I will add it
[Android Software Development] HippoMan:
Thank you very much!

.​
[Android Software Development] cooldudezach:
Actually, the repo for the device i posted doesn't have the graphic glitch. It affects some of the others, but not mine :D (because I did find a fix for it.) So it is all ready to go!

Would you be able to point me to a device that has a graphics.c with disabled double buffer? I'll be looking regardless.

And I actually build the kernels from the same kernel source, just with different configs. I will be working on unifying the code at some point in the near future. That's good to know, so I need to hold off on a single device tree for now.

Thanks for your help with this!
[Android Software Development] Phil3759:
- New: Galaxy Tab 3 7.0: SM-T210 WiFi (lt02wifi), credits to [MENTION=3034891]gr8nole[/MENTION] and [MENTION=4021423]ketut.kumajaya[/MENTION]

- New: Warp Sequent - N861 (warp2), credits to [MENTION=4700072]jetx2x[/MENTION]

Note:

ZTE:

Tab 3 7.0:
[Android Software Development] Phil3759:
Ah, I see

Will look at it then

Check PM in a minutes for graphics.c
[Android Software Development] Phil3759:
About v6.16.0

It wasn't supposed to be released. It includes a huge rework of recovery settings.

It is an intermediate code to implement external touch lib and to commit the recovery settings code to CyanogenMod official gerrit for stock CWM

If some bugs are spotted, let me know
[Android Software Development] Phil3759:
- New: Awe (nex), credits to [MENTION=5635553]cooldudezach[/MENTION]

check PM

I also did a few changes to fstab

Let me know if they work
[Android Software Development] cooldudezach:
First try, no they didn't. Had to tinker with it.

Notes:

1. The path for sdcard1(external_sd) has to be "/devices/platform/msm_sdcc.3/mmc_host"

2. For WHATEVER reason, vold(minivold?) looks for fstab.qcom in the "/", which it obviously doesn't find. Without it seeing fstab.qcom, it doesn't give any entries to use the external sd card. (Or rather, anything that is marked as voldmanaged) I have a custom init.rc I use that's in the repo, which adds a symlink to /fstab.qcom from /etc/recovery.fstab "symlink /etc/recovery.fstab /fstab.qcom" I put it just below the "# Fuse public mount points." section in the init.rc. Is there a better way to do this?

After making those 2 changes, it works great! Question: What is the point of the 2 entries in extra.fstab? :confused:

Thanks!
[Android Software Development] Bhargav97:
Thanks...Will try out and report. Is this version merged in your Source at Github?
[Android Software Development] Phil3759:
My current version works or i need to repack?

extra is to provode blkdevice2

No, ugly code...
[Android Software Development] cooldudezach:
It just needs a repack with those changes.

Edit: I found why it didn't build with the custom init.rc file. I have it pointing to another device's custom init.rc. oops. I'll fix that tomorrow after work. A repack is all that's needed though, no rebuild. Thanks for the help you've given!
[Android Software Development] Phil3759:
Can you fix the github repo so that i can maintain proper updates on goo.im in the future?
[Android Software Development] cooldudezach:
Yeah. I'll do it when I get off work later today.

Do you know why vold is wanting fstab.qcom in "/" rather than using "/etc/recovery.fstab"?

Edit: also, how do I add the support for the extra.fstab in the repo?
[Android Software Development] Phil3759:
Recovery uses recovery.fstab only

You can add extra.fstab in product_copy_files flag or hack Makefile in build/core

Read op about extra.fstab but it is optional
[Android Software Development] the_original_teknikl:
i have a question...

is there a problem with this recovery not being able to find and wipe dalvik cache?

i have went thru every version for the d2spr and everyone of the give me an error cant find path to sd-ext when i try to wipe dalvik cache...

is there i setting that needs changed?

i am on virgin mobile btw... same hardware and specs as sprint... if that makes a difference....

any help would be greatly appreciated.

EDIT: After playing with the settings, i discovered i have to MOUNT system in the mounts section BEFORE trying to wipe dalvik.... then it finds and wipes it.... not mounting system just gives a CANT FIND error and wont wipe... make sure to mount system before wiping dalvik.... never had to do this with other phones and recoveries it was all automatic... small but might help others to know this info... if i missed it in a previous post then my apologies please remove this post.
[Android Software Development] jtash01:
Can PhilZ be used to install a stock rom and unroot?

Can Philz be used to reinstall a stock firmware to replace a rooted rom? Or do I need to reinstall the stock recovery then reinstall the stock firmware? If I need to replace both, which should be installed first, the recovery then the stock firmware?
[Android Software Development] Bhargav97:
Which device do you owe?
[Android Software Development] Isuru cs:
Noob question ,new philz cwm update support jb 4.3?

Device-SGS3
[Android Software Development] Yeti47:
Yep
[Android Software Development] cooldudezach:
That's the issue though. If the fstab.qcom is not there, then vold refuses to mount anything. It's like vold is looking for fstab.qcom and recovery is looking for recovery.fstab. That's why I have to have a symlink in the init.rc file so that vold thinks the fstab.qcom is there.

Anyway, the repo has been cleaned up and fixed. It's all ready to go!

I changed it so that it's got a custom lunch entry as "zte_nex-eng". In the process, it should also fix the assert value failing because the device name was "cm_nex" not "zte_nex" (which is what it's set as now) :)

Also, added the extra.fstab to the repo, and everything builds great.

Thanks Again!
[Android Software Development] jtash01:
SPH-L720 (Sprint Galaxy S4)
[Android Software Development] Phil3759:
Because you are confusing everything

sd-ext is a dedicated partition

It is not an error but a notification
[Android Software Development] the_original_teknikl:
It says error cant find dalvik.... error means error. Have to mount system to wipe dalvik is all I was tryimg to convey.

Only confusing part is why does the recovery try to wipe dalvik in sd_ex if its in the system partition....

if I don't mount system and wipe dalvik I get an error and when I reboot my dalvik is still there... if I mount them wipe and reboot it'll rebuild dalvik because it got wiped that time. ..

Mounting the system when clicking wipe dalvik should be done automatically when selecting that option... not go in one menu and mount then go in another menu and wipe then go to a third to reboot. ... should mount automatically or give a notification that it needs to be mounted manually before wiping...

Other than that this is s great recovery ad is the only one that will install wicked sensations on my virgin mobile gs3..
[Android Software Development] indianx:
Hi,

i tried to find a solution for this problem for weeks now. Apparently there is no official cwm 6.0.4.5 for the d801 and PhilZ latest cwm does not automatically flash the cyanogenmod nightly updates.

I always have to reboot manually into recovery and manually flash it.

Do i miss something in PhilZ setting?

Is there an offical cwm and a touch version for the d801?
[Android Software Development] Phil3759:
To which branch should I sync, master or cm-11.0?

Using standard branch names can make life easier ;)

edit: ok, I used master as it is latest and updated to ZTE Awe (nex) 6.16.3

Let me know if you have issues
[Android Software Development] cooldudezach:
Thanks, I will test it out.

What do you mean by standard branch names? I only started really using github a few months ago, so I've been going with what the other devs I work with named it. :) Anyway, both branches are the same. We haven't done much with cm-11, so it's kinda just sitting there.
[Android Software Development] Ali6049:
Hey guys.Can i flash this on jb 4.1.2?
[Android Software Development] Bhargav97:
Yeah...you can flash on jb 4.1.2 but atleast say which device you have?
[Android Software Development] Ali6049:
I have i9300.
[Android Software Development] Bhargav97:
Yes, it would work on Jellybean 4.1.2.
[Android Software Development] nrage23:
Any chance someone could build this recovery for the Galaxy Tab Pro 8.4? It now has root thanks to Chainfire. Here is the stock recovery and boot.

https://www.dropbox.com/s/8vn58u6tsl61aqj/recovery.img

https://www.dropbox.com/s/kucpq4i9mdzykjk/boot.img
[Android Software Development] Bhargav97:
You need to provide full device tree under cm-11.0 branch (if it exists).
[Android Software Development] nrage23:
It does not exist yet. I will just get TWRP working first then. Thanks for the response.
[Android Software Development] Phil3759:
LoL

This is really no sense

To get TWRP to work you first must get CWM to work, at least ideally

If you get CWM to work, you have PhilZ Touch done
[Android Software Development] Bhargav97:
Sadly, that's not the case with my device right now... :(
[Android Software Development] nrage23:
I have given the boot and recovery to the guys with TWRP. They used that and got it working for the Note 2014.
[Android Software Development] Phil3759:
I see

Sadly, I have no more time to repack from stock images as I was doing when I was only supporting 10-15 devices
[Android Software Development] Phil3759:
- HTC Rezound (vigor), thanks to Snuzzo for providing sources
[Android Software Development] ValenteL:
Hi [MENTION=4666971]Phil3759[/MENTION]

What You need to have a PhilZ Recovery to Note Pro 12.2" P900 wifi and P905 LTE?

Attached the Stock Recovery's + boot.img's.

Thank You
[Android Software Development] Bhargav97:
Your device is newly launched. So, your device may not have a tree in cm-11.0 branch yet. Wait for the developers of your device to do this. And...if there exists a device tree in cm-11.0 branch at Github then just provide that here.
[Android Software Development] DavidFlory:
Is the plan to move to a single version HLTE for all Note 3 versions or to keep the individual releases such as HLTEVZW?
[Android Software Development] Phil3759:
It is more complicated for hlte. Some variants have the new bootloader while others are on old. Let me know when they all have a new bootloader or when stock cwm is compatible with new bootloader. I would then build on common hlte
[Android Software Development] ValenteL:
Hi [MENTION=4666971]Phil3759[/MENTION]

What your opinion about my post #2717?

Thank You

---------- Post added at 10:00 AM ---------- Previous post was at 09:45 AM ----------

I don't understand what You say. cm-11.0??? I don't use customers Rom's, only stock.