yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] vikram66778:
Will somebody Plz care to explain what is the Concept of being Eligible for Posting in Developers Thread only After posting 10 Posts:crying::crying:

I don't understand :confused::confused::confused:

For Example, If i have a doubt about a Rom and want to post in respective Thread, am not allowed to.. Am allowed to post only in General Q & A Section. It is very difficult to get Answer. Some People are kind enough to respond to PM, Otherwise it is hell of a Job to get an Answer.

What is the use of posting 10 posts which are not usefull only to get a Usefull Answer:(:(:(
[General Questions and Answers] Patman99:
I agree.....
[General Questions and Answers] WildfireDEV:
It is to make sure that people don't post anything they want to as soon as the get an account. It is there in an effort to avoid new users from posting wrong threads and questions in the development section. If you want to read more go here

http://www.xda-developers.com/announcements/xdas-10-post-rule/

You said that you have to post useless posts and other things to get to being able to ask questions in the dev threads. Well the 10 post rule was made so that you could contribute to the community in the q and a sections and so forth to get your 10 posts.

Sent from my HTC One
[General Questions and Answers] vikram66778:
Thanks for Clarification. I still see people asking so stupid questions in dev's thread inspite of their coverage extensively in many thread, But they are allowed to post for only they have completed their quota of 10:rolleyes::rolleyes:

And regarding contributing to community, I think am at Kindergarten level in a Hidh School:p:p:p
[General Questions and Answers] vikram66778:
:highfive: For your successfull completion of !0 posts :victory::victory:
[Nokia Lumia 1020] dryspuri:
Hi everyone.

I got this phone for 3 datys now, I have experienced rattle in camera Unit. if you shake the phone u can hear it, is OIS i am hearing, can any one s confirm this please.
[Nokia Lumia 1020] ReiskaSeta:
It's normal. OIS just makes sound.
[Nokia Lumia 1020] Gvr4-330:
Just bought a 1020 as well. Mine came with a piece of paper in the box stating that the OIS system will make a rattling sound when the phone is shaken.

I guess there were quite a few complaints early on.
[Windows Phone 7 Development and Hacking] Phil_123:
I have a HTC Titan running the Dynamics 2.0 ROM.

I was planning to install "Move to cloud" by contable to backup my app data, but my Titan has been acting strange lately, all apps that require interop unlock do work anymore, they crash immediately upon launch. Opening a .xap directly on the Titan does not work. Deploying the .xap with a computer returns an 81030119 error.

Luckily, I installed the FTP server by jessenic a few months ago and it is still working, so I have access to my Titan's filesystem.

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

I would like to backup my WhatsApp data and messaging history, is it possible to back them up just by copying files off my Titan and pasting them back after installing a new ROM? If yes, which files should I backup? For WhatsApp, I found this folder, is backing up this folder enough?

\Applications\Data\218A0EBB-1585-4C7E-A9EC-054CF4569A79\

Alternatively, is there a way to fix the interop unlock issue so I can use other tried and true backup tools?
[HTC Pico (Explorer)] thewisenerd:
So, I've seen many a people talk about boot.imgs, and kernels, and mostly spamming dev threads. So, why not create a new thread for it? ;)

Here, ask your questions related to kernels and boot.imgs, and feel free to post any *improvements* that you've made to an existing boot.img/kernel, and so...

Also, feel free to join the discussion, feature requests, whether or not possible, etc, etc.

This thread might be one whole lot of junk, but still if it helps from keeping people from spamming dev threads, why not :)

So, start!
[HTC Pico (Explorer)] thewisenerd:
Lets start from the basics...

Compiling a kernel is easy, IMO :fingers-crossed:

But, the unpacking repacking stuff is a bit difficult...

Anyways, here's the basics:

Packaging kernel for flashing on target device (by sakindia123): http://xdaforums.com/showpost.php?p=31656992&postcount=3

Packaging kernel for flashing on target device (by #define): http://xdaforums.com/showthread.php?t=2114594 (start from step 6)
[HTC Pico (Explorer)] thewisenerd:
New CM11 Ramdisk changes...

Well, this was taking up a lot of space on the main thread... Read it here :fingers-crossed:

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

edit: some more thoughts...

If you're going to boot this ROM from your SD Card, then, better beware of the new changes in the mounting process... A new fstab.pico is handling the mounting processes..

And, its moved from init.rc to init.pico.rc :|

So, If you're gonna do the editing stuff, you'd find that init.pico.rc has:

on fs
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 mtd@system /system
mount yaffs2 mtd@system /system ro remount
mount yaffs2 mtd@userdata /data nosuid nodev
mount yaffs2 mtd@cache /cache nosuid nodev

# mount partitions
mount_all /fstab.pico

So, if you're gonna just edit those lines, and just change the mtd@userdata, or the mtd@system lines, then, you'd likely be pretty much booting the ROM again from your internal nand. the main reason for this being the line below: mount_all /fstab.pico, which is the fstab.pico I was talking about...

Now, if you'd open up fstab.pico, its pretty much like the /etc/fstab that you'd find on any linux system. the typical device, mountpoint, type and all... If you'd open it, you'll find this:

#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/mtdblock3 /system yaffs2 ro,barrier=1 wait
/dev/block/mtdblock4 /cache yaffs2 nosuid,nodev,barrier=1 wait,check
/dev/block/mtdblock5 /data yaffs2 nosuid,nodev,noauto_da_alloc,barrier=1 wait,check

/devices/platform/msm_sdcc.1/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard0:auto

Well, those were the lines from the CM11 preview, not exactly the same, the last line was derped by me in my vain attempts to get the sdcard running... Oh, and the mounting of the SD Card's completely changed too :silly:

BTW, getting back to mounting the ROM from the sdcard, you'd need to edit this fstab.pico file, to something similar to this:

#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/mmcblk0p2 /system ext4 ro,barrier=1 wait
/dev/block/mmcblk0p4 /cache ext4 nosuid,nodev,barrier=1 wait,check
/dev/block/mmcblk0p3 /data ext4 nosuid,nodev,noauto_da_alloc,barrier=1 wait,check

/devices/platform/msm_sdcc.1/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard0:auto
[HTC Pico (Explorer)] thewisenerd:
Well this is the first post, asking for help... Hope you get the hint *wink *wink

In case you can't get something done, ask for help here!

I tried porting the touchscreen gestures from Siyah Kernel with reference from this commit: https://github.com/gokhanmoral/siyahkernel3/commit/9f57d9efc7458c1a9f540cd04bc5cb14e08fb342

Well, that more or less turned out to be like this: https://github.com/vineethraj49/android_kernel_htc_pico/tree/gestures (check the last few commits...)

And, turns out it works :laugh: with a small bug :(

1. only single finger gestures work, i think....

2. no way to get the infinite while loop started at init.d

Here's how I did it... Reference thread: http://xdaforums.com/showthread.php?t=1831254

the init.d script is as belows, doesn't work...

#!/system/bin/sh

echo "
# Gesture 1 - swipe 1 finger near the top
1:1:(0|150,0|150)
1:1:(210|320,0|150)
" > /sys/devices/virtual/misc/touch_gestures/gesture_patterns

while [ 1 ]
do
GESTURE=`cat /sys/devices/virtual/misc/touch_gestures/wait_for_gesture`

if [ "$GESTURE" == "1" ]; then

screencap > /sdcard/`date +%H%M%S.png`

fi;

done

So, inputted those commands using adb, in adb shell, and it works... Got a hell lot of screenshots... but, any way to fix the bugs I mentioned? :cool:
[HTC Pico (Explorer)] v_superuser:
Hey, one question

I'd like to know about one thing, I've seen people talking about memory increasing kernels and kernels that mount certain partitions(like cache, data etc. etc. :p ) . i want to know how this works? I mean, what all things are to be done in both things for them to work?

I'll be glad if you tell this to me in a noob-friendly way. :victory:

Thank You! :fingers-crossed:
[HTC Pico (Explorer)] v_superuser:
Three words - YOU ARE GREAT! I mean, in the whole explanation you did, I just knew that there is some reverse mounting in init.rc in which few partitions are mounted as data/cache and you cleared my concepts. One more thing related to this I'd like to ask, in sense based roms(For our device) is it possible to do changes in init.rc(which I guess would be required) so that apps are directly installed in sd-ext and the symlink also gets done.

Once again,

THANKS
[HTC Pico (Explorer)] ateeq72:
Lol thats a huge explanation! :good: :highfive:
[HTC Pico (Explorer)] cute_prince:
Yes, it is possible. Open your init.rc and find the following line:

mkdir /data/app 0771 system system
mkdir /data/app-private 0771 system system
mkdir /data/app-asec 0700 root root
mkdir /data/app-lib 0771 system system

Now change it like this:

# For installing apps directly to /sd-ext:
mkdir /sd-ext/app 0771 system system
mkdir /sd-ext/app-private 0771 system system
mkdir /sd-ext/app-asec 0700 root root
mkdir /sd-ext/app-lib 0771 system system

# Now the symlinking part:
symlink /sd-ext/app /data/app
symlink /sd-ext/app-private /data/app-private
symlink /sd-ext/app-asec /data/app-asec
symlink /sd-ext/app-lib /data/app-lib

NOTE: Before doing this make sure that you have mounted /sd-ext partition.
[HTC Pico (Explorer)] cuteitsme:
[MENTION=4869275]thewisenerd[/MENTION]....excellent post.....cleared so many doubts....You are really great.

I have a question, I am no dev but just trying to learn some basics about android. As u said that ramdisk does the job of mounting sd partitions using the reverse mounting thing. What is the job of the scripts like int2ext or ungaze or mount2sd.

Is it like when the reverse mounting is not done in ramdisk we need to use these scripts. If yes, then how do these scripts talk 2 ramdisk or kernel to tell them to mount these sd partitions.

I know this may sound noob to you. But m just trying to learn some basics. :)
[HTC Pico (Explorer)] v_superuser:
[MENTION=4649424]cute_prince[/MENTION] Thanks. Now, I'm gonna post all my doubt related to kernels and ramdisks! Thanks to [MENTION=4869275]thewisenerd[/MENTION] as well! :)
[HTC Pico (Explorer)] cuteitsme:
Simply awesome.....what an explanation sirji.... :D

Still trying to understand some part but i will have to do more reading for that first....that i will do.....but must say U rock man.....thanks a lot for this....
[HTC Pico (Explorer)] v_superuser:
I read somewhere, that init.d scripts run alphabetically, maybe this is the reason int2ext is named as 40int2ext so that it starts first? ;)
[HTC Pico (Explorer)] cuteitsme:
Yeah....I guess that's the linux thing. I think the higher the no. the late the script will be called. This is basically to run the more important scripts before the other scripts.
[HTC Pico (Explorer)] cuteitsme:
hi i unpacked the boot.img files of cm11 beta 1 and 2 in order to understand this better and understood many things which u have explained.

I did found those lines starting with exec in some init. files.

Thanks a lot for this. Since u must be aware that the sd-ext is not mounting in buid 2 and thus int2ext is not working. So, out of curiosity I was trying to understand the difference between these two files from different builds(beta 1 and 2) but not able to find any.

Can u give any hint as to why even after having the same lines in fstab.pico of build 1 and build 2 int2ext was working in buld 1 and not in build 2. Of course by doing reverse mounting we can overcome this issue. But I am just trying to understand the difference between the two builds at ramdisk level.
[HTC Pico (Explorer)] thewisenerd:
Hmm... Could you post the two boot.img's here? I'd like to have a look :)
[HTC Pico (Explorer)] cuteitsme:
Sure y not.....here u go :)
[HTC Pico (Explorer)] pico hackr:
[MENTION=4869275]thewisenerd[/MENTION]: does the ION Kernel used in cyanogenmod 11 support swap
[HTC Pico (Explorer)] v_superuser:
The question is: Why do you need swap? :confused:
[HTC Pico (Explorer)] thewisenerd:
[MENTION=4635923]galaxyfreak[/MENTION] said that there was some problem in init.rc (i doubt if it was init.rc, it might have been init.pico.rc as well :| ) as per this post: http://xdaforums.com/showpost.php?p=48782331&postcount=646

