yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] Martini293:
Which PhilZ kernel should I use for ParanoidAndroid (Utacka) ? I have been using HydraCore and everything is quite simple there but here are 11 different files for 3.1 kernel and I'm little bit confused???

Thank you all.
[Galaxy Note GT-N7000 Android Development] shoey63:
Philz kernels are for Touchwiz based ICS and JB ROMs only. Not for AOKP, AOSP, CM9, CM10 based ROMS. Why not flash an LS7 ROM and enjoy Philz kernel and recovery?
[Galaxy Note GT-N7000 Android Development] Martini293:
Thanks for the answer, I enjoy tablet mode because its easier to navigate on such a big screen (tougher to reach status bar up there with a thumb).
[Galaxy Note GT-N7000 Android Development] iakovl:
is there a way to use the recovery on CM10?
[Galaxy Note GT-N7000 Android Development] Phil3759:
It should work smooth, if you repack their kernel with my binary and depending files

It is not hard to do, but I am busy with cleaning code source for publishing in github and migrate to multi-device easier code setup

Once done, I could look at things like that or anyone could easily compile it from source and get a cm10 kernel with my recovery

However, touch source will not be published as I do not intend to compete in anyway with ROM Manager. You will be able to build my recovery from source with all its functions except touch gui

The cleaning part to make base code public takes a bit of time as my code was first intended for galaxys2 common devices only and without publishing to github in first mind

Actual advance status:

- multi device support finished for i9100, n7000, n7100, i9300 and P5100

- still moving touch source outside of main code
[Galaxy Note GT-N7000 Android Development] iakovl:
your touch gui is the reason i want to use the recovery

while i do understand your point in not releasing the source, any chance you could help and and it to another kernel?

the hydra kernel is a fit for all roms and your recovery would add a lot to it in my view

while i know im asking a bit much but i would love to see the recovery on other kernel and not just stock as i use AOSP based roms and not SAMY roms
[Galaxy Note GT-N7000 Android Development] SandeepEmekar:
Battery life is low compared to SpeedMod.

And more black clipping in videos than SpeedMod.
[Galaxy Note GT-N7000 Android Development] dr.ketan:
http://xdaforums.com/showpost.php?p=31914373&postcount=6
[Galaxy Note GT-N7000 Android Development] Phil3759:
Please, never compare this to custom kernels. It is a STOCK kernel. No battery features will ever be added. This is only for people looking at stock kernels.
[Galaxy Note GT-N7000 Android Development] rraaka:
Phil, the OP shows how much work has gone into the project and we really appreciate your contribution to our community. I hope you will stay :)

This kernel truly deserved a thread of its own in the development section, so am happy its here.

Ive collected the files I need and will be testing soon. I dont really need to. Doc's word is enough for me.

Just got onto a new custom rom and a bit shaky so dont want to confuse my experiences right now.

thanks again

all i can say

my search is over, I have found love :)
[Galaxy Note GT-N7000 Android Development] vfusion393:
@philz

Just a small question on CWM Manager,

The backup is always stored in the Internal Card, even if I selected to save at Ext Card (also tried Int Card) and also not in tar format ?
[Galaxy Note GT-N7000 Android Development] dr.ketan:
I have created backup with first option

-Backup and restore

-backup (first option)

And it saved to Ext Sd card
[Galaxy Note GT-N7000 Android Development] vfusion393:
My existing (first) backup is still in Ext Card and in tar format (selected as default).

Thanks.
[Galaxy Note GT-N7000 Android Development] dr.ketan:
Then i don't get your question, you said it always stores int SD card.

You mean subsequently backup have issue?
[Galaxy Note GT-N7000 Android Development] shantanubarik:
Same to me. Back up stored in Ext Sd card. No issue.
[Galaxy Note GT-N7000 Android Development] vfusion393:
Yes.

Anyway, I will try to delete all existing backups later with CWMR and try CWM Manager again.

Will do this later:

1] CWMR - select EXT Card & Tar as default. Make 1st backup.

2] CWM Manager - will select Ext to make a subsequent backup. Just to see where the back up is stored.
[Galaxy Note GT-N7000 Android Development] Phil3759:
If CWMManager saves in internal sd instead of external, you are probably affected by the "no marker" found on sdcard issue. In CWM6, you will see that error in the on screen log at start. If you are affected, even using original cf-root kernel will not fix it. I never saw a definite solution. Google the cwm6 error log and you will find a few posts with that issue and no fix. Maybe reformatting sdcard to fat32 would fix, but not sure. CF could help probably if you post in his thread after confirming the issue on its kernel

