yashsingh1/xdaforums huggingface dataset:
[Android Software Development] cvpillai:
aw3som3

If PhilZ Touch can work with aw3som3, it would have been wonderful.
[Android Software Development] yuweng:
[MENTION=4666971]Phil3759[/MENTION], it seems like i'm the only one that tries to build the latest on arm11, it boots up with adb & no GUI, donno how to debug, thanks . . . :o
[Android Software Development] bigmike6200:
Can you add Verizons S3 mini to the list. SM-G730V is the model. Thanks.
[Android Software Development] DSA:
Do you have cm11 for your device?
[Android Software Development] fanistic:
Rom development for the samsung galaxy s has not started up yet besides no CWM for flashing such hence my request for PHILZ
[Android Software Development] danarama:
At the moment, Philz is still built on CWM. You need CM11 / CWM first for Philz to be available for a device.
[Android Software Development] fanistic:
so who is responsible for building of CWM? so i can channel my queries over ther.
[Android Software Development] danarama:
Cyanogen
[Android Software Development] Phil3759:
I am not aware of any arm11 device supported by cyanogenmod!
[Android Software Development] Orphee:
The galaxy tab S tablets have a exynos octo core processor...

I did not see any development on these tablets.

TWRP is available since today on it.
[Android Software Development] Bhargav97:
Well if you (or anyone else) badly need, there are many which are supported under project androidarmv6. They add no custom things in pure cm11, they just do some hacks, patches to make these devices run cm11.

They have their gerrit:

http://review.androidarmv6.org/

They have Jenkins:

http://jenkins.androidarmv6.org/

Github is here:

http://https://github.com/androidarmv6/
[Android Software Development] cvpillai:
PhilZ Touch

I have. The details are CM version 11-20140708-UNOFFICIAL-pico

Android version 4.4.4Kernel 3.0.101 CM.
[Android Software Development] Phil3759:
I did support pico until no kernel devs were interested anymore because they left to other devices

Issue is you need a special very tight selinux enabled kernel to fit recovery partition...
[Android Software Development] yuweng:
Whoops, may i should have stated it more clearly, libtouch on armv6 . . . :o
[Android Software Development] Phil3759:
Since libtouch is open source now, just add tracing log inside code started on boot until you locate the cause and let me know