Anyways, I'm waiting for his patch, to see what he's changed... Will get back to you later, informing the changes :)
[HTC Pico (Explorer)] sakshamx:
[MENTION=4869275]thewisenerd[/MENTION]

In CM 11 there r things through which we can change mount point

1 is the fstab and another is init.rc.pico

init.rc has a code something like

mount fstab and also other nand mounting codes

so can the stab can be removed and that code from int.rc ?

would be better then

the simpler the better
[HTC Pico (Explorer)] thewisenerd:
If you'd see (by comparison), both are doing the same thing :P

the init.rc.pico, after the "mount something somewhere" lines, a "mount_all fstab.pico" is called.

So, even though you do random stuff in mount lines, the fstab.pico would override them. So, ...
[HTC Pico (Explorer)] sakshamx:
that is why i asked if we could delte that ;)
[HTC Pico (Explorer)] thewisenerd:
you could delete those "mount something somewhere" lines in init.pico.rc, but not the fstab.pico, i guess...

[MENTION=4635923]galaxyfreak[/MENTION] is using some workaround for the mounting of partitions (which he probably fixed), so, I ain't that sure...
[HTC Pico (Explorer)] sakshamx:
or can we just use the mount_fstab be4 the actual mount code

with this we wont hav to take care of it
[HTC Pico (Explorer)] pico hackr:
bcz i use ram expander app from playstore i cant connect to swap partition made using it , it tells invalid argument
[HTC Pico (Explorer)] cuteitsme:
Yup even I am waiting for his patch. For some reason I dont feel the rom that smooth with this 2 partitions thing SD-System and SD-Data. No offense the rom is still smooth and we have the the advantage of increased /system partition but still I feel the rom more smoother with the normal sd-data and sd-cache partitions. Of course its my personal view. What's your take on this? just asking :)