Please give a feedback to confirm the no marker error i supposed, and if you manage to fix it
[Galaxy Note GT-N7000 Android Development] vfusion393:
Results:

CWMR: 1st backup stored at Ext Card in tar format (as selected). Good no problem.

CWM Manager: 2nd backup stored in Int Card in dup format, even if I selected Ext Card in CWM Mgr. Will try another backup by selecting Int Card in CWM Mgr. (reverse order to see if the backup is stored at Ext Card).

BTW, I was on CF-Root LRG before changing to your kernel and did not faced any problem with CWM Manager, i.e backups will be stored at Ext if selected at CWM Mgr.

Will also look for 'no marker' later in CWMR. Thanks.
[Galaxy Note GT-N7000 Android Development] spacetaxi:
I'm using MO 3.30. I wasn't aware of the problems some people are reporting.
[Galaxy Note GT-N7000 Android Development] vfusion393:
Results:

CWM Manager (for the above test):

The subsequent backup by CWM Mgr is stored in the Internal Card in dup format, i.e the selection of Ext / Int at CWM Mgr has no effects. No Go.

------------------------

CWM Recovery:

Subsequent backups is stored at External Card. Good !

Hence, CWM Manager is pointless for me if it is unable to store backups at the external card.
[Galaxy Note GT-N7000 Android Development] Phil3759:
The no marker error shows in cwmr when cwmmanager restarts for a backup job in ext sd. I am sure it is the issue. Nothing related to my kernel. I have it also on cf-root kernel on a second phone. Many have it on other kernels...

Let you confirm the marker error and i will try to investigate it
[Galaxy Note GT-N7000 Android Development] vfusion393:
Edited my post above:

CWM Recovery:

Subsequent backups is stored at External Card. Good !

Hence, CWM Manager is pointless for me if it is unable to store backups at the external card.

No big deal, will remove it and use the CWM recovery from your kernel. Thanks.

--------------------------------

Yes, during backup with CWM Manager, the 'no marker' was seen at the displayed log.
[Galaxy Note GT-N7000 Android Development] Phil3759:
Thanks for the confirmation. I will try to investigate it. Why it happens on some systems and not others...
[Galaxy Note GT-N7000 Android Development] vfusion393:
Thanks Phil.

Questions, please advise the best method to remove CWM Manager:

1/ By using the phone's Application Manager or ?

2/ Reflash the kernel again with Mobile Odin ?

BTW, can I reformat (fat32) the ext. card with Windows and then copy all my data & folders back to the phone from PC ? Will this solve the CWM Manager's issue?

------------------------------------------------------

Edit:

i removed CWM Mgr from the phone with Root Uninstaller. Lets put this matter to rest.

Thanks again.
[Galaxy Note GT-N7000 Android Development] rraaka:
just flashed XXLRT

first things first

in about phone i wish i could make out which kernel i am on

you know ...something like the name on the downloaded file , LRT or LR9

right now it looks so simillar to cf root kernel

i could get pretty confused since im always changing kernels :o
[Galaxy Note GT-N7000 Android Development] kenshinjar:
Hi Phil,thanks for you hard work, so,

Can I use this kernel to flash another Rom from ICS, (ex: ICS to custom ISC, CM10, CM9...)?

I want to be sure :D

wait for ur reply
[Galaxy Note GT-N7000 Android Development] Phil3759:
You can ask Hydracore to add my touch recovery too...

But I know he doesn't like touch... However, my new touch code is really much more mature and stable. Errors are really very hard while scrolling (I never could induce one despite vicious scrolling gestures).

So, ask him to look at it again maybe he changes his mind.

If I have time later, once done with new devices, I would look at CM10/AOKP kernels (please remind me by a request in few weeks)

Also, if hydracore author allows it, I could look at his kernel

Keep in mind also that my recovery currently doesn't support multi-boot
[Galaxy Note GT-N7000 Android Development] xasd:
PHIL,Could you please make Root safe kernel I9220ZCLS2 ? THX....

https://docs.google.com/open?id=0B3I03eeRFNtENFdWT0phMDJ5NVk
[Galaxy Note GT-N7000 Android Development] shoey63:
Hi Phil. You know those old full touch recoveries I showed you? Turns out they behave exactly the same way as Cwm-touch-6.0.1.2-i19100.zip. Interesting yes?