Also try to replace background during compile time
[Android Software Development] x5c0d3:
Can really noone help me with my goo.im problem? :( All I want is the newest 6.48.4 :(
[Android Software Development] danarama:
You do not say in this post what your problem is. I'm not going to go searching the thread to find your problem.
[Android Software Development] x5c0d3:
In my first post I wrote that goo.im is totally messed up. The files are in no chronological order. I cannot flip pages and see tons of CORS (Cross-Origin Resource Sharing) errors from Cloudfront in my Debug Console. So there is no way for me to grab the newest version of Philz Touch.
[Android Software Development] RK:
1 click on any version on goo.im

2 copy the resulting URL

3 replace the version number in the URL with the latest one

4 be happy

Example, for jflte device you can get to the latest version simply be replacing X.XX.X by the latest version number in the following URL

https://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte/philz_touch_X.XX.X-jflte.zip

Also, this question and this answer does not belong in this thread. Sorry Phil.
[Android Software Development] x5c0d3:
Oh sorry but it does belong here.. because it's a problem with Philz Touch.. not beeing able to get it is a problem. ;)

Thanks for your answer! I will try it out
[Android Software Development] yuweng:
Whoops again, donno much C/C++, only know how to compile & simple debugging . . . :o

Source built no error, boots up with adb but doesn't mount anything . . .

i've try both using prebuilt & the compiled libtouch_gui.a at $OUT -> libtouch_gui_intermediates & replace the one at bootable/recovery/libtouch_gui/armv6 both output the same error . . .

bootable/recovery/recovery.c:1322: error: undefined reference to 'check_recovery_lock'
bootable/recovery/advanced_functions.c:4005: error: undefined reference to 'show_recovery_lock_menu'
external/busybox/debianutils/mktemp.c:96: warning: warning: mktemp() possibly used unsafely; consider using mkstemp()
bootable/recovery/libtouch_gui/gui_settings.c:2346: error: undefined reference to 'ui_increment_frame'
bootable/recovery/libtouch_gui/gui_settings.c:2347: error: undefined reference to 'ui_set_nice'
bootable/recovery/libtouch_gui/gui_settings.c:2347: error: undefined reference to 'ui_set_nice'
bootable/recovery/libtouch_gui/gui_settings.c:2348: error: undefined reference to 'ui_was_niced'
bootable/recovery/libtouch_gui/gui_settings.c:2350: error: undefined reference to 'ui_was_niced'
bootable/recovery/libtouch_gui/gui_settings.c:2351: error: undefined reference to 'ui_delete_line'
bootable/recovery/libtouch_gui/nandroid_gui.c:94: error: undefined reference to 'ui_delete_line'
collect2: error: ld returned 1 exit status
build/core/executable.mk:70: recipe for target '/home/yuweng/v6/out/target/product/MediaTek/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery' failed
make: *** [/home/yuweng/v6/out/target/product/MediaTek/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery] Error 1
[Android Software Development] Phil3759:
are you using latest sources?

By default, libtouch_gui is now compiled. Do not use the prebuilt as I did not update since a while

Does the stock CWM work? If yes, it will be hard to help without device or you knowing some C code :)
[Android Software Development] yuweng:
Just tested CWM, both boots, both latest source, androidarmv6 & cm with v6 bionic . . . :o
[Android Software Development] danarama:
Where did you get the information about the phone having 2 efs partitions?

Use root explorer to confirm.
[Android Software Development] katinatez:
Confirmed using root explorer, check out picture.
[Android Software Development] danarama:
So you need to know the fstype and add Rows to /device/vendor/phone/fstab.phone

I keep track of all my device tree changes in a text file
[Android Software Development] katinatez:
Wow, you are very organized, I will follow your example of organizing code changes.

Is my 2 lines of code correct targeting the efs?

I also noticed the ro.cwm.forbid.format code, is that so users don't format their efs?

Last question is any ideas on screenshots error log?

And Thank you for your help!
[Android Software Development] danarama:
I don't have those lines you mentioned.. All my changes are in the screenshot.

Yes the forbid stops that.

Not sure about screenshot. Did you set f2png as I did at the bottom of my screenshot?
[Android Software Development] katinatez:
No, I have not. Did not know I had to set a true flag.
[Android Software Development] danarama:
Try it.
[Android Software Development] Android-Andi:
[MENTION=4666971]Phil3759[/MENTION] just compiled for p31xx, p51xx and golden PhilZ 6.50.6, should I upload for you too?
[Android Software Development] madcaesar18:
Huge backup size?

I'm having trouble with the recovery. I recently flashed Philz and installed CM 11. All is working fine, but when I go into recovery to create a backup to flash some other stuff, I am presented with a ridiculous sized backup requirement (12000 GB!!). My SD card is almost empty, and my internal drive is 4.8GB free out of 12 GB.

Anyone else having this issue? I tried doing a backup to SD card and internal storage, but both want that 12000 GB for some reason. Picture is attached.

Device: Samsung Galaxy Tab 3 8

[IMG="Huge Size Philz recovery backup"]http://i.imgur.com/cgVNOe5.jpg[/IMG]
[Android Software Development] Phil3759:
What [MENTION=2872010]rootSU[/MENTION] said is ok. Just 2 more things:

1- don't try twrp mount flags in CWM fstab (display= and such...)

2- you do need this line in fact:

PRODUCT_PROPERTY_OVERRIDES += \
ro.telephony.default_network=20 \
ro.cwm.backup_partitions=/modemst1,/modemst2,/devlog

where you set the extra partitions to display in nandroid menu by their MOUNT POINT

Obviously, each added partition must have an entry in device.fstab file

without the environment property properly set, recovery cannot know that some special partitions should be added to your nandroid jobs and will default to base partitions

About fb2png: it is an issue in the kernel using a wired frame buffer node entry. I have same issue on my S2 and didn't find a fix (I didn't have much time to fix it in the kernel or fb2png)

I found golden and put on goo. Please upload the other 2 and let me know

Also, please do not rename your files the way you do. Keep the same formatting I use on goo. Else, I cannot upload any tar or md5 file and I do have to manually rename them to avoid messing third party apps relying on this naming