---------- Post added at 10:27 PM ---------- Previous post was at 10:23 PM ----------

If you have partitioned your memory card using linux swap option and if you are using ateeqs kernel then i think the swap thing should work but if you are using amal's kernel and method I don't think the swap partition will work. :)
[HTC Pico (Explorer)] v_superuser:
One simple thing: Don't use swap.
[HTC Pico (Explorer)] thewisenerd:
a commit was missing!

IDK if galaxyfreak was using a custom boot.img or so, but clearly seems/ed to be using a custom init.local.rc (which copies into init.cm.rc at compile-time...)

This commit: https://github.com/CyanogenMod/android_vendor_cm/commit/6698e5ebdb538c0f3df694b91bd3ed70cb712f6f was missing in the init.cm.rc (note: init.local.rc in source), causing init.d to not work (look at the init.local.rc's diff)...

Anyways, hope this clears up why sysinit didn't run...

Just in case:

As I had said in this post: http://xdaforums.com/showpost.php?p=48776629&postcount=632,

So, it moved from being called as an exec to a service... Now, we look back into the android init reference... (find a more appropriate version (as we are talking about custom ROMs, and mostly CyanogenMod) here: https://github.com/CyanogenMod/android_system_core/blob/cm-10.2/init/readme.txt)

and

So, sysinit became a service, and it moved from "boot" to "post-fs-data" in this commit: https://github.com/CyanogenMod/android_vendor_cm/commit/79ba9970842d32470c43c4c634edef15b7c85e8c

The disabled option, as shown above... the service will not start with its class

which means that it has to be called for execution, and it's called in post-fs-data.

These commits went missing (*:confused:) causing init.d to not work. Anyways, this has been fixed up, so, all's well that ends well :D
[HTC Pico (Explorer)] gauravsaini964:
Can you tell me that how to change cpu frequency at the time booting of any kernel including sense one !!!
[HTC Pico (Explorer)] thewisenerd:
I am guessing these two files

/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

would have a direct effect on the cpu frequencies (correct me if I am wrong)...

These can be set at boot, by writing these lines to init.rc or init.pico.rc

write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq <insert-value>
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq <insert-value>

Note that the frequency has to be a valid one! Look at them frequencies here: https://github.com/sakindia123/android_kernel_htc_pico/blob/master/arch/arm/mach-msm/acpuclock-7201.c#L362
[HTC Pico (Explorer)] gauravsaini964:
Where would I find those files for sense kernel ???

I need to edit them just to oc upto 767 !!
[HTC Pico (Explorer)] thewisenerd:
In that case remove these lines (374-378) in "acpuclock-7201.c" (found at /arch/arm/mach-msm/ folder in kernel source), and recompile :D
[HTC Pico (Explorer)] gauravsaini964:
Non-dev :P

Will have to ask someone !!! How much time it takes to compile ???
[HTC Pico (Explorer)] thewisenerd:
Around 40 minutes on my pre-Pentium 4 processor,

and around 7 minutes on my Intel i3-3220 :D
[HTC Pico (Explorer)] gauravsaini964:
I need that modified kernel !! Sadly no one is up for modifying and compiling !!

We already have that for aosp and cm based rom !!! But none for sense :/

PS - Your explanations are far too good :D
[HTC Pico (Explorer)] gauravsaini964:
Please give a walk through on how to change ramdisk of kernel along with tools required for windows !!!

Thanks
[HTC Pico (Explorer)] thewisenerd:
AFAIK, the mkbootfs, mkbootimg, unpackbootimg are available for windows, but frequently, versions for these (for windows) surface... A few searches should get you in the right direction :)
[HTC Pico (Explorer)] thewisenerd:
currently working on a memory script for OC'ing with new PLL2 (based off int2ext)