(Except 6.0.1.2 has "wipe via secure discard supressed")
[Galaxy Note GT-N7000 Android Development] Phil3759:
If they are the same then it could be they were not compiled from a personal source, but just done with Koush Builder or from ROM Manager

Anyway, if you have a link to source code I am interested. But, it will be of a limited interest as ROM Manager touch versions are also affected by these "by error validations" when you scroll

I optimized a bit more the touch code. Now, double tap validation and direct touch validation should be more reliable (not missing action so easily) but still as safe as before. On i9100 is less visible, but I imagine on the n7000, from time to time, when you want to double tap to select you have to really stable and steady
[Galaxy Note GT-N7000 Android Development] shoey63:
Interest is curiosity value only. Your new recovery makes it pale into insignificance.
[Galaxy Note GT-N7000 Android Development] weixiang80:
hi Phil.... i got stuck at unmounting system, able to help?

thanks....

i flashed to TMT 5.0 and has Philz 3.1 on my phone but i dun have the root (SuperSU says no binary found)
[Galaxy Note GT-N7000 Android Development] axeman007:
Do I need to use an External SD card (Micro SD) , in order to flash this kernel? Could I do away with my internal storage (/sdcard) ?
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
if using stock recovery the yes. else if using mobile odin or cwm then no
[Galaxy Note GT-N7000 Android Development] giri@xda:
Installing Philz kernel

I am on stock 4.0.4 running XXLRK. I have downloaded "PhilZ-cwm6-XXLRK-XEU-3.1-signed.zip".

Should I be taking any additional precaution other than backing up my apps, wiping data / cache in recovery after installing the ROM ? ( Of course keeping fingers crossed till phone boots up properly :p !!!! )
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
installing kernel will not alter any data or apps. so there is no need for backups.

There is no need to wipe data and cache too
[Galaxy Note GT-N7000 Android Development] giri@xda:
Thanks for your reply. I will go ahead & save my phone from EMMc brickbug with the hope that it has not hit my phone already. ;)
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
if you had been non rooted till now, and not done any wipes, they you should be fine. after installing this kernel you will auto root. then install ktool from play store and backup your efs before doing anything else.
[Galaxy Note GT-N7000 Android Development] giri@xda:
I was rooted earlier, but did not do any wipe earlier. After installing update .zip from stock recovery, it still shows me the old kernel version. Did I miss something ?
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
installing the philz kernel will not change anything in the kernel section as it's a stock kernel. easiest way is to boot into recovery and you will see cwm 6.0.1.5 philz. or use terminal emulator and use the commands

su

get prop

[customkernel.base.PhilZ-cwm6]: [true]

[customkernel.namedisplay]: [PhilZ-cwm6]
[Galaxy Note GT-N7000 Android Development] giri@xda:
Booted into recovery and got a feel of cwm 6.0.1.5 philz - fabulous. However, the editor commands did not work - never mind.

Thanks again.
[Galaxy Note GT-N7000 Android Development] jasonkhoo87:
can it be added any other governer like pegasus?
[Galaxy Note GT-N7000 Android Development] :
This is a stock based kernel. You will not see additional governors.

This has been asked many times, please search.
[Galaxy Note GT-N7000 Android Development] rcaballero:
I cant find if this was asked already. how do i access the external sdcard in cwm?
[Galaxy Note GT-N7000 Android Development] :
Are you on ls7?
[Galaxy Note GT-N7000 Android Development] rraaka:
just for feedback sake Phill, with Rocket Rom v3 with your ls7 kernel we get CWM app in app drawer and people said its working well. I was under the impression after initial releases you stopped including it in your kernels.....just confused ....
[Galaxy Note GT-N7000 Android Development] Phil3759:
You can backup EFS under cwm6/philz settings menu

should be getprop in one word

You mentioned it yourself, blame Rocket Rom v3 for that. The CWM app came probably with their ROM. Chainfire doesn't allow redistribution of his app

I include goomanager support. You should give it a try
[Galaxy Note GT-N7000 Android Development] rcaballero:
Yes im on ls7
[Galaxy Note GT-N7000 Android Development] shoey63:
@rcaballero Install ZIP/Choose ZIP from SD card
[Galaxy Note GT-N7000 Android Development] msedek:
Dude could you do this:

