gingerbread compcache - G1 Q&A, Help & Troubleshooting

How can i add compcache to gingerbread rom.
I need a push in the right direction.

Same as in CM 6.x
But in addition you need
- a fix for loading the ramzswap module
- install rzscontrol
If you need further help, this evening I can provide you with a update.zip

AndDiSa said:
Same as in CM 6.x
But in addition you need
- a fix for loading the ramzswap module
- install rzscontrol
If you need further help, this evening I can provide you with a update.zip
Click to expand...
Click to collapse
Ya if you could possible set me up with and update.zip that would be great.
Lol school and work takes up all my time nowadays.

An update.zip, which enables compcache on gingerbread, too, is available here. Goog luck!

Related

tun.ko for NEXUS ONE available?

as I am behind the GFW of CN I am eager to get openvpn to work (trying with TunnelDroid, with vpn binaries of WITOPIA...
unfortunately i can't get the connection to work, and apparently it is because of the lacking tun.ko
I took the only tun.ko I can find online (vpn connnections, for DROID...), but apparently the current Nexus One kernel does not support.
Does anybody have a tun.ko file that works on Nexus One?
thanks....
I have the exact same problem.......I need a tun.ko to start using witopia to get through the stupid ISP block on google Voice !!
So if anyone has any working tun.ko PLEASE PLEASE help us out !!
I got it !!
Finally......I managed to extract the tun.ko from Modaco's latest build, so credit goes to Modaco for this, I just extracted it for those who like to stick to Stock Roms (like myself for now).
I tested it and it works
How do you guys like openvpn on android? is it pretty stable? Has anyone tried using Access Server?
Are you sure you're running the stock OS?
I am still getting those messages:
insmod: init_module 'tun.ko' failed (Exec format error)
and in dmesg:
tun: version magic '2.6.29.6-cm-teknologist-0.1 preempt mod_unload ARMv7 ' should be '2.6.29-01117-g4bc62c2 preempt mod_unload ARMv7 '
@chirayu : Well, I dont like it so much right since it still needs ALOT of work. Its lacking ALOT of things right now.
@sjakub : Yep, im running the latest ERE36 update. But yea its a stock image.
I didnt see any of the errors you mentioned. I got differnet errors while I was trying it with Witopia, which didnt really work out, but it doesnt seem like a tun driver issue, it was something about an encryption key not available, still working on that.
I have ERE27, that could be why. Where did you get that update from?
Can you get some other module from that phone (like bcm4329.ko) and look for 'vermagic' string inside?
Also, how did you extract tun.ko from that build? Maybe it's possible to extract one from the ERE27-based build?
sjakub said:
Also, how did you extract tun.ko from that build? Maybe it's possible to extract one from the ERE27-based build?
Click to expand...
Click to collapse
Well, the tun.ko is tested and works fine on ERE27 and ERE36 updates so that shouldnt be the problem.
As for the other files, like bcm4329.ko . Why would you need that ? It should be there by default ? as far as i know that module is responsible for certain wireless activities, I do have that file with me if you need it.
As to how i extracted, its simple.....I made a NAND backup of my stock image then flashed Modaco's latest update including the tecknologist kernel which supported tunneling and therefore included the tun.ko. Copied the file to the sdcard, then restored the backup and copied the files to /system/lib/modules
I don't NEED that module.
I would like to know what is the value of "vermagic" inside.
This is the string that describes the version of the kernel used.
Now, if it's something like '2.6.29-01117-g4bc62c2' and the one in the tun.ko you posted is '2.6.29.6-cm-teknologist-0.1' it means that you're somehow able to load module that has a different vermagic than a kernel. If the vermagic in bcm4329.ko is '2.6.29.6-cm-teknologist-0.1' it means that you have a different version of the kernel (and not the stock one). I have no idea why it would be working with ERE27 in that case, unless it was modified ERE27, not the stock one. Or, you were able to load an incompatible module somehow. In that case I would start investigating how to do that with my kernel as well
Hm, or you could check you phone's info:
Could you, on your phone, go to "Settings->About phone" and check what it says under "Kernel version"?
Thanks!
Finaly! I figured out how to build tun.ko module for the stock kernel.
If anybody wants to repeat that:
* I have Android OpenSource installed in /opt/android
* In /opt/android I did: git clone git://android.git.kernel.org/kernel/msm.git kernel-nexus
* In kernel-nexus I did:
- git checkout -b origin/android-msm-2.6.29-nexusone
- git checkout HEAD^
(The last operation reverses one revision, I needed a previous revision from the tree. Different revisions generate modules with different vermagic values)
(Actually, instead of previous two this should work as well - it should checkout the correct revision: git checkout 4bc62c230b2942bea72c3b5258e3e4f1d6cb534b )
- make ARCH=arm CROSS_COMPILE=/opt/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- distclean
- adb pull /proc/config.gz
- gunzip config.gz
- mv config .config
- Edited .config: changed "# CONFIG_TUN is not set" to: "CONFIG_TUN=m"
- make ARCH=arm CROSS_COMPILE=/opt/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- modules
- The driver ends up in: drivers/net/tun.ko
- You can verify if it is going to match the kernel by running:
+ strings drivers/net/tun.ko | grep 2.6.29
+ It should produce "vermagic=2.6.29-01117-g4bc62c2 preempt mod_unload ARMv7"
+ The "2.6.29-01117-g4bc62c2" should be the same as the "Kernel version" in "Settings->About phone" on your phone.
* Now you can upload the module to your phone. I did:
- adb shell mount -o remount,rw /dev/block/mtdblock3 /system
- adb push drivers/net/tun.ko /system/lib/modules/
- adb shell mount -o remount,ro /dev/block/mtdblock3 /system
- And you can use adb shell, enter /system/lib/modules and run: insmod tun.ko
- It should work
The module is attached.
hey Sjakub..
I have tried using your module and I got the same thing like with the one i extracted from Modaco's mod. The tunnel droid gets stuck at "Connecting" any ideas?
Thanks again for all your work mate appreciate it !
Cyanogen Roms have built-in openvpn support. I don't have any problem using Tunneldroid on CM 5.0.4.1. I got the tun.ko error only when I was on the stock ROM. I'm also behind the GFW. Witopia does the trick for me.
thank you sjakub~i used to use your tun.ko working very well with tunneldroid.but after i update the kernel that supports tethering.the tun.ko doesn't work... the new kernel version is:2.6.29-gad36b87-dirty...
The tun.ko module has to be compatible with the kernel you have. Where did you get the kernel from? You need to find a source of exactly that kernel version and compile tun.ko yourself.
sjakub said:
The tun.ko module has to be compatible with the kernel you have. Where did you get the kernel from? You need to find a source of exactly that kernel version and compile tun.ko yourself.
Click to expand...
Click to collapse
i download the kernel for my nexus one from here ——code.google.com/p/android-wifi-tether/
and i follow the steps in the site to flash my rom :code.google.com/p/android-wifi-tether/wiki/NexusOneKernelUpdate
finally...i'm not able to use the previous workable tun.ko which you built...and i'm afraid that i was too amateur to complie tun.ko myself even though you have already list out the compiling steps...
Try asking authors of the wifi-tether for that module. That's probably the easiest way
sjakub said:
Try asking authors of the wifi-tether for that module. That's probably the easiest way
Click to expand...
Click to collapse
okay~i manage to browse that source in google code,though,i can't found tun.ko module.or maybe i will flash cyanogen rom which consist of all the necessary things
anyone brewing a tun.ko for nexus one froyo stock kernel. I don't see aosp code to build right now.

HTC Legend: full r/w access via overlay filesystem

Hey all,
No idea at all if this is possible or even applicable to the Legend [I'm not a dev, but still learning about Android ], but I thought it deserves a thread of its own just in case the method allows us to run metamorph on the Legend...
ValMar73 posted the quoted text below HERE
ValMar73 said:
Dear All,
I just noticed that people applied a trick to desire roms to obtain a kind of writing permissions on /system. Essentially, they create a "shadow" /system dir and the system looks for files in this dir before getting the ones from system.
See the details here:
http://forum.xda-developers.com/showthread.php?t=748025
People could run metamorph on the Desire with this and they applied to CM6 nightlies (Desire version)
Now, this should be applicable also to the Legend, right? All that is needed is the aufs module for the kernel. Does anyone know if this module is in the kernel in CM6 for the Legend?
Valerio
Click to expand...
Click to collapse
If the above is not applicable to the Legend... MOD: please feel free to delete thread.
I. they havn't succeed.
II. our kernel didn't include aufs, neither desire. you should compile module. it's called cross compile to get binaries via a pc.
or you can use aufs module for desire, with your own risk. anyway, it couldn't turn your legend to a bomb.
III. you should remount aufs to "the right mountpoint".
you should change fstab with update.zip <------ it could damage your system.
IV. sorry for my pool english.
Theta did succeed. The thread is listed as Fixed. On Page 6 they are discussing how to best implement it.
Sent from my Desire using Tapatalk
thx i ll try later
it could be used on legend after "cross compile".
Yes, it could be done. The principle is the same as on those Asus EEE PCs. Haven't read that Desire thread in all but I'm familiar with procedure to achive this. But the question is... is it worth? What would one gain with this? You still won't be able to remove fileas from system partition for real and you'll have references to "deleted" files on data partition which also will take space and inodes. So basically for any "deleted" file from system partition, you'll have less space on data partition.
First as lucloner said, you need aufs module. Then you'll need rw store. It can be directory on data partition or small image with file-system in it also on data partition. Then you have to mount aufs and mount-move partitions to the right places. It is imperative that this procedure is done as soon as possible in init.rc before any other service is run. Guys at Desire thread put the script into run-parts init.d script (I believe) which I wouldn't suggest. The possibility to damage the system is really infinitesimal and everything can be reversed. Also fstab is not an issue as there is no fstab in initramfs environment.
When I have time (possibly beginning of next week) I will prepare myself a cross-compiling environment for compiling kernel and try to compile aufs module for Legend's 2.6.29-5f084974 kernel. Then I will try to prepare init.rc with integrated aufs procedure.
if you will compile a kernel, plz add compcache module which already included in the kernel.
i'm lazy lucloner. lol
Have you tried compcache on some embedded device yet? I mean what's the actual gain? You have to take into acount that you have slow processor and compression would take time thus battery would drain faster.
compcache is great! it performans in my pIII laptop with 480 ram and ubuntu 10.04.
if you want to more ram, compcache is faster and better than swap. and drain battery faster for sure.
as a module, it could be disabled. i just decide to try.
in wiki:
wiki.cyanogenmod.com/index.php?title=Swap_and_Compcache
-------------
no i've not tried it on embedded device.
forgive my damn english.
OK guys, I managed to cross-compile Legend's kernel and add aufs module. I tried it and it worked.
You can download kernel and aufs module for Legend 2.03.405.3 (kernel version 2.6.29-5f084974) and give it a shot. Be advised, that there is only kernel image (not boot.img) and actual module aufs.ko in this zip archive.
You can try aufs like this (of course you have to be root and know what you are doing):
Code:
insmod /<dir_to_aufs_module>/aufs.ko
mount -o remount,rw rootfs /
mkdir /aufs
mkdir /rw
mount -o dirs=/rw:/data=ro -t aufs none /aufs
...now you should see contents of /data in /aufs. Any changes to /aufs should now be reflected in /rw and /data stays intact. Be careful not to drain all RAM as you are playing on initramfs
Please report back or feel free to continue the implementation.
Thread Closed.
New thread from BlaY0 Here: http://forum.xda-developers.com/showthread.php?p=7983387

[MOD] eRecovery for CM7/stock ...

Hi all!
Surfing a bit into XDA, I've created this mod in order to add to Froyo/GB/CM7 the way to access CWM on boot pressing any hardware keys.
Once installed, to access recovery you only have to repeatedly press any hard key; it works like eRecovery in Nova ROM.
In order to install/remove it, you only have to flash it via CWM, so you need CWM recovery installed at your OB.
V20B:
Installer: http://dl.dropbox.com/u/4629711/zeus/huexxx-eRecovery-V20B.zip
Remover: http://dl.dropbox.com/u/4629711/zeus/huexxx-eRecovery-remover-V20B.zip
V20N:
Installer: http://dl.dropbox.com/u/4629711/zeus/huexxx-eRecovery-V20N.zip
Remover: http://dl.dropbox.com/u/4629711/zeus/huexxx-eRecovery-remover-V20N.zip
CM7:
Installer: http://dl.dropbox.com/u/4629711/cm7/huexxx-eRecovery-CM7.zip
Remover: http://dl.dropbox.com/u/4629711/cm7/huexxx-eRecovery-remover-CM7.zip
Stock V10D:
Installer: http://dl.dropbox.com/u/4629711/cm7/huexxx-eRecovery-V10D.zip
Remover: http://dl.dropbox.com/u/4629711/cm7/huexxx-eRecovery-remover-V10D.zip
Stock V10E:
Installer: http://dl.dropbox.com/u/4629711/cm7/huexxx-eRecovery-V10E.zip
Remover: http://dl.dropbox.com/u/4629711/cm7/huexxx-eRecovery-remover-V10E.zip
PD: This stuff will probably work flawlessly in other stock rom versions, but to ensure that it will work, send me your /system/bin/pvrsrvinit file indicating your ROM version and I will create a specific .zip for this version. Thanks pbog1 for the file.
Credits go to knzo and D4rKn3sSyS.
If you find this useful, please thank it!
Regards.
No need to nandroid before install it... is fully probed.
Regards!
Suggestion: Information about CWM version?
It only changes one file at /system/bin, then I would suggest to use the latest CWM.
Regards.
It's a bit late on the boot, inject a sooner service.
Yeah, it's still at beta stage.
I though it would be a good point because is just before init.d starts.
I will find the first service and hijack it, but at least this mod can handle framework's loopboots.
Regards!
i'm doing the same thing for 2.3.4
but i was failed.
i hijacked lgdrmserver,no response
can you help me?
Try with another service... I can't say more ATM...
Send me the init.rc
This is great news!! AAMOF, the no-hard-reboot is one of the things that prevents me from flashing these days. Last time I bicked the phone I lost one full day.
I'll install this as soon as it's improved.
Thank you Huexx!
knzo said:
Send me the init.rc
Click to expand...
Click to collapse
sorry i dont know why i can't send you pm,here's link
http://hotfile.com/dl/132897861/3f3e377/init.rar.html
thx
Try to inject: /system/bin/pvrsrvinit.
It's the PowerVR SGX 540 driver and it's earlier in the boot.
Rename it to /system/bin/pvrsrvinit2, then create an empty bash file with that name and inject the command I used on my eRecovery and in the last line (after the keypress check) run /system/bin/pvrsrvinit2 or it won't boot.
got it,try it now thx
Hi all.
Looking at init.rc and according with the suggested service by knzo, why you say that my inject point would be sooner?
sysinit is executed before ueventd, console, adbd, pvrsrvinit, etc... it's before ALL the services, and I haven't to modify it because it's a script by itself.
Regards.
Huexxx said:
sysinit is executed before ueventd, console, adbd, pvrsrvinit, etc... it's before ALL the services, and I haven't to modify it because it's a script by itself.
Click to expand...
Click to collapse
That doesn't even make sense.
You want to execute a sh without console running?
Or why can you see the first init.d in the adb logcat then?
Just because it comes in a previous line doesn't make it start sooner.
Well, if I've understood, the place at init.rc doesn't determines the run order, doesn't it?
Then how can you know which service will be launched the first?
If I hack pvrsrvinit, would it check for keystroke sooner?
Regards.
Depends on the trigger/call.
Pvrsrvinit ought to be sooner indeed.
Ok, let's try it then!
Regards.
it make nosense at all.
i don't know where i did wrong.
hijack pvrsrvinit,and create init.d folder ,write script to make original pvrsrvinit run...
My version doesn't work...
It's strange... later but It sholud run.

[ROM][4 Dec][HC32] isi-galaxy 1.2.5v with pershoot's kernel

This is based on P7500XWKK4_P7500NEEKK1_NEE Galaxy Tab 10.1 / HC 3.2 ROM but it is for the P7100 tablet.
​
Please read the whole thread before you flash. There are a couple of BUGS!
Flash on your own risk. I cannot be held responsible for any damage caused to your tab
This is not all my own work, I have worked with other members to get this ROM working.
DO NOT USE FACTORY REST IN ROM, EVER, USE WIPE SCRIPT TO RESET IF YOU NEED/WANT, IF YOU ARE GOING TO USE THE FACTORY RESET OPTION, YOU WILL BOOTLOOP!
kernel is provided by pershoot - compiled by myself - all kernel work is from pershoot here
first-time users you need to wipe! use supplied wipe script. Please read carefully, everything is here to get it flashed onto your TAB, if you do not understand what to do, ask, we will gladly try and assist.
Copy the downloaded files to sdcard (/sdcard/) and flash via ClockWorkMod
As always backup your data / apps before doing this! I use Titanium backup, search for it in the market.
Please read the thread before you report a bug. don't report already reported bugs. keep the thread clean. use xda's search feature
You need unlocked bootloader, click on link to see how to unlock.
You need root, click on link to see how to root.
Note: you MUST have Samsung Kies installed, or device drivers, for adb to work! It seems a lot of people do not have it installed, which causes a lot of confusion.
You need ClockworkMod Recovery (it is part of ROM Manager), download ROM Manager from market to install ClockWorkMod.
If you are a new to this please read this guide: http://forum.xda-developers.com/showthread.php?t=1232664, on how to unlock and root your TAB.
Please remember that this modified rom of P7500, Some features will not work 100%, most does but there are going to be a few bugs.
Features
Honeycomb 3.2 Based on P7500XWKK4_P7500NEEKK1_NEE ROM for the P7500, it will report as a P7500 but it is a P7100. Cannot change it to P7100 then some applications do not work.
Samsung TouchWiz UX UI
allows OC up to 1.4Ghz kernel, based on pershoot kernel compiled to include the following modules: ntfs.ko, tun.ko, cifs.ko
Kies via Wifi works on latest Kies in windows
Zipaligned
Deodexed - First boot will take a while, so be patient, if it did not boot after 30min then force a reboot!
Voodoo sound improvements (Download voodoo from Market)
NEVER USE FACTORY RESET IN INSIDE ROM SETTINGS OR DELETE DATA/CACHE IN CWM. YOU WILL BOOTLOOP!
See second post for other items
Bugs
3g: SIM PIN Lock must be removed for 3g to work after first boot. If you have SIM PIN please disabled it in Setting->Location and Security -> Set up SIM card lock
None of the security features work, Lock screen, PIN, Pattern, Password. If someone can let me know why and how to fix let me know!
Camera currently is only 3.2mp. May Crash sometimes - working on it.
Please report Bugs in thread
Thanks to:
pershoot, for getting the kernel working! He is the MAN! He worked nights to get the kernel working on the 10.1v, with not even having the device!
SEO, He has assisted me a lot over the last couple of months!, if it was not for him I could not have done this
To the community that got me into this without them I would not have been able to do this.
If I missed someone let me know it was not intended.
Changelog:
1.2.5.v: VoiceSearch.apk - deodexed
1.2.4.v: Camera fixed - touch autofocus - seo
1.2.4.v: Kernel modules cifs and ntfs added.
1.2.3v : Camera Fixes as per SEO
1.2.2v : Removed FactoryTest.apk and Factory.apk as per SEO suggestion.
1.2.1v : Public Release Build
1.2cv : third test build - limited testing
1.2bv : Second Build - internal
1.2av : Initial Build - internal
Download:
- 1.2.5v Full ROM
- please flash the "WIPE" zip, TB Galaxy WIPE script (SEO's), required for new users coming from stock. This will FACTORY RESET your tab but /data/media(sdcard) (your music, pictures & videos) will be left intact.
- this will NOT factory reset your tab if you're not on older version of this rom
More information available from. http://ismaakit.com/blog/
Kernel sources is compiled by me to make sure it is working 100%, but all credit goes to pershoot.
See this post: http://forum.xda-developers.com/showpost.php?p=20050409&postcount=128 for a different location. Thank you to algzed for providing this location.
Please do not link directly to the files, use this thread if you want to link.
[Q]
I updated and noticed cifs.ko is not included?
[A]
Here you go: Link This includes a compiled kernel without debug-info, it also include all the modules that is compiled for pershoots kernel. List of modules included:
asix.ko
aufs.ko
auth_rpcgss.ko
cifs.ko
dhd.ko
ff-memless.ko
hid-sony.ko
lockd.ko
nfs_acl.ko
nfs.ko
ntfs.ko
rpcsec_gss_krb5.ko
scsi_wait_scan.ko
sunrpc.ko
tun.ko
xpad.ko
[Q]
Where are the modules installed?
[A]
Have a look on the tablet via adb
Code:
adb shell
cd /lib/modules
ls
Latest Official buke2 Modem:
adb reboot bootloader
fastboot flash modem modem.bin
fastboot reboot
YOU DO THIS AT YOUR OWN RISK!
Modem.bin
-------------------------------------------------------------------------------------------------------------------
TIP: Enable USB Charging
Code:
adb shell
cd /sys/class/power_supply/battery/
echo 1 > force_usb_charging
To disable it:
Code:
adb shell
cd /sys/class/power_supply/battery/
echo 0 > force_usb_charging
b.t.w. a couple of users has asked why not default?
I DO NOT LIKE THE IDEA OF CHARGING THE BAT FROM USB, IF IT WAS SUPPOSE TO DO THAT, IT WOULD HAVE BEEN ENABLED, but that is me, you are welcome to do it if you wish.
This is active until you reboot. Then you will have to redo.
-------------------------------------------------------------------------------------------------------------------
TIP: IF YOU MAYBE LOOSE ROOT IF YOU RESTORE A ROM, TO GET ROOT BACK JUST DO THIS:
Code:
adb remount
adb shell chmod 6755 /system/bin/su
-------------------------------------------------------------------------------------------------------------------
You push me to flash my tab XD
Excellent job ! Thank you
I just got a tiny question, is it possible to made a touchwiz UX.zip apart ?
To keep the beauty of Honeycomb ?
Just asking
Downloading, will give this rom a try after download has finished
Thnx ISI (and offcourse seo and pershoot) to for all your work.
Downloading rom and will flash when, it's finished.
Richard
Send from my rooted 10.1v
Great Rom
Ok,
Fist of all thanks for having this new version of android on my tablet.
This is how i installed the ROM.
Coming from your HC3.1 1.03v:
booted in recovery via rom manager
install zip from sdcard isi-galaxy-1.2.1v.zip
wipe cache
wipe dalvik
reboot
I first thought my tablet was hanging, for several minutes it was stuck at the samsung logo during boot, so i hold the powerbutton and rebooted. After that it booted ok. Maybe i had to wait longer?
But everything seems to be ok. Appearantly it doesn't wipe
For me this rom is beter than the previous since I don't use camera and 3g.
The Calendar app is now amazing, it is fluent like it should have being.
I will report back if i encounted errors.
Fancois said:
You push me to flash my tab XD
Excellent job ! Thank you
I just got a tiny question, is it possible to made a touchwiz UX.zip apart ?
To keep the beauty of Honeycomb ?
Just asking
Click to expand...
Click to collapse
Nope, not at the moment. Maybe later. Let us get it stable first!
thzone said:
Ok,
Fist of all thanks for having this new version of android on my tablet.
I first thought my tablet was hanging, for several minutes it was stuck at the samsung logo during boot, so i hold the powerbutton and rebooted. After that it booted ok. Maybe i had to wait longer?
But everything seems to be ok. Appearantly it doesn't wipe
I will report back if i encounted errors.
Click to expand...
Click to collapse
Yeah you should have waited, first boot will take a while because the ROM is DEODEXED. After that is should fly.
ISI,
Do you know if the hooolmglow theme will work on this rom.?
Backing up my apps right now, then the flashing wil begin.
Thnx again
Send from my rooted 10.1v
isimobile said:
Yeah you should have waited, first boot will take a while because the ROM is DEODEXED. After that is should fly.
Click to expand...
Click to collapse
isi, some things I found so far while working on my own build:
- keeping stock p7500 gralloc.tegra.so / hwcomposer.tegra.so + stock 7500 kernel make video playback smoother. way smoother than *old* replaced hw libs + pershoot kernel. (of course camera does not work and orientation is always flipped but that's ok with stock kernel) we should wait for new official kernel source and keep p7500 libs in the future
- FactoryTest.apk BLOCKS setupwizard. removing FactoryTest.apk and Factory.apk should fix setup wizard and non-working lockscreen. pls test on your build.
I don't have much time ATM to fix camera / seccamera / secmediarecorder. will do it tomorrow and will post the apk here for you.
cheers
EDIT: btw I am not 100% sure that choppy video playback is caused by hw libs / kernel OR nvodm_* libs. no time to check atm.. will do later or tomorrow
You guys deserve a Christmas present. I know you don't take donations seo but what about a beer/coffee isimobile ?
seo said:
isi, some things I found so far while working on my own build:
- FactoryTest.apk BLOCKS setupwizard. removing FactoryTest.apk and Factory.apk should fix setup wizard and non-working lockscreen. pls test on your build.
I don't have much time ATM to fix camera / seccamera / secmediarecorder. will do it tomorrow and will post the apk here for you.
cheers
EDIT: btw I am not 100% sure that choppy video playback is caused by hw libs / kernel OR nvodm_* libs. no time to check atm.. will do later or tomorrow
Click to expand...
Click to collapse
Will test later today. thanks.
I got Camera at 8mp but Video Recoder crashed on me so I decided not yet to release and keep stock as to have a working camera set.
Thanks will wait for your patched files. I am no smali expert, would rather wait for you
[Edit] I can confirm if you delete those two files setup wizard works and lock screen as well! Great! Busy fixing....
Assistance needed: Someone with a fast internet connection. I only have a 512kb connection at home. It takes four hours to upload. So I did the change online. Hopefully it will work. It should!
Can you please test a fix for me. I did the fix online in the zip file not to upload everything from scratch.
Download this file. Do a full wipe and install. Post here if it works!
If no one tests it, I'll try that fix when I get home in a few hours...
isimobile said:
Assistance needed: Someone with a fast internet connection. I only have a 512kb connection at home. It takes four hours to upload. So I did the change online. Hopefully it will work. It should!
Can you please test a fix for me. I did the fix online in the zip file not to upload everything from scratch.
Download this file. Do a full wipe and install. Post here if it works!
Click to expand...
Click to collapse
Sorry isi im at work right now....
Will test tonight if still needed
So first flash wipe. Zip then flash rom....?
Send from my rooted 10.1v
Downloading...
Will flash and report..
-First Boot completed
-Setup - completed
-3G working
richard2311 said:
ISI,
Do you know if the hooolmglow theme will work on this rom.?
Backing up my apps right now, then the flashing wil begin.
Thnx again
Send from my rooted 10.1v
Click to expand...
Click to collapse
Not at the moment, will ask him later to get the theme.
Sent from my GT-P7500 using Tapatalk
isimobile said:
Assistance needed: Someone with a fast internet connection. I only have a 512kb connection at home. It takes four hours to upload. So I did the change online. Hopefully it will work. It should!
Can you please test a fix for me. I did the fix online in the zip file not to upload everything from scratch.
Download this file. Do a full wipe and install. Post here if it works!
Click to expand...
Click to collapse
Hi ISI
Just to confirm that it works
Just have to change than my signature
algzed said:
Hi ISI
Just to confirm that it works
Just have to change than my signature
Click to expand...
Click to collapse
Cool thanks.
Sent from my GT-P7500 using Tapatalk

Any way of hiding root or installing Magisk?

So I'm running the latest version of Evervolv Android Pie and I'm trying to hide root for apps that can detect it. At first I looked into Magisk as that has it built in, but upon reading, as well as trying it myself, it doesn't want to install. Is there a way to install it that I'm not aware of or is it just not possible? I've also looked into suhide, however I cannot get that to work either. Any info and help would be greatly appreciated, and I can provide any info that's needed. Thanks
Magisk does not work on the Hp Touchpad, it needs to modified the RAMDISK to have access to the Kernel and patch it.
This could be better, I do not know if it could be merge into the current Kernel.
https://www.xda-developers.com/kernel-assisted-superuser-kernelsu/
https://forum.xda-developers.com/android/software/root-backdoor-android-kernel-development-t3870559
Thanks for the reply, and appreciate the help. How would I go about merging it with the kernel? I know you said you didn't know if it could, but I'd want to try to see? Also, is there anyway of installing SuperSU in systemless mode so su-hide would work?
Camry2731 said:
Thanks for the reply, and appreciate the help. How would I go about merging it with the kernel? I know you said you didn't know if it could, but I'd want to try to see? Also, is there anyway of installing SuperSU in systemless mode so su-hide would work?
Click to expand...
Click to collapse
You are welcome,
The developers will have to merge the kernel Assisted SuperUSer ( kernelSU ) into the kernel branch of the Android ROM. Then it will need to be recompile, I provided a guide on how to recompile the HP Touchpad kernel:
Click HERE for the Guide
About Systemless: The boot image ( Ramdisk and Kernel ) is read only and it gets loaded into memory each time. There is no program that will be able to modified the boot image for the HP Touchpad, but the RAMDISK can be modified manually, here is a guide on how to do it:
Click HERE for the Guide to unpack and repack the Ramdisk
The Ramdisk modification only allows /system to have read and write access for SuperSU to work, it does not modified the kernel.
To modified the Kernel for systemless this is what is required and then recompile the kernel.
Click HERE to compile the kernel with root permission.
I have not look into this on the HP touchpad Kernel and I know that all I have posted on here is a lot to do, but if you want, let me know the version of Android you want to have the kernel with root access and the CPU speed and I could try to compile that and then you test it.

Categories

Resources