anyone interested, the modified script (probably won't work that soon :rolleyes: ) would be up in a couple of hours :o

Also, we could use AnyKernel by koush, so that there's a common flashable zip for OC'ing picos (along with features like sweep2wake), because *almost* all the ROMs use the same kernel, so why bother making different flashable zips?

All this (right now, only a couple two) might be possible :)

And, this is a discussion thread too, remember? :angel:

what the script would do (if working):

Check if first boot

If first boot, format the partitions to ext4 accordingly

reverse-mount
[HTC Pico (Explorer)] cuteitsme:
Ummm sry BT confused a bit.....if m nt wrong Ocing is done in kernel. Right? Are u saying u will write a script for this which will enable Ocing as well as reverse mount?

Sounds lk a good idea if yes....:)
[HTC Pico (Explorer)] thewisenerd:
Not exactly...

AFAIK, most of the ROMs use a single kernel.

And, koush's AnyKernel would help us flash that zImage, without having to unpack/repack ramdisk and stuff... So, a single flashable zip (with an OC enabled zImage) can be used for OC'ing a variety of ROMs.

Now that the kernel part's done, looking for ways to reverse mount the partitions, why not use a script based off int2ext to mount the /sd-data and /sd-cache partition? :cyclops:

So, flash zip (which contains both modified zimage, and init.d script), and reboot phone! voila! you can OC your ROM :D
[HTC Pico (Explorer)] thewisenerd:
twn_oc_helper v0.1