Voodoo LOUDER driver configuration troubleshoot:

Solution 1: switch to a kernel already fully supporting LOUDER

See*a list of kernels here.Solution 2: help kernel authorIts likely kernel author build LOUDER driver but couldn’t test it.In most case errors have a single cause, kernels are built without some standard required options.For the kernel developer, the fix is as easy as:Enable*KALLSYMSEnable*DEBUG_KERNELEnable*KALLSYMS_ALL*(auto checked with 2 previous options)Those 3 config options are enabled in every Samsung build.Kernel must also not disable*debugfs*support (and have really no reason to).If kernel is missing debugsfs, LOUDER will tell you “Unable to find ASoC codec_reg interface”I recommend you to contact them with this documentation. I also can help kernel authors directly.Those options are available in menuconfig (search with the “/” key)It also correspond to CONFIG_KALLSYMS=y and CONFIG_KALLSYMS_ALL=y

If possible to the xls2 and xls7 kernels? I want to use my voodoo Louder and I'm not able to because of that and that's what supercurio suggested... Thanks in advance

I'm getting the

“Unable to find ASoC codec_reg interface” and that's the final step in order to activate the plug in

Tapatalking on my n7000
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
yeah. I know.. blaming this SwiftKey
[Galaxy Note GT-N7000 Android Development] Phil3759:
same thing here. No way to stop inserting these white spaces when ever it likes...
[Galaxy Note GT-N7000 Android Development] tbong777:
Wondering why ext SD Card does not mount in recovery. Is this by design or do I need to reflash. something. I recently cleared out my entire phone of all files and reformatted everything , flashed RR v3 and installed apps one by one from the market. Pretty clean install.

I don't remember not having access to the external SD card in recovery. I have flashed zip files from there before.

Thanks
[Galaxy Note GT-N7000 Android Development] Phil3759:
:rolleyes:

Please, remove your long quoting, it clutters the thread... mainly for mobile users

It seems from the feedback it is related to XXLS7.

But in your case you are confusing external_sd and ext-sd... not same thing

Also, you need to give much more info on what you are reporting if you want help
[Galaxy Note GT-N7000 Android Development] Phil3759:
Good news, we got an official JB leak for i9100

Now downloading

Feels like a long night

My githubbing is now paused

dr.ketan got a first n7100 pre-release from the new multi-device code

Damn it samsung, they are going to kill me :D
[Galaxy Note GT-N7000 Android Development] shoey63:
Don't forget to look at Goomanager;)
[Galaxy Note GT-N7000 Android Development] Phil3759:
On i9100 external sd works

Goomanger fix will be done. It is already coded in my brain

But so hot on JB

It is amazingly great

Hey shoey, thank you for the support over n7000. This time, it was the opposite, n7000 ported to i9100. Same changes, so my script was ready :good:

I can now go back to my cwm6

Did a really huge job, code wise in these last few days...

backup / restore script will be more intelligent now, no more issues with int/ext in recovery
[Galaxy Note GT-N7000 Android Development] Phil3759:
Ok, looking at it closer

Goomanager is not JB compatible. It cannot browse new storage location extSdCard

Sadly, no fix is possible until they update it, which is I am not even sure...

Maybe I'll have to make my own app...
[Galaxy Note GT-N7000 Android Development] shoey63:
Actually it doesn't worry me. I quite enjoy spending a little extra time in recovery:)
[Galaxy Note GT-N7000 Android Development] tbong777:
Thanks Phil. Maybe I can make it clearer. When I reboot into recovery mode I can only mount the internal SD Card from recovery.

I can mount both cards when using the USB cable from a PC.

What I cannot do is select a ZIP from my 64GB SD Card or browse the 64GB card within recovery. Only the Phone's SD card is mounted for flashing zips. Even If I go to mounts within recovery it does not all "E: Can't mount /sdcard/" The "internal" SD card can be browsed from recovery. Any additional cards cannot be on my device from within recovery mode

I just was inquiring as to whether this is by design or I am doing something wrong.
[Galaxy Note GT-N7000 Android Development] Phil3759:
It should work

Now, even testing the JB leak for i9100 over my same 3.1 kernel for note, and dual usb mount does work perfectly

Some people fixed it by formatting sdcard on PC...
[Galaxy Note GT-N7000 Android Development] tbong777:
Dual USB mounts for me as well IF I am cabled to a PC. They work great.