Also, goo is gonna fix the sorting to be done based on file name. So, I need a rule to increment versions
[Android Software Development] Phil3759:
some people reported it fixed after formatting the /data partition

It is probably caused by too many holes in the file system or some reported it caused by some games installing thousands of 0 size files

Another fix is to just disable teh free size check in Misc Nandroid Settings
[Android Software Development] madcaesar18:
Thank you for the quick reply. I probably can't just go in and format /data partition to see if it fixes it, wouldn't I have to format everything and re flash CM to see if that fixes it? How big should a backup be in general, so I know I have enough space if I disable the size check.
[Android Software Development] Unb0rn:
Encryption support

It looks like the dev is really busy here! Is there any point in asking TWRP-style support for encrypted partitions? Don't want to switch to TWRP from this awesome recovery, so it would be really great! :fingers-crossed:
[Android Software Development] danarama:
I dont recall saying that :/
[Android Software Development] Phil3759:
You didn't. But his fstab code contained those twrp entries

I should have written : "2 more things in addition to what you said"

Edited my post
[Android Software Development] Android-Andi:
Sure, i rename for you every time and modded my *.tar.md5 converting script https://github.com/andi34/android_pull/blob/cm-11.0/odintar.sh#L69 :D :)

Will upload later for you :)

Need to update my script to make a flashable zip also :p
[Android Software Development] Android-Andi:
[MENTION=4666971]Phil3759[/MENTION] here we go:

http://www.androidfilehost.com/?fid=23578570567714432

Includes *.img, flashable *.zip and odin flashable *.tar.md5 for p3100, p3110, p5100, p5110 and golden.
[Android Software Development] danarama:
Ah understood
[Android Software Development] Phil3759:
Will upload when back

many thanks
[Android Software Development] [NUT]:
[MENTION=4666971]Phil3759[/MENTION]

https://github.com/xNUTx/philz_touch_cwm6/commit/f3763b3d9e581b472ea80966a8144e2568c4fb60

I wrote this patch to automatically enable the non time_daemon fixes, but also to improve the brightness path search. It works a treat on sony devices but should work on all philz touch supported devices.

The Xperia ZL has a second brightness control path, that's why I doubled the setter code to include that.

I hope you regard this patch worthy of a merge with the code base :)
[Android Software Development] Phil3759:
:good:

will look at it and let you know
[Android Software Development] [NUT]:
Just make notes in the code on github if you want something to be changed, I'm still learning C/C++ so some things might not be as logical as they could have been :)

I'm even prepared to rebase it on your beta branch if you want as this patch has been made on the latest 'stable' branch.
[Android Software Development] Phil3759:
well since you say it... ;)

I looked quickly and put it on my to "take time with..." list because of the code issues

- Why that new_find_file option? better modify original one so that I can quickly spot what you are trying to achieve

- brightness set to 0 can be an issue with some kernels as the toggle won't make any change on first increments

- are you sure all krait CPUs need time daemon?

- actually, about reading the ats files, there is a huge issue with samsung phones. They do accept some date -s commands from toolbox which makes all this useless. We need to force reset time and date to 1970. I will look at it later when I have time as my S4 is also affected and I can reproduce it

- I will add a small notice inline also

:good:
[Android Software Development] [NUT]:
Will do my best to resolve all and any issues in the code, so you won't have to :good:

- I couldn't find the find_file_in_path function to be honest :o

- Actually, I was considering turning that in to a #ifdef solution. for some Sony models 0 needs to be set to turn the screen backlight completely off (Yuga, Odin)

- Yes, it's part of the krait spec, device manufacturers can of course have deviated from that (like sony did with the since_epoch on the Yuga...)

- Hmmm, well, I don't know about samsung devices, I only know about Sony's devices ... and that means the RTC starts somewhere in 2009 instead of 1970 ... how about that for an epoch: it's the date on which the first ever Android device Sony (-Ericsson) was released/announced ;)

Will fix the issue in the little note you wrote, thanks :)
[Android Software Development] Phil3759:
Very interesting about the RTC. These devices use the offset. But even the offset can fail on Samsung if date was forced using date -s in toolbox

Will closely read your code on that part

About brightness: thanks, I will add it then to the "blank screen function rather"

The find_file function is in advanced_functions.c