Initialized a repo, a very messy initial commit, and I present to you, "twn_oc_helper" v0.1... my initials+ what the script is supposed to do :fingers-crossed:

Anyways, here's the script: https://raw.github.com/thewisenerd/twn_oc_helper/master/flashable/system/etc/init.d/40twn_oc_helper

what this does:

same as int2ext, with a "couple" of changes to make it mount sd-cache too :)

Use this script, if you have an OC'ed kernel, but it isn't having the appropriate ramdisk to reverse-mount the sddata, and sdcache partitions :angel:

will be Working on the zImage, and anykernel part later ;)

Yes, it does work.

Proof:

nvm about the image :p

More development to be done on this script:

Clean up code, and github repo :o

Restructure some of the functions, and mounting of partitions :p

add features like no journaling, and automatic cleanup (if first boot) :fingers-crossed:

Make the whole thing as a single flashable zip :)

Working on above features :)
[HTC Pico (Explorer)] akshay4:
wating for somthing like this ...by this we can include oc in all roms and those who wants oc they just flash this script insted of whole kernel ... no need to modify ramdisk great work OP:victory::D
[HTC Pico (Explorer)] thewisenerd:
Finally!

A no-ramdisk change required, OC'ing zip!

Initial public beta testing

this release is for: Any kitkat ROM running ION :D

Just flash the below attached zip, and poof! You can OC the device :D

Anyone wants to look at what made this possible, look here: https://github.com/vineethraj49/twn_oc_helper/commit/b5dd0d0169691e08677f74f744122392046501b2

^nvm, not necessary.

Pre-requisites:

No, really, read this first:

1. A rom with (working) init.d support and busybox

2. nvm, that's all' that's required :p

Download: View attachment kernel_update.zip

I tested this on:

Recovery used: Philz 5.15

ROM: Omni Beta 3

So, post your results below!!!

note: this doesn't even require a factory reset ;) :D
[HTC Pico (Explorer)] gauravsaini964:
Changing ramdisk of aries 3.5 oc kernel will make it boot in jb4.1 or 4.2.2 ????

Or what else to be changed ???

Edit :-

Make ION oc kernel for cody rom please
[HTC Pico (Explorer)] pico hackr:
[MENTION=4869275]thewisenerd[/MENTION]: ( I know its offtopic still i wish to say) hey anna sema post in cyanogenmod 11 thread , really proud of you anna and hatsoff to your work
[HTC Pico (Explorer)] thewisenerd:
Thanks, I'd see that as justifying myself. Anyways, no more "providing updated builds" in others threads, instead of asking their permission first :)
[HTC Pico (Explorer)] thewisenerd:
The good news is: It doesn't need a ramdisk change. Just flash it, and you're ready to go :fingers-crossed:

P.S. The zImage attached is only for Kitkat ROMs, as it contains an updated genlock.h header, and is likely to cause unlikely problems with previous android versions.
[HTC Pico (Explorer)] gauravsaini964:
If we replace genlock.h header [of which I have no idea ,what dat is :silly:] with older one !! We will get ion kernel for jellybean roms ???

If it is like ,its great !! Please make such kernel :good:
[HTC Pico (Explorer)] thewisenerd:
OFFTOPIC

moved to: http://xdaforums.com/showpost.php?p=49355310&postcount=9

as it was off-topic :p
[HTC Pico (Explorer)] singhranjit:
This is not working for me as whenever I use this it doesn't mount sd-data and sd-cache and I get low memory issue please tell me the right permissions or make a flashable zip please it will be helpful.