If I am only in recovery and no cabled to a PC, I cannot access the 64GB SD External card using recovery menus or mounts.

If I select "Choose Zip from SD Card" I get the E:Can't mount /sdcard

If I try to do a Nandroid back up in Backup and restore selecting the first option generates a "can't mount backup path" error

Forced to backup to internal SD card only

Oh well.... no big. I will just put any zip files and backups on the internal SD card and flash from there.
[Galaxy Note GT-N7000 Android Development] Phil3759:
Issue is not general, sorry. It should work fine. Again, ask in general section. Also, try my temporary pure stock cwm6 in corresponding thread to see if it fixes it (I doubt as mine is stock in that regard). Finally, format your sdcard from pc
[Galaxy Note GT-N7000 Android Development] shoey63:
How do you like the jellybeans Phil? (Or haven't you been out of recovery long enough to explore)? Screenshot is an Easter egg. Have you found it?
[Galaxy Note GT-N7000 Android Development] Phil3759:
:D

I see my day as c++ now...

Only remains ors and aroma to be universal for detecting path

I also added option to flash kernels directly from recovery (useful for temp recovery and phones with dedicated recovery partition)

I am surprised by jb stability for a first leak. It looks like a good daily use rom. Just missing some mods I do like but sure they will be soon available for jb too

Cannot see your pic now sadly. Will look later
[Galaxy Note GT-N7000 Android Development] shoey63:
Obviously any app that seeks to access extSdCard via sdcard/extSdCard will fail miserably. (Goomanager included ). I19100 forums should be full of confused users by now. Aroma and ORS work fine from int. SD though. But who wants to load up internal sd Card with ROMS? Best to leave as clean as possible:eek:
[Galaxy Note GT-N7000 Android Development] Phil3759:
Every thing should work in 3.0 except goomanager in fact. Custom ors should work perfectly too as it relies on cwm mount points

What I am doing now is make it compatible for any phone that cwm support using a more clever approach to detect mount points mainly for efs and kernel backup/flash tasks

Do not worry it will be even more clean and reliable
[Galaxy Note GT-N7000 Android Development] shoey63:
Actually I don't use ORS myself much. I prefer to play around in recovery. But it is in your OP, and needs to be tested right? Please don't think I'm being too criticizing:)
[Galaxy Note GT-N7000 Android Development] Phil3759:
Oh, do not worry

Never thought about that

ORS is a big feature but has a crappy app to manage it: goomanager
[Galaxy Note GT-N7000 Android Development] Phil3759:
PhilZ Touch 3.17

The temporary recovery

So, where's that egg?
[Galaxy Note GT-N7000 Android Development] shoey63:
About phone, tap rapidly until big red jellybean appears, then swipe up and down on it abusively until you get get jellybeans everywhere. Then flick them off the screen

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

New recovery eh? What shall I look for?

---------- Post added at 10:20 PM ---------- Previous post was at 10:10 PM ----------

Flash boot from external. Nice!

---------- Post added at 10:24 PM ---------- Previous post was at 10:20 PM ----------

Oh wow heaps of changes! I will test and report:thumbup:
[Galaxy Note GT-N7000 Android Development] Phil3759:
Funny, nice tip, my children will like it I am sure :laugh:

ICS had such a surprise too?

About recovery, yes, change log is above. Flashing kernels is a small addition. Will be useful for phones with dedicated recovery partition. But, for S2 and Note, the temporary cwm could be useful for that too. You can test any kernel from stock recovery with it.

Major changes are in the code though. Now, I do not have to track different versions for S2 and i9100 or any other phone. One code is enough for them all. Soon on github
[Galaxy Note GT-N7000 Android Development] shoey63:
I assume Dr Ketan knoes about this?
[Galaxy Note GT-N7000 Android Development] kopitalk:
Yep, flying ice cream sandwiches!
[Galaxy Note GT-N7000 Android Development] Phil3759:
he's killing me softly...

So, an open request for any one having a N7100 and that is ready to test my recovery image, send me a PM

Same for S3 and Galaxy Tablet 2 for now
[Galaxy Note GT-N7000 Android Development] Phil3759:
thanks
[Galaxy Note GT-N7000 Android Development] shoey63:
Kernel flashing works great. As does backup facility. Nice job:thumbup:
[Galaxy Note GT-N7000 Android Development] Phil3759:
I am done with github versions to commit in some clear steps. However, have some guests all the day, will look to submit in next days and make a final kernel