You can always use grep command to track functions in sources
[Android Software Development] yuweng:
Found out it was the Cherry picks from AOSP / CM Recovery that bricks arm11, that is the only simple debugging skill i know, git checkout 588dbcf still works . . . :laugh:
[Android Software Development] Phil3759:
sad we cannot debug it a bit more :(
[Android Software Development] yuweng:
Sorry i don't understand, i notice there are indeed quite alot of changes there, just let me know what i have to do & i'll carry on to see which one is the culprit . . . :cowboy:
[Android Software Development] Phil3759:
It is very hard to say without trying to reverse some changes inside that huge commit

mainly those in adb files and recovery.c
[Android Software Development] Phil3759:
Please do not quote code as it is not readable at all

Just post it inside

tags

you forget the trailing \ when adding properties. Never edit make files without properly knowing what you do. Take time to read across the Android.mk guides on google at least

Also, you do not read my answers. I corrected all the other mistakes in your fstab and I see they are still there!

I did not read through the rest of your post as those bugs must be fixed first. After that, please post again with code tags so that I can look at it easier

Read again very closely my previous answer to you
[Android Software Development] danarama:
What is this supposed to do?

/dev/block/platform/msm_sdcc.1/by-name/modemst1 /efs1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modemst2 /efs2 emmc defaults defaults

Would that be more accurate?
[Android Software Development] Phil3759:
He must specify the proper mount points in that case in his properties

Also, in makefile, each line must end with \ except last one when he's adding properties
[Android Software Development] nicklovell23:
Great guide and easy to follow. I compiled for i925, thread can be found here http://teamuscellular.com/Forum/top...dition-philz-touch-6484-i925libtouch-gui-130/
[Android Software Development] beautifulsun:
Edit.
[Android Software Development] danarama:
You can just flash the zip

Wouldn't say fully. Some functions work, but you shouldn't use rom manager anyway. It is much better to do things manually.

---------- Post added at 03:46 PM ---------- Previous post was at 03:46 PM ----------

Hey [MENTION=4666971]Phil3759[/MENTION]0, when you move to AOSP base, will you still support proprietary extendedcommand?
[Android Software Development] beautifulsun:
Thank you.

So no cache/dalvik wipe?
[Android Software Development] danarama:
What are you asking? No cache/dalvik wipe for what? Yes the recovery has menu to wipe cache and dalvik.
[Android Software Development] beautifulsun:
I mean cache/dalvik wipe after update new version of PhilZ and before rebooting.
[Android Software Development] danarama:
No of course not. Cache and dalvik have absolutely nothing to do with recovery. Please google what they are. You should know this stuff
[Android Software Development] davy4475:
Sorry if this is not the right place. I'm on v6.0.4.5 and every time I try to download and install and rom I get an error (bad) install aborted. I tried to update to the latest version v6.10.0_jfltexx.zip but still keep getting the same error. Any ideas, thanks
[Android Software Development] Pons:
If you haven't already, try posting in your device's thread. But also include a full recovery.log when you do.
[Android Software Development] davy4475:
Sorry I'm on s4 GT-I9505 4.4.2 and was told to post here. Sorry I'm a Noob and just looking for a little guidance. Thanks
[Android Software Development] danarama:
This is the development thread. Problems that users have belong in device threads.
[Android Software Development] 2545:
Hello. When making a backup, can I disable MD5 to make the nandroid finish quicker? I assume I'll have to disable it on restore?

Are most of you selecting to perform a standard backup vs custom?
[Android Software Development] Phil3759:
I am keeping CyanogenMod to compile it

Extended commands will be maintained
[Android Software Development] yuweng:
After 3 days of continuous reversing/ reverting for arm11, the more files/ changes i revert, the more new ERROR 1 occurs . . .

And only just now i tried reverting recovery.c only, while keeping other files untouched & Voila, found the culprit . . .

By adding back ui_init(); at Line 1151, arm11 will boot up with GUI, Thank You so much for the tip . . .
[Android Software Development] Phil3759:
:good::good:

Please, can you do the following:

- revert the ui_init() and put it back at line 1197

- edit code as below:

printf("Starting recovery on %s", ctime(&start));

load_volume_table();
printf("--- volume table loaded\n");
setup_data_media(1);
printf("--- media setup\n");
vold_client_start(&v_callbacks, 0);
printf("--- vold started\n");
vold_set_automount(1);
printf("--- vold automount set\n");
setup_legacy_storage_paths();
printf("--- legacy paths done\n");
ensure_path_mounted(LAST_LOG_FILE);
printf("--- cache mounted\n");
rotate_last_logs(10);
printf("--- logs rotated\n");
get_args(&argc, &argv);
printf("--- args parsed\n");

boot and post a log so that I quickly find the culprit
[Android Software Development] yishay:
Hello

I'm sorry to inform that philz_touch_6.48.4-p880.zip for LG Optimus 4x HD and former version don't function.

The only version philz_touch_6.26.6-p880.zip functions well.
[Android Software Development] yuweng:
Fyi, i didn't move the ui_init() but rather add a new one to line 1151 without it, no GUI on arm11 . . . . . . :cowboy:

Hmm, with the additional code, i can't see anything different with the log . . . :o

log 1197 is as comment but no gui so i added back ui_init() to line 1151 & got the log . . .

log 1151, i've added both your commented code to after ui_init() to both line 1197 & 1151 . . .
[Android Software Development] Phil3759:
It is a bit hard to understand what you did!

If you do not add ui_init() at line 1151, do you get a log?

Try to read it in /tmp/recovery.log

If you get a log without adding the extra ui_init(), just do the following and post the log:

Please just keep my sources and edit recovery.c like:

printf("Starting recovery on %s", ctime(&start));

load_volume_table();
printf("--- volume table loaded\n");
setup_data_media(1);
printf("--- media setup\n");
vold_client_start(&v_callbacks, 0);
printf("--- vold started\n");
vold_set_automount(1);
printf("--- vold automount set\n");
setup_legacy_storage_paths();
printf("--- legacy paths done\n");
ensure_path_mounted(LAST_LOG_FILE);
printf("--- cache mounted\n");
rotate_last_logs(10);
printf("--- logs rotated\n");
get_args(&argc, &argv);
printf("--- args parsed\n");
[Android Software Development] yuweng:
Whoops, i didn't know the log is at /tmp/recovery.log but not much info ( done exactly as you said ) :o

__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Sat Jan 1 01:36:29 2011
No /etc/extra.fstab
recovery filesystem table
=========================
0 /boot mtd boot 0
1 /recovery mtd recovery 0
2 /uboot mtd uboot 0
3 /cache yaffs2 cache 0
4 /data yaffs2 userdata 0
5 /system yaffs2 system 0
6 /sd-ext ext2 /dev/block/mmcblk0p2 0
7 /storage/sdcard0 auto /devices/platform/mt6573-sd.0/mmc_host/mmc0 0
8 /tmp ramdisk ramdisk 0
E: invalid device, skipping /etc/fstab entry

E:Error connecting to Vold! (Connection refused)
E:Error in select (Invalid argument)
E:Error connecting to Vold! (Connection refused)
E:Unable to send command to vold!
I:Connected to Vold..
[Android Software Development] Phil3759:
[MENTION=4478781]yuweng[/MENTION]

Please cherry pick this commit and let me know:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/8b92dd017a9bc179632c3fe5702f490a949783eb
[Android Software Development] yuweng:
Compile 2 times with make clean, doesn't fix it . . . :o
[Android Software Development] topcat07:
hi

does a normal backup include efs? or do i need to do a separate custom one thanks
[Android Software Development] Phil3759:
At least I am sure it is not caused by LOGE/ui_print calls after my fix

It could be some changes to armv7 sources still using some calls needing ui_init()

Can you please try this:

printf("Starting recovery on %s", ctime(&start));

load_volume_table();
setup_data_media(1);
//vold_client_start(&v_callbacks, 0);
//vold_set_automount(1);
//setup_legacy_storage_paths();
//ensure_path_mounted(LAST_LOG_FILE);
//rotate_last_logs(10);
get_args(&argc, &argv);

then remove // from one line, compile and start recovery

if it is ok, uncomment another line...

Until you find the exact function causing the issue

After that, I can look at your armv7 sources
[Android Software Development] yuweng:
its vold_client_start(&v_callbacks, 0); . . . :cowboy:
[Android Software Development] Phil3759:
Can you post link to the armv7 cm repos you compile with? Mainly system_vold