10/30/11 Update: Added modules for GB kernels (e.g., EH17).
Since they're somewhat frequently requested, this thread contains compiled (in-tree) kernel modules that don't come with stock kernels. They should, for the most part, work in any custom kernel based on the same kernel version/build.
Note that the EB13 modules are identical to EC05, so there is a single set posted for both kernel versions.
GB (EH17) Modules (mirror links):
cifs.ko (& slow-work.ko): CIFS/SMB file system (Samba/Windows shares): Mount w/CifsManager or Mount Manager).
fuse.ko: FUSE file system: For sshfs, other user-space file systems.
tun.ko: TUN/TAP network device: For Cisco VPN, OpenVPN, etc.
xt_TCPMSS.ko: Netfilter TCPMSS target: For MSS clamping in Wired/WiFi tether.
Built from GB kernel sources with these changes.
EB13 (& EC05) Modules (mirror links, do not require forum login):
cifs.ko (& slow-work.ko): CIFS/SMB file system (Samba/Windows shares): Mount w/CifsManager or Mount Manager).
fuse.ko: FUSE file system: For sshfs, other user-space file systems.
tun.ko: TUN/TAP network device: For Cisco VPN, OpenVPN, etc.
xt_TCPMSS.ko: Netfilter TCPMSS target: For MSS clamping in Wired/WiFi tether.
Built from Samsung kernel sources (SPH-D700_Froyo_update_EB13.tar.gz) with these changes.
If anyone is interested in a module not listed here, feel free to request it and myself or someone will compile it and add it to this thread.
So wait...these put abilities into kernals? Such as wired tether..........?????? >_>
Sent from my SPH-D700 using XDA App
What exactly is the implementation workflow for these?
A_Flying_Fox said:
So wait...these put abilities into kernals?
Click to expand...
Click to collapse
Sort of, they're loadable kernel drivers, to add functionality that's not found in the stock EB13 kernel. See Wikipedia. Typically the modules themselves aren't particularly useful alone, but are often required for third-party programs to function.
dannyzen said:
What exactly is the implementation workflow for these?
Click to expand...
Click to collapse
Typically one downloads a third-paty app for Cisco VPN, OpenVPN, or something like that. These apps require driver functionality (e.g., tun) in the kernel which do not come stock on the Epic. So one has to, as root, run "insmod tun.ko" (or whichever module) before running these to get them to work.
The kernel modules are specific to a kernel version, so it's typically recommended that one builds them per-device out of the Linux source tree. So I posted these for the Epic.
With regard to the TCPMSS module, this is a Netfilter feature that was previously included in the Eclair (e.g., DI18) stock kernels. For some reason Samsung decided to build it as a module in Froyo, but not actually include it in the initramfs.
So what exactly would be the benifit if I installed the tcp kernel mod? And are these compatible with the 0.2a genocide kernel? Thank you.
Sent from my SPH-D700 using XDA App
Cam3ron1 said:
So what exactly would be the benifit if I installed the tcp kernel mod?
Click to expand...
Click to collapse
If you use Wired Tether or a recent version of the WiFi Tether v3.0-preX series, then the module will allow MSS clamping while tethering.
In WiFi Tether, this has to be enabled in the Settings, and the option only appears if kernel support is available. I'm not sure if Harald has had a chance to integrate the change needed to detect modular TCPMSS support (as opposed to built-in), so it may not be available there yet.
MSS Clamping:
Network devices (Ethernet, wireless, whatever) communicate by encapsulating IP packets into frames. For any connection, these frames are limited to a certain size (maximum tranmission unit, MTU)--typically 1500 bytes. Now, TCP connections (HTTP, FTP, most of everything you do on the Internet except possibly gaming and real-time streaming) generate packets that are also limited in size, and that limit is negotiated during the connection handshake to whomever you're communicating with. This is the maximum segment size (MSS).
Typically, when a computer establishes a TCP connection, the MSS is set as large as possible, but small enough that each packet fits into one frame. It calculates this based on the MTU used for the network connection.
The problem is that, when tethering, typically the tethered-computer uses an MTU of 1500, but the tethered conection uses a lower MTU. For example, Sprint 3G uses 1492 (typical of PPP), and Sprint 4G uses 1400. This means, when tethering, your phone has to fragment each (large enough) packet into two frames before sending them over this air. This is somewhat space inefficient, and might reduce throughput--although I've not tested to see how noticable the effect is.
The TCPMSS module allows the phone to change (clamp) the MSS in TCP connections from tethered-devices to fit the MTU of the outgoing network conection. This makes sure that each TCP packet transmitted to/from the tethered-device fits in a single frame without fragmentation.
The real reason for MSS clamping is that some ISPs (particularly cable providers it seems) just drop fragmented packets. So, for example, in the context of a home wireless router, if you don't do MSS clamping, bulk downloads don't work at all--so most routers clamp. It's possible that some mobile providers don't support fragmentation either, although Sprint does.
So the practical benefit for you might be slightly-faster tethering. Or it might have no noticeable difference.
Cam3ron1 said:
And are these compatible with the 0.2a genocide kernel?
Click to expand...
Click to collapse
They should be, but I've not tested/used that kernel.
Samba would be pretty sweet. I hope someone uses it.
Sent from my SPH-D700 using XDA App
Schuby said:
Samba would be pretty sweet. I hope someone uses it.
Click to expand...
Click to collapse
CifsManager (xda thread) and Mount Manager support mounting SMB shares with the CIFS module. So yeah, you can stream music/movies that way.
Added those to the OP.
Dumb question, would the tun.ko for EB13 work with DK28 kernel? Both froyo, but I don't know if there are enough differences to matter.
rcboosted said:
Dumb question, would the tun.ko for EB13 work with DK28 kernel?
Click to expand...
Click to collapse
Probably, it doesn't touch any Samsung-specific code that would've changed since DK28, but YMMV.
This must be a noob Question but where to you put these? to get them working?
zman519 said:
This must be a noob Question but where to you put these?
Click to expand...
Click to collapse
It doesn't really matter, /sdcard, /data/local/tmp, etc. Permanently I'd put them in /data/modules or /system/lib/modules even.
To load them you have to use insmod. So, for example, if you put tun.ko in /sdcard, from a shell (e.g. ConnectBot local or adb) run:
Code:
su
insmod /sdcard/tun.ko
Modules stay loaded until you reboot the phone. If you want to unload one anyways (e.g tun), run from a shell:
Code:
su
rmmod tun
Most programs that typically require a kernel module have a feature that lets you specify their location and it will load them automatically. CifsManager and Mount Manager do this I believe.
Can I Flashes these with clock work 3.0.0.6?
Can these be flashed with clock work? I guess not. I tried and I failed.
Thanks, useful. Is the source published?
k0nane said:
Is the source published?
Click to expand...
Click to collapse
They're built from unmodified EB13 kernel sources. I've made that more explicit in the OP and attached a diff against the stock kernel configuration along with the Samsung source link.
jamice4u said:
Can these be flashed with clock work? I guess not. I tried and I failed.
Click to expand...
Click to collapse
these are more for devs to cook into roms and custom kernels.
For the life of me I cannot get this working. I tell CIFSmanager exactly where the module is but it never loads it.
Could the lack of tethering module be the cause of my wired tethering randomly disconnecting? It does not randomly disconnect in DI18.
Sent from my SPH-D700 using XDA App
muyoso said:
For the life of me I cannot get this working. I tell CIFSmanager exactly where the module is but it never loads it.
Click to expand...
Click to collapse
It looks like the stock kernel doesn't have the slow_work stuff enabled, which cifs requires. For cifs, a whole new kernel needs to be compiled and installed.
dnathan13 said:
these are more for devs to cook into roms and custom kernels.
Click to expand...
Click to collapse
These are really intended for folks running a stock kernel, but who need an extra module or two to use VPN clients, CIFS, etc. Every so often a thread pops up in General requesting "tun.ko" or some other module for the stock kernel. This thread is intended to provide those modules in a single location.
These modules may also be useful for folks running custom kernels that don't include these features yet. However, kernel developers don't need these, they'll just compile whichever feature is desired either as a module, or into the kernel itself.
tartarhead said:
It looks like the stock kernel doesn't have the slow_work stuff enabled, which cifs requires. For cifs, a whole new kernel needs to be compiled and installed.
Click to expand...
Click to collapse
Good catch. CIFS didn't depend on slow-work in Eclair, so I didn't notice the kernel config change nor did I test that module, as I don't use CIFS myself.
Anyways, Tab folks have had success building slow-work as a module. I've done so here and updated cifs-EB13.zip, along with the source modifications, in the OP. I've tested the new cifs module and it at least inserts, although I have no way to verify its functionality.
Do note, the slow-work.ko module needs to be inserted before cifs.ko as it's a dependency.
muyoso said:
For the life of me I cannot get this working. I tell CIFSmanager exactly where the module is but it never loads it.
Click to expand...
Click to collapse
It should work now with the updated modules. According to this, if you place slow-work.ko & cifs.ko in /sdcard, you should tell CifsManager to load "/sdcard/slow-work.ko:/sdcard/cifs.ko".
DeeODoubleD said:
Could the lack of tethering module be the cause of my wired tethering randomly disconnecting?
Click to expand...
Click to collapse
No, that's likely something else. Are you using the Wired Tether client?
Related
This is a test release with a new kernel 2.6.32 based from legend kernel source modified by cyanogen and attn1 to work on cm6. I am looking for reports on wifi and bluetooth mostly. Since this just replaces the kernel in 6.1.0 RC2. I don't want bug reports of issues already mentioned in the main 6.1.0 RC2. Please contain them to wifi and bluetooth. Overclock is included. I basically want to make sure your wifi runs good and the bluetooth works with your headsets/a2dp devices.
Thanks for testing
http://www.mediafire.com/?fbdrs3n6jv6d3d0
jznomoney said:
This is a test release with a new kernel 2.6.32 based from legend kernel source modified by cyanogen and attn1 to work on cm6. I am looking for reports on wifi and bluetooth mostly. Since this just replaces the kernel in 6.1.0 RC2. I don't want bug reports of issues already mentioned in the main 6.1.0 RC2. Please contain them to wifi and bluetooth. Overclock is included. I basically want to make sure your wifi runs good and the bluetooth works with your headsets/a2dp devices.
Thanks for testing
http://www.mediafire.com/?fbdrs3n6jv6d3d0
Click to expand...
Click to collapse
Changelog?
Is the included overclock already clocked higher or is it set at stock?
It would be great to have more info on this please! I may test it out once you can include more information.
The os itself is the same it's just a kernel change. Going from 2.6.29 in the other release to 2.6.32 in this test release. It's basically a subsystem change. You won't see any cosmetic change. I just want to make sure it doesn't cause any issues before attn1 and I add it to the next cm release. The only reason I mention OC is because this kernel still has it in it. So you will have the same OC features as the 2.6.29 kernel. Hope this helps explain what has changed.
Just curious if this .32 kernel will pave the way for FM radio support?
Wifi is working fine for me so far. I don't use any bluetooth devices, so haven't tested that.
Sent from my Liberty using XDA App
downloaded, haven't flashed it yet. There's still no nls_utf8.ko in /system/lib/modules. I know how to compile one, but I'll appreciate if you guys could make a small change in the config.
Code:
CONFIG_NLS_UTF8=m
That would save my trouble.
Wifi is working fine; tested both Wifi data connection and Wifi tethering (actually posting this using Wifi tethering). BT paired with Plantronics 520 headset is working and BT Voice Dialer was launched when I selected the headset button.
Do you just flash this?
Sent from my Liberty using XDA App
You install it the same way you install the cm6-rc2.
ladios said:
downloaded, haven't flashed it yet. There's still no nls_utf8.ko in /system/lib/modules. I know how to compile one, but I'll appreciate if you guys could make a small change in the config.
Code:
CONFIG_NLS_UTF8=m
That would save my trouble.
Click to expand...
Click to collapse
I made a kernel with your change. You'll still need to install the first package on this page before you install this kernel update. What is is for nls_utf8 used for anyways? Does this kernel update do what you need it to?
http://www.mediafire.com/?8c9pqhckurh7rlg
jznomoney said:
I made a kernel with your change. You'll still need to install the first package on this page before you install this kernel update. What is is for nls_utf8 used for anyways? Does this kernel update do what you need it to?
http://www.mediafire.com/?8c9pqhckurh7rlg
Click to expand...
Click to collapse
Thank you so much!!
nls_utf8 should always comes with cifs. With this module, we can mount cifs with "iocharset=utf8" option to access files that have special characters in their names. This is quite important for non-english users who use cifs.
WiFi seems be fine here. Bluetooth connects and working fine with Blue Eagle ll headset.
Sent from my Liberty using XDA App
Thanks for your input guys, if I could get some more it would be great. CM6.1 final will be out in the next couple of days so I'd like to get as much feedback as possible before then.
Bluetooth is connecting fine with my Nokia headset (BH-503). Wifi is working no different for me (aka, it works).
Tether working great for me don't know about Bluetooth don't ever use it but everything else is great!
Sent from my Liberty using XDA App
Wifi's fine. Cifs's working and it's good to have utf8 support.
Don't have any BT device to test on.
Wifi working for me. Just the kernel flashed over the latest nightly.
Downloaded this, ran it through it's paces as best I could. Connected two bluetooth devices (jabra and jawbone) worked without any glitches or weirdness. I also moved between several wifi spots WEP, WPA, and unsecured without issue.
Need any other info let me know.
I can also verify wifi working perfectly.
(no bluetooth devices to test that)
Only ROM in the CM series that works with my WIFI router (WPA-PSK). Had tired the most recent CM version and really liked the expanded dock along the bottom that allowed up to 5 icons to be placed there, but again, no wireless. Guess I'll stay with this one till Gingerbread comes out, Right...
Would one of the Dev's be willing to tackle getting VPN PPTP with encryption (mppe 128 or 256) working on the G-Tab? Right now it is either not working or working as unsecured PPTP (depending on the ROM). If anyone knows of a ROM where this is functional please let me know.
What little I have found on the history of VPN in android indicates that the last version with encrypted PPTP was version 1.6. Google was having problems keeping a connection to the VPN server.
Reference: http://code.google.com/p/android/issues/detail?id=4706
For myself and my coworkers this has become an important need. If we can't get the feature we may be forced to get iPads (*cringe*). I for one am willing to make donations to Dev(s) who can add this. Some ROMs have the option but seem to be lacking the module (unconfirmed) to handle encryption through the included PPPD.
It is possible this may come back in Android 3.0 since it is geared toward tablets but I haven't been able to find any information either way.
Thank you for your time.
Newanzer said:
Would one of the Dev's be willing to tackle getting VPN PPTP with encryption (mppe 128 or 256) working on the G-Tab? Right now it is either not working or working as unsecured PPTP (depending on the ROM). If anyone knows of a ROM where this is functional please let me know.
What little I have found on the history of VPN in android indicates that the last version with encrypted PPTP was version 1.6. Google was having problems keeping a connection to the VPN server.
Reference: http://code.google.com/p/android/issues/detail?id=4706
For myself and my coworkers this has become an important need. If we can't get the feature we may be forced to get iPads (*cringe*). I for one am willing to make donations to Dev(s) who can add this. Some ROMs have the option but seem to be lacking the module (unconfirmed) to handle encryption through the included PPPD.
It is possible this may come back in Android 3.0 since it is geared toward tablets but I haven't been able to find any information either way.
Thank you for your time.
Click to expand...
Click to collapse
Did you try one of clemsyn's latest kernels - they have the tun support. Also on market place there is an OpenVPN app that attempts to install an openvpn binary - that same dev also has an OpenVPN settings app that you can use to create your tunnel. Perhaps that will work for you.
prscott1 said:
Did you try one of clemsyn's latest kernels - they have the tun support. Also on market place there is an OpenVPN app that attempts to install an openvpn binary - that same dev also has an OpenVPN settings app that you can use to create your tunnel. Perhaps that will work for you.
Click to expand...
Click to collapse
I can currently get a VPN connection, but the server refuses it because it isn't encrypted - even with the encryption option on. I'll try clemsyn's kernel. I noticed he posted one specific to the ZTab ROM recently.
Newanzer said:
I can currently get a VPN connection, but the server refuses it because it isn't encrypted - even with the encryption option on. I'll try clemsyn's kernel. I noticed he posted one specific to the ZTab ROM recently.
Click to expand...
Click to collapse
PLEASE keep us updated. This is also essential to my job and I want to use android! GTab in particular.
jmdearras said:
PLEASE keep us updated. This is also essential to my job and I want to use android! GTab in particular.
Click to expand...
Click to collapse
No luck. Tried the new kernel and still get the same error. G-Tab shows connection lost. Server log shows same error (port 47 blocked or unable to negotiate encryption). Since our laptops all work I'm going to assume port 47 isn't blocked on our network. Maybe not enabled on G-Tab?
Which ROM are you using?
EDIT: nevermind - I see zpad rom. Did you try the vegan rom or tnt rom?
I am setting up a server with two cards and windows server 8 and an accesible ip just as test lab for this. If any dev wants access pm me.
Sent from my DROIDX using XDA App
Newanzer said:
Would one of the Dev's be willing to tackle getting VPN PPTP with encryption (mppe 128 or 256) working on the G-Tab? Right now it is either not working or working as unsecured PPTP (depending on the ROM). If anyone knows of a ROM where this is functional please let me know.
What little I have found on the history of VPN in android indicates that the last version with encrypted PPTP was version 1.6. Google was having problems keeping a connection to the VPN server.
Reference: http://code.google.com/p/android/issues/detail?id=4706
For myself and my coworkers this has become an important need. If we can't get the feature we may be forced to get iPads (*cringe*). I for one am willing to make donations to Dev(s) who can add this. Some ROMs have the option but seem to be lacking the module (unconfirmed) to handle encryption through the included PPPD.
It is possible this may come back in Android 3.0 since it is geared toward tablets but I haven't been able to find any information either way.
Thank you for your time.
Click to expand...
Click to collapse
Try this, I enabled everything re: PPP in this kernel including PPTP and also enable MPPE (Microsoft PPP Encryption). I hope this helps. BTW, this MPPE is experimental in the kernel but I hope it works for you.
clemsyn said:
Try this, I enabled everything re: PPP in this kernel including PPTP and also enable MPPE (Microsoft PPP Encryption). I hope this helps. BTW, this MPPE is experimental in the kernel but I hope it works for you.
Click to expand...
Click to collapse
Brillant! I have a connection! From home even. Many Thanks! (but I can only hit the button once...)
I'll keep an eye on it and see how long the connection lasts. That seemed to be the bug that killed Google's interest in this. With luck it wont show because someone tweaked over it.
I'll spread the word. Thanks again!!
Update: Unfortunately the data traffic stops within a minute. The connection stays up and reports a server connection just no data passes. This is the same issue as Google has in it's bug report. I"ll look at the server logs in the morning to see if anything is reported, but it is at least a step in the right direction.
BTW: The GUI seems a bit faster. Were there any other tweaks in that kernel?
Newanzer said:
Brillant! I have a connection! From home even. Many Thanks! (but I can only hit the button once...)
I'll keep an eye on it and see how long the connection lasts. That seemed to be the bug that killed Google's interest in this. With luck it wont show because someone tweaked over it.
I'll spread the word. Thanks again!!
Update: Unfortunately the data traffic stops within a minute. The connection stays up and reports a server connection just no data passes. This is the same issue as Google has in it's bug report. I"ll look at the server logs in the morning to see if anything is reported, but it is at least a step in the right direction.
BTW: The GUI seems a bit faster. Were there any other tweaks in that kernel?
Click to expand...
Click to collapse
There is a cryto sha 256 or 512. Lmk which to enable
clemsyn said:
Try this, I enabled everything re: PPP in this kernel including PPTP and also enable MPPE (Microsoft PPP Encryption). I hope this helps. BTW, this MPPE is experimental in the kernel but I hope it works for you.
Click to expand...
Click to collapse
This is awesome - and just what I was looking for! Any chance you could post the Vegan version as well? Thanks so much!
Hi Clemsy,
Thanks again for all the great work you're doing. If you could also do this for vegantab it would be greatly appreciated.
Cheers
Jonesie
How do I install this file?
Jonesie18 said:
Hi Clemsy,
Thanks again for all the great work you're doing. If you could also do this for vegantab it would be greatly appreciated.
Cheers
Jonesie
Click to expand...
Click to collapse
I might have to take a pause on this since I'm having issues with my Gtab at the moment. My screen turned white and I can't see a thing. I was playing angry birds and noticed that my screen sensitivity turned bad and a few seconds later it turned all white. I might have to get a replacement for my Gtab
I can build the kernel for Vegan tab but there is no way for me to test it but it should work fine
I read a post that doing this might fix it:
Add the following to /etc/pptpd.conf
mru 1280
mtu 1280
Please try and see how it goes.
More Info
I had our network admin look at the VPN server logs for my connection. No errors or warning from the server.
One interesting thing to note, it seems that when the data transfer between the tab and the VPN server stops it's only one way. I was able to send mail out from the tab, but not receive mail or view web pages. I'm wondering if the decryption side (incoming to tab) of MPPe is broken. That could explain why the server keeps a connection, but the data flow seems to stop.
Could we steel code from a linux kernel that works?
clemsyn said:
I read a post that doing this might fix it:
Add the following to /etc/pptpd.conf
mru 1280
mtu 1280
Please try and see how it goes.
Click to expand...
Click to collapse
I don't have a pptpd.conf in /etc. What is the file syntax? I'll make one and copy it in. I'm assuming this is ./etc and not ./system/etc.
Edit: Never mind found info here: http://www.linux.org.au/~quozl/pptp/pptpd.conf.5.html
Edit Edit: Ok I think I have reached the level of my ignorance. How do you get a file copied to /etc? I have tried a file manager with SU permissions, and a terminal with SU permissions. In both cases I am getting a permission denied error. What's the secret?
Newanzer said:
I don't have a pptpd.conf in /etc. What is the file syntax? I'll make one and copy it in. I'm assuming this is ./etc and not ./system/etc.
Edit: Never mind found info here: http://www.linux.org.au/~quozl/pptp/pptpd.conf.5.html
Edit Edit: Ok I think I have reached the level of my ignorance. How do you get a file copied to /etc? I have tried a file manager with SU permissions, and a terminal with SU permissions. In both cases I am getting a permission denied error. What's the secret?
Click to expand...
Click to collapse
Upload the file and ill make a zip file for you to flash it.
So close ... I think Google may need to work out a few of their bugs first.
First off a big thanks to clemsyn for the hard work. (I used Root Explorer to copy the file pptp.conf)
Using the latest kernel posted here for VeganTab I was able to connect to a MS PPTP VPN and ping for a long while however just like my Samsung Vibrant the VPN appears to die once a burst of traffic is shot through the tunnel. The tunnel I have discovered is not disconnected but unusable through the Android system. If I disconnect the VPN session remotely the log files indicate that the remote server killed the connection. Not sure much can be done as now I feel I am hampered by Google's inability to care for VPN access. I am sure the developers here can figure this out but why should they have to figure this out when it seems to be a fundamental issue with Google's code. Maybe this disconnection does not happen with OpenVPN? Anybody use it? I am tempted to setup a test OpenVPN server just to see how long I can keep my connection.
BTW ... After remotely killing the VPN connection the VPN services crashes and throws up an exception in the back ground when terminating the service.
Not working. I might try without the encryption in the server side to check if that works. It actually connects (pings) a couple of seconds with the LAN computers... then it nevers connects again... even with reboots. Does the pptpd.conf only need those two lines?
I found this site which may help
http://code.google.com/p/android/issues/detail?id=6402
A user stated this:
"Hey! Saw another post elswhere in the forum. For Microsoft VPN using PPTP, I think it helps to disable Software Compression in Routing and Remote Access Manager on the Windows server hosting VPN. After I did that, I was able to connect to VPN.
In Routing and Remote Access Manager, right click on the server in the tree and select Properties. Then, under the PPP tab, uncheck Software Compression. I am the Sys Admin at my Co, so I was able to do this myself. Others may have to submit a request to your respective Sys Admins. Besides, who uses compression on VPN's since the death of Dial-up?
Good Luck!"
2.2 released!
In the news!
Current features:
Based on Asus 9.2.1.27 WW kernelsources
Backported all Linux 3.2 USB LAN drivers (bandwidth up to 250 MBit/s! tested with a SMSC LAN7500)
ISO9660 (+Joilet), UDF, FAT12 and Apple HFS file system support (USB CD\DVD access! See notes)
Voodoo Sound support!
Turned a few unneeded kernel features off and compiled with Linaro GCC, it's smaller and boots quite a bit faster than other kernels!
Installable using your favorite recovery (tested on CWM v6.0.1.4 v2)
New versions of Tegra 2 codecs for ICS based ROMs (will be provided within a separate installable .zip)
Kernel manager application to manage loaded drivers and file system modules!
Supports almost all current ICS and JB ROMs
Compatible with:
[ICS] Asus official firmware (with root)
[ICS] Android Revolution HD
[ICS] Energy™
[ICS] Revolver
[JB] LiquidSmooth
[JB] RaymanFX's CM10
[JB] ParanoidAndroid:CM10 Hybrid
If you tested this with any other unlisted ROM, please drop some feedback!
Note 1: Some USB devices may need additional power, if so, get a Y cable from eBay so you can power a USB device using a external USB power source
Note 2: External optical drivers and floppy drives will not be mounted automatically, as Android doesn't officially support them
Note 3: CSS protected DVDs are not supported (e.g. Retail movies), due to Linux kernel limitations
Note 4: NTFS is not supported 'out of the box', please use Paragon driver from Google Play
Downloads:
https://www.dropbox.com/sh/gxi0gsl0tdfapgi/Ja19Exs4Sz
(PLEASE install Busybox 1.20.2 using one of the installer apps from Google Play, it is needed for the Kernelmanager application to function properly)
Source:
https://github.com/sander-ashwin/tf101-allinone-kernel
Please report if something does not work!!
Mounting optical drives:
1: First make sure your device is proper rooted (the "mount" command we'll use needs root)
2: Install Android Terminal Emulator from Google Play and open it
3: Type "su" and press enter, you should be asked if you would like to give root access, say Yes
4: Make a mountpoint directory, e.g. "mkdir /Removable/opticaldrive"
5: Mount your optical drive (make sure it gets enough power and something is inserted in the drive) using this command: "busybox mount /dev/block/sr0 /Removable/opticaldrive"
6: You're done! If you inserted a DVD movie, you might want to install Wondershare player or some other player that is capable of playing DVDs with menus
7: If you encounter any difficulties, please reply on this thread or send me a message
Connecting your TF101 to wired ethernet:
1: Buy a TF101 USB Host connector if you don't already have one (they are very cheap online, around 12-15 dollars)
2: Connect the adapter to your TF101, plug in your USB ethernet adapter
3: Android will display a message in the lower right corner of the screen that an ethernet adapter has been connected
4: Connect the LAN cable
5: Android will display a message that your device is connected using DHCP, you can now use internet using LAN
6: If you require manual IP settings, please go to Android's settings, there you can set manual IP or DHCP (OPTIONAL STEP)
Thanks to:
RaymanFX - for inspiring me with his own kernel, and for porting CM10
Asus - for making a pretty good device
prendomiao - for beta testing
Changelog
v1.0:
First release!
v1.1:
Removed some more junk from kernel
Now actually added new filesystem drivers!
v1.2:
Backport of Linux 3.6 I2C core
A little more cleanup of unneeded features
v1.3:
Backported all Linux 3.2 USB LAN drivers
Kernel now includes support for Voodoo Sound!
v1.4:
I2C fixes + Tegra I2C driver ported from kernel 3.6
Tweaked I2C timeout, hopefully our touchscreen won't lag anymore
(this may fix the problem that the touchscreen sometimes doesn't respond for a second, because of an I2C timeout)
v2.0:
Fixed sound
Now compiled using latest Linaro GCC 4.7.2 compiler
New kernel manager application to manage loaded drivers! You're in control, so the kernel doesn't load unneeded modules anymore!
Reverted I2C changes, as they didn't really help
v2.1:
Now compatible with ROMs based on RaymanFX's CM10
Updated BCMDHD WLAN driver for CM10 kernel
A little cleanup to synchronise both ICS and CM10 versions
Updated Linaro compiler to 2012.10
v2.2:
Added some new releases for more compatibility
i tried it. there is a little change, it is a bit speedly... i don't tried videos... but it is good good work
Thank you! Hope videos will play better as Tegra 2 is really picky with HD videos.
I'm now writing a tutorial for mounting optical discs, fortunately it's not really difficult.
but drivers must support them
Well, I included them already They are in your device if you still have my kernel installed.
But Android doesn't support automounting optical drives, so we have to mount the optical disc ourselves, until someone writes an app to do it (automatically).
EDIT: please install v1.1 if you would like to use your optical drive, as I forgot to include the drivers while compiling v1.0
Outstanding kernel. The first one I've run without SoD so far. I don't need OC, so the extra freq.'s are not important. Super quick, reliable so far for a few hours. I'll continue to report back, especially if I get SoD's. They are the bane of my existence. Keep up the good work.
Sent from my Transformer TF101 using xda premium.
Thanks! Hope you can enjoy your device again
I would like to implement overclocking though, but only if the kernel is still 100% stable for everyone.
Stil need to find out how, as I'm still learning C and kernel hacking.
The main problem at the moment is that all different hardware revisions have different issues.
Mine has touchscreen issues with a lot of kernels for example, your device may freeze when sleeping, but with a lot of testing and debugging we might be able to create a kernel that works for everyone.
When having any problems, please keep reporting!
poppajules said:
Outstanding kernel. The first one I've run without SoD so far. I don't need OC, so the extra freq.'s are not important. Super quick, reliable so far for a few hours. I'll continue to report back, especially if I get SoD's. They are the bane of my existence. Keep up the good work.
Sent from my Transformer TF101 using xda premium.
Click to expand...
Click to collapse
sainthout said:
Thanks! Hope you can enjoy your device again
I would like to implement overclocking though, but only if the kernel is still 100% stable for everyone.
Stil need to find out how, as I'm still learning C and kernel hacking.
The main problem at the moment is that all different hardware revisions have different issues.
Mine has touchscreen issues with a lot of kernels for example, your device may freeze when sleeping, but with a lot of testing and debugging we might be able to create a kernel that works for everyone.
When having any problems, please keep reporting!
Click to expand...
Click to collapse
To avoid SoDs, you need to set the lower voltage higher.
The standard voltages I'm using should be ok, but mine still SoD's sometimes.
With stock kernel as well as with other kernels, as well as with my own kernel..
Unfortunately it always happens when I'm not at home, so I can't directly debug using ADB (if possible at all).
So I can't easily find out wether it's a hardware issue, kernel issue or software issue.
If anyone has a clue about this, please reply!!
K900 said:
To avoid SoDs, you need to set the lower voltage higher.
Click to expand...
Click to collapse
sainthout said:
The standard voltages I'm using should be ok, but mine still SoD's sometimes.
With stock kernel as well as with other kernels, as well as with my own kernel..
Unfortunately it always happens when I'm not at home, so I can't directly debug using ADB (if possible at all).
So I can't easily find out wether it's a hardware issue, kernel issue or software issue.
If anyone has a clue about this, please reply!!
Click to expand...
Click to collapse
Is it SoD with dock connected or tablet alone? I'm sure you're familiar with the SD card removal thing from the dock to prevent SoD with guevors kernel? That wasn't my issue anyway, but it's just one I've heard of...
edit: you know, I didn't even think about the voltages being the issue with the other kernels... Is there an automated program to adjust voltages? I used QuickClock Overclock for my Droid X, but I'm not familiar with changing voltages on any other devices...
---------- Post added at 11:42 AM ---------- Previous post was at 11:33 AM ----------
I wouldn't MIND having OC, but I hardly use it. I got out of the OC game after watching it kill batteries on multiple phones and devices..
No one really NEEDS to OC, but for some reason people feel the need for it. The only phone I really NEEDED OC was my Droid Eris to play Angry Birds when that first came to Android... anyways, off topic...
I messed with the tablet last night, and still had no SoD.. I'll report back again tonight when I get home from work.
do you make it for jb please ?? we need it
Good to hear that the kernel works so far, hope it won't SoD.
I don't have the dock, the SoD's are just random it seems.
I'm also not working on overclocking anymore, too much files are involved which make it difficult to understand and fix.
It's also a pretty big risk, you could burn your CPU or GPU if using wrong values or something like that.
I'll leave the stock voltages and stock frequencies.
I'm now trying to fix the touchscreen issue that happens after some time. Not many people have the problem, so this won't do anything to other people.
Just updating the Linux I2C core to new 3.6 and backporting some newer touchscreen drivers.
Maybe I can also include some newer USB Ethernet drivers and backport other things.
When I implemented something that's worth trying out, I will put a new kernel version online
poppajules said:
Is it SoD with dock connected or tablet alone? I'm sure you're familiar with the SD card removal thing from the dock to prevent SoD with guevors kernel? That wasn't my issue anyway, but it's just one I've heard of...
edit: you know, I didn't even think about the voltages being the issue with the other kernels... Is there an automated program to adjust voltages? I used QuickClock Overclock for my Droid X, but I'm not familiar with changing voltages on any other devices...
---------- Post added at 11:42 AM ---------- Previous post was at 11:33 AM ----------
I wouldn't MIND having OC, but I hardly use it. I got out of the OC game after watching it kill batteries on multiple phones and devices..
No one really NEEDS to OC, but for some reason people feel the need for it. The only phone I really NEEDED OC was my Droid Eris to play Angry Birds when that first came to Android... anyways, off topic...
I messed with the tablet last night, and still had no SoD.. I'll report back again tonight when I get home from work.
Click to expand...
Click to collapse
Different JB ROMs may require different ramdisks, so it will take a little time to get it done properly and stable.
For which JB ROM would you like to use it? I might be able to take a copy of the ROM's kernel's own ramdisk and combine it with my kernel
I'm also thinking into making one for RaymanFX's new LiquidSmooth ROM, anyone interested?
prendomiao said:
do you make it for jb please ?? we need it
Click to expand...
Click to collapse
I am sorry if i sound stupid, but where do i extract files to? I have a flashing red light on my USB ethernet but no connection
Hi, does Android display a notification that you connected an USB Ethernet device?
And for which ROM are you trying?
mazimo said:
I am sorry if i sound stupid, but where do i extract files to? I have a flashing red light on my USB ethernet but no connection
Click to expand...
Click to collapse
USB Ethernet works on Android 2.3 with icon...
Ethernet doesn't have anything to do with Android at all.
The Linux kernel provides drivers which will provide Android a universal interface to control Ethernet devices.
When you plug in your USB ethernet device, the kernel will create an eth0 interface (first ethernet device interface).
Android sees that immediately and will show a little message that an ethernet device is detected.
With very old Android versions, Android doesn't really support ethernet, but some kernels do.. in that case ethernet support will be provided automatically without any notifications.
So for example, if Samsung want to support every USB ethernet device, they can, by building support into the Linux kernel.
If Asus doesn't, they don't build any support in the kernel, so the devices won't be recognised and so they will not work.
Except 1 or maybe 2 devices, the original Asus kernel doesn't support ANY Ethernet device, but my kernel supports them all
prendomiao said:
USB Ethernet works on Android 2.3 with icon...
Click to expand...
Click to collapse
new release
Everyone on older versions, please upgrade to v2.0 and try my new kernel manager application!
(Which is also my very first Android application)
Enjoy and please post feedback
If anyone would like to tryout a JB version of my kernel, please pm me!
I ran your 1.0 version, and it's great. I have MASSIVE battery life compared to before. The only issue I have noticed is with wifi reconnecting after deep sleep. It disconnects when screen is off (i verified the settings), but it has a difficult time reconnecting. I usually cycle the wifi toggle and it connects, or I click on my wifi and it connects. It's clearly not a major issue, just a little extra thought when I wake it up.
I read through and no one reported anything like this, so I figured it might be something to keep your eye out for in your later builds. I will install the 2.0 today and give feedback later. Thanks for your hard work!
I am using Gimlo 0.2 ROM and ICS Vengeance kernel.
I tried using Proxydroid in my phone to run my college wifi connection (which has a proxy) in all aps.
It didnt run. a bit of googling told me that i need a kernel with IPTables support.
K()T! said:
I am using Gimlo 0.2 ROM and ICS Vengeance kernel.
I tried using Proxydroid in my phone to run my college wifi connection (which has a proxy) in all aps.
It didnt run. a bit of googling told me that i need a kernel with IPTables support.
Click to expand...
Click to collapse
I honestly think Tipo already supports IPTables, as I use Droidwall (sort of firewall-like app, where you can select which app can and which app cannot connect to 3g and/or wifi). That app also uses IPTables...
But that's all I know. Perhaps I'm wrong, perhaps the support gets added by the app itself. Although I'm still quite sure as IPTables are a native Linux functions, while Android (and actually, also iOs, Firefox OS, and many more) is based on.
^ Thanks.
I'll try the app again...
Maybe I'm doing something wrong......
Hi,
i'd like to share my de-bloated & lite arrangement for GT-I9305 with you and hope some of you may like it, or even find it useful!
It all started as an experiment... for personal use only
I used an early alpha release of this tweaked ROM (system size < 1GB) to test hardware functionality
and power consumption of one of my devices.
After a while i thought it might be useful for others as well.
Some more words about my intention:
I thought about a stable stock ROM which is as close as possible to the official release but more essential.
As it all started on an experimental base and was focused on best effort, i decided not to start from scratch.
Of course this would have been the more elegant way, but basic work had already been done.
So special thanks go out to kenar2 for dumping, deodexing, zip-aligning and prepare the KK stock ROM for CWM flashing.
A lot of research has been done to seperate the essential parts from the extra stuff.
In the end i stripped of all apps which are not needed for the basic features of the system (tons of MBytes).
Additionally i tried to reduce the background traffic and services to the bare minimum.
Some basic addons (mainly apps) then got implemented to make the ROM at least usable.
I decided to choose mostly open source and non-playstore apps (there are some exceptions though)
and remove Google as far as possible.
The rest is barely as is, so no tweaks at apk level... at least for now.
The ROM is quite stable and you should check it out, if you...
... want good battery life
... like reduced background processes
... like some of the stock goodies (WiFi direct, MHL (HDMI) support, NFC)
... always wanted a good base to implement your own features
... like minimalistic ROMs
So here it is:
I9305XXUFNI3-DLite_V1
Size: 514 MB (539.169.629 Bytes)
MD5: bf481f11f7923f4c2f941a083700f587
- Based on kenar2's I9305XXUFNI3 KK 4.4.4
- Using kernel AGNi pureSTOCK V5.5 from psndna88
boot.img preconfigured and arranged by djb77 for TGP_I9305_XXUFNJ1_v20.20
UPDATE:
I created my own kernel based on psndna88 source branch pureSTOCK-I9305-4.4.4:
- applied offline charging patch
- removed f2fs support in config
- support for FTDI USB serial adaptors
- cleaned/shrinked down initrd
See attachment below!
Clean and mean... works very nice :victory:
- Implemented Superuser V2.45 from Chainfire
(formerly used GPL'd superuser from Koush, but unfortunately it's not ready for SElinux right now)
- Cleany removed KNOX (i don't use it)
- Removed Google apps and background services (not touching any jar files though, mainly for stability reason)
- Disabled and removed SetupWizard's at first boot (i don't need it)
- Added some open source apps mainly taken from http://f-droid.org
Firefox Version 35.0 (License: MPL2)
K-9 Mail Version 5.002 (License: Apache2)
Apollo Version 1.1 (License: Apache2)
Sound Recorder Version 1.0 (License: Apache2)
CM File Manager V1.0.2 taken from cm-11-20141030-NIGHTLY-i9305.zip (License: Apache2)
Hacker's Keyboard Version v1.37 (License: Apache2)
- I replaced Samsungs calendar app with a lightweight one, because I personally didn't like the look
of stock S-Planner and later versions are much too bloated.
Though my intention was to use open source apps, this one is simply the best and lightweight calendar app:
aCalendar V1.0.2 (Free version, Copyright Tapir Apps GmbH)
If you like a very basic calendar, look at f-droid.org again:
Standalone Calendar Version standalone-1.2 (License: Apache2)
Prerequisites:
- You'll need custom recovery installed first.
I recommend philz touch recovery 6.48.4 for i9305
Boot to recovery and do a clean wipe of cache and data partition.
Afterwards step to installation from external SDcard.
- If you're coming from an older version (e.g. 4.3) you'll need a KK modem firmware on your device to use this ROM.
I recommend I9305XXUFNI3 modem firmware to be installed before or directly after ROM has been written to flash.
Place the modem file and the ROM file on your SDcard and boot to recovery.
Get the modem files here:
http://sourceforge.net/projects/djb-tgp/files/CWM_Flashables/Modems/4.4.4 Modems/
http://sourceforge.net/projects/amchaprojekt/files/Modems/
Credits go to djb77 and kenar2 again for distributing these files!
- The ROM should work independent of the bootloader version...
... but has only been tested with old bootloader yet.
So as always... i am not responsible for anything you do with your phone. Please keep that in mind!!
Known issues:
- As i did not tweak any apk or jar files so far, there are rare things in the settings that may stop the process.
E.g. setting notfication sound of non existing Samsung Apps, as there are Samsungs Email and S Planner.
(Maybe this will result in a TODO list, if there's time and energy to tweak apk's)
- I decided to remove SetupWizard2013 (Samsung) & SetupWizard (Google) and blocked the processes
from being started by setting the build.prop variable ro.setupwizard.mode=DISABLED
I'm not sure about any flaws, though there might be some side effects (see next two issues).
- At some point i realized that the multiwindow mode has no effect anymore
- The edit button of the notification panel (upper right corner) is not working anymore
- You may notice some messages in logcat from McDaemon stating: Failed to obtain version info Mobicore...
This is a know issue on deodexed stock ROMs:
http://forum.xda-developers.com/showpost.php?p=43037197&postcount=9
Nfc payment will not work on deodex rom because of signature checks and looking for particular
odex and odex framework files.
(See 2nd post for a possible workaround)
Further advice:
- I really suggest to install VLC player from f-droid and check it out.
This app works pretty well and supports a lot of video formats.
It also serves video on an external monitor via MHL/HDMI!!
- Press the the menu button in the Data Usage settings and disable "auto sync data".
There's nothing to sync with and it will close some backup services running in background
- If you don't like background traffic or make the ROM even more "silent",
think about using a firewall like AFWall+ or restrict app access with Xposed+Xprivacy.
- You might easily encrypt email and files by using APG
Remark:
- There's nothing to worry about the pre-configured kernel image, but tweaking some of the init.*.rc files
would be a good thing to do .
- While using Koush's GPL'd Superuser i observed "Superuser granted to Shell" messages if an app is crashing.
Don't worry too much about it, the message will go away in a couple of seconds and i realized no strange issues.
From what i got so far is, that it might be related to kernel rights management or SElinux extension in specific.
https://github.com/nelenkov/cryptfs-password-manager/issues/5
- During testing i discovered a useful command to identify camera firmware.
On your dialer use *#34971539#
There are multiple threads covering secret codes already... i didn't knew this one before.
Further remarks:
- As Android "is" Google, it is not possible to block background traffic to Mountain View completely.
From time to time system apps use certain service ports to initiate transmissions.
I did not observe any Samsung related traffic anymore though.
Anyway, it was really interesting to observe the effects at certain milestones, while playing with this ROM.
- Users who like to share everything, like cloud services or like to sync all data with Google or Samsung,
should use another ROM.
- I don't like to disappoint you, but this ROM is only a shrinked down version of stock I9305XXUFNI3.
No blasting features, no extras, no special addons...
If you don't like it, tell me... but be polite.
If you like it, leave a comment or at least press thanks button!
O.k. enough talking.
CREDITS:
@kenar2 for his great work and modded Stock ROMs
@djb77 for some advice and also building awesome ROMs with a great user experience
@psndna88 for his extensive work on AGNi kernel
@Chainfire for developing a full featured Superuser
@Phil3759 for his work on PhilZ Touch CWM Advanced Edition and providing this great tool
Contributers at f-droid in general and all the curious and openminded people here at XDA forum.
Have fun!
scholbert
Additional stuff...
Look:
Screenshots
As requested...
Wallpaper shameless taken from here:
http://wallpaperswiki.org/wallpaper-lines-lines-stream/
You'll find no copyright notes on this page... so hopefully it's o.k. for the creator to use it in a ROM :angel:
Removals:
See the text file attached (removals.txt).
Looks a bit ugly though, because i'm too lazy to format it :silly:
Addons:
See the text file attached (addons.txt).
This is only a file listing, tweaks are not included...
Specials:
Mobicore error message workaround (not implemented and tested yet):
- Prevent the start of mobicore service in file init.smdk4x12.rc by comment out these lines:
Code:
# mobicoreservice
mcDriverDaemon /system/bin/mcDriverDaemon -r /system/app/FFFFFFFF000000000000000000000001.drbin -r /system/app/mcRegistry/ffffffffd0000000000000000000000a.tlbin
class core
user system
group system
Enjoy!
scholbert
Further info...
I'm not a paranoid person, but i like privacy.
It would be nice, if users are aware of things going on on their mobile devices.
Information about remaining services (will try to keep this updated):
ResourceManager
A.k.a MyScript ResourceManager is related to handwriting recognition and pen writing.
This service was not removed, but could easily be disabled in Settings -> Application Manager
Search for MyScript Resource Manager in all applications and disable this service.
I observed some connections to Amazon servers, maybe MyScript makes use of Amazon's cloud service.
Reference:
https://dev.myscript.com/technology/
FixmoISA and MDMApp
The Samsung Knox platform provides Application Programming Interfaces for use by third-party vendors to develop tools to enable security controls required by the Samsung Knox Android STIG. APIs include:
The Mobile Device Management API includes more than 500 policies and 1100 interfaces to be called by any MDM agent.
A vendor can implement an MDM solution that can meet or exceed requirements.
Vendors implementing MDM API include Mobile Iron, AirWatch, SOTI, and Fixmo.
The Integrity Services Layer (ISL) provides an interface that allows third party vendors to implement an Integrity Services Agent (ISA) to communicate with the on-device MDM agent.
The agent provides on-device scanning for integrity failures and reports results to the MDM server.
Solutions implementing the ISL include Fixmo ISA.
The MDM API includes VPN policies and interfaces to allow an administrator to configure third-party IPSec VPN solutions implementing the MDM interfaces.
This enables the device to connect to DoD networks using a FIPS 140-2 validated cryptographic module to protect data in transit.
Solutions that implement the MDM interface include Mocana KeyVPN and Inside Secure VPN.
The Smart Card API provides an interface that allows third party vendors to implement smart card reader functionality,
enabling Samsung Knox Android to support the DOD Common Access Card for PKI, including user authentication, S/MIME digital signatures, and device unlock.
Solutions that implement this interface include the Biometrics Associates Bluetooth Smart Card Reader.
Reference:
http://gcn.com/articles/2013/05/29/breakdown-dod-security-controls--ios-android.aspx?m=1
http://www.businesswire.com/news/ho...oration-Samsung-Enhanced-Support#.VNIIpSyhymw
OmaCP and OmaDrmPopup
OMA Client Provisioning is a device management protocol specified by the Open Mobile Alliance (OMA) Device Management (DM) Working Group.
The OMA CP protocol covers WAP provisioning with minimal user interaction, typically over-the-air or via SIM Card.
Reference:
http://en.wikipedia.org/wiki/OMA_Client_Provisioning
http://technical.openmobilealliance...-information/release-program/current-releases
Don't be evil...
scholbert
scholbert said:
I'm not a paranoid person, but i like privacy.
It would be nice, if users are aware of things going on on their mobile devices.
Information about remaining services (will try to keep this updated):
FixmoISA and MDMApp
The Samsung Knox platform provides Application Programming Interfaces for use by third-party vendors to develop tools to enable security controls required by the Samsung Knox Android STIG. APIs include:
The Mobile Device Management API includes more than 500 policies and 1100 interfaces to be called by any MDM agent.
A vendor can implement an MDM solution that can meet or exceed requirements.
Vendors implementing MDM API include Mobile Iron, AirWatch, SOTI, and Fixmo.
The Integrity Services Layer (ISL) provides an interface that allows third party vendors to implement an Integrity Services Agent (ISA) to communicate with the on-device MDM agent.
The agent provides on-device scanning for integrity failures and reports results to the MDM server.
Solutions implementing the ISL include Fixmo ISA.
The MDM API includes VPN policies and interfaces to allow an administrator to configure third-party IPSec VPN solutions implementing the MDM interfaces.
This enables the device to connect to DoD networks using a FIPS 140-2 validated cryptographic module to protect data in transit.
Solutions that implement the MDM interface include Mocana KeyVPN and Inside Secure VPN.
The Smart Card API provides an interface that allows third party vendors to implement smart card reader functionality,
enabling Samsung Knox Android to support the DOD Common Access Card for PKI, including user authentication, S/MIME digital signatures, and device unlock.
Solutions that implement this interface include the Biometrics Associates Bluetooth Smart Card Reader.
Reference:
http://gcn.com/articles/2013/05/29/breakdown-dod-security-controls--ios-android.aspx?m=1
http://www.businesswire.com/news/ho...oration-Samsung-Enhanced-Support#.VNIIpSyhymw
OmaCP and OmaDrmPopup
OMA Client Provisioning is a device management protocol specified by the Open Mobile Alliance (OMA) Device Management (DM) Working Group.
The OMA CP protocol covers WAP provisioning with minimal user interaction, typically over-the-air or via SIM Card.
Reference:
http://en.wikipedia.org/wiki/OMA_Client_Provisioning
http://technical.openmobilealliance...-information/release-program/current-releases
Don't be evil...
scholbert
Click to expand...
Click to collapse
Can you post screenshot of rom?
I don' have idea how it is
Hi andreazimba!
andreazimba said:
Can you post screenshot of rom?
I don' have idea how it is
Click to expand...
Click to collapse
I will add a screenshot in 2nd post tomorrow.
There's nothing special with the look... just stock TouchWiz and custom wallpaper
Cheers,
scholbert
Nice work on the ROM
The NI3 base is a bit old though. I can share with you a cleanly built NL1 if you would like to use that (with SU, BuxyBox, Deodexed + Zipaligned).
With that Mobicore fix, is that a kernel-related fix? If so I can patch my existing modded version of AGNi.
Hi djb77!
djb77 said:
Nice work on the ROM
Click to expand...
Click to collapse
Thanks a lot for this positiv feedback!
djb77 said:
The NI3 base is a bit old though. I can share with you a cleanly built NL1 if you would like to use that (with SU, BuxyBox, Deodexed + Zipaligned).
Click to expand...
Click to collapse
Yeah you're right, it's not the latest...
The reason i started with this release is quite simple.
I once extracted an EXT4-image from the original UFNI3 firmware and started investigation based on this ROM.
It's o.k. for me, because i did not realize any major bugs or malfunction.
The UFNI3 modem gave got quality as well.
But anyway, it's a nice offer and i may come back to it :fingers-crossed:
... and i'll try to find some change notes for the latest stock ROMs as well.
djb77 said:
With that Mobicore fix, is that a kernel-related fix? If so I can patch my existing modded version of AGNi.
Click to expand...
Click to collapse
We better not call it a fix... it is a ramdisk workaround and it was my best guess, that it might prevent the error message coming from McDaemon.
But if i look at the snippet in my post again, this entry is the call of mcDriverDeamon, which seems to be a different tool to load proprietary stuff before the upper service get's started
BTW it has to be checked if blocking the Mobicore service would harm NFC in any way.
If so it would be better to accept the errors in logcat or try to search for a real fix.
Do you know, if odexed and deodexed may live together in harmony?
Maybe it's worth a try to move the original NFC files (apk+odex) to the ROM and see what happens.
The signature of security check should match then...
Anyway this not my focus of work right now.
Thanks again for the feedback and have nice day!!!
scholbert
Deodexing sholdn't break files, but it would be often best to have all your files one way or another (odex or deodex)
djb77 said:
Deodexing sholdn't break files, but it would be often best to have all your files one way or another (odex or deodex)
Click to expand...
Click to collapse
Deodexing will not break files from a functional view, that's correct...
... but re-assemble odexed files (apk+odex) to a deodexed package (apk only) will do from the binary point of view.
So if there's an integrity check of apk+odex with some security mechanism/checksum before loading contents to memory a deodexed file will break this check. That's at least what i conclude from the thread i refered to in my first post.
Anyway i dont' know enough about the Mobicore Daemon, so it's just guessing how it interacts with all the proprietary files.
Another perhaps more simple question is about camera firmware:
I made a dump of camera firmware by dialing *#34971539# and press the dump button.
Does anyone know at which location this file gets stored afterwards???
And finally.. :
While looking into the init files of AGNi ramdisk, i stumbled over these mount commands in init.agnimounts.rc (snippet):
Code:
...
mount ext4 /dev/block/mmcblk0p13 /system ro wait noatime nodiratime nosuid nodev discard
mount f2fs /dev/block/mmcblk0p13 /system ro wait noatime nodiratime nosuid nodev discard,background_gc=off,inline_xattr,active_logs=2
...
I know that psndna88's pureSTOCK have f2fs support compiled in (that's at least what i assume after i looked into his config).
Is it common practice to mount f2fs over ext4 filesystem
... mmmh, think i'm going of topic a little bit
Best regards,
scholbert
Camera firmware gets dumped to /data/cfw if I'm correct.
My friend MaHo_66 has actually come up with a patch which can be included into ROMs Check out this post HERE, you should be able to use these files in your ROM (just give MaHo_66 credit obviously).
F2FS I can't help you with, never used it or really looked into it
Hey djb77,
thanks again for your help!
djb77 said:
Camera firmware gets dumped to /data/cfw if I'm correct.
Click to expand...
Click to collapse
Got that folder, but no dump inside... maybe i'll start some further investigation.
Apart from that my camera works very well, with this ROM, its just for educational purpose
djb77 said:
My friend MaHo_66 has actually come up with a patch which can be included into ROMs Check out this post HERE, you should be able to use these files in your ROM (just give MaHo_66 credit obviously).
Click to expand...
Click to collapse
Yeah thanks for the hint, i knew that patch/collection already... don't know if it's useful for me right now.
Depends on people's reports... if there are any
djb77 said:
F2FS I can't help you with, never used it or really looked into it
Click to expand...
Click to collapse
No problem, i guess i already found out.
Both filesystems need a single mount to be accessed.
Depending on the filesystem of the partition in use, one of the commands will succeed, the other one would always fail.
So this "double" entry will always match, wether you use ext4 or f2fs on your partitions.
Seems that psndna88 decided this would be the easiest way to support both filesystems.
Regards,
scholbert
Hi,
not sure if anyone even tested my release, might be a bit too stripped down for most.
Maybe i'm little late with this ROM and most people already jumped to Lollipop ROMs.
Anyway, i'm testing for a few weeks now and the ROM still behaves rock solid.
In the meantime i made an AnTuTu bench as well and reached a score of ~26394, which is not that bad for a stock based ROM i guess.
Battery time is still nice, while wireless networks (WiFi, 3G/LTE) are the most hungry suckers
Though there's less interest, i think about updating to the latest 4.4.4 release and give the ROM a few additional tweaks as well.
I guess i'll integrate my own boot.img with a customized kernel including the offline charging fix (kernel will be based on psndna88's sources).
No need to hurry though
Rock on!
scholbert
RazvanG said:
not on stock froyo, no
Click to expand...
Click to collapse
i am going to try this rom , man. seems very good rom.
how do you compare the battery life of your rom to the original stock rom?
Sent from my GT-I9305 using XDA Free mobile app
scholbert said:
Hi,
Though there's less interest, i think about updating to the latest 4.4.4 release and give the ROM a few additional tweaks as well.
I guess i'll integrate my own boot.img with a customized kernel including the offline charging fix (kernel will be based on psndna88's sources).
No need to hurry though
scholbert
Click to expand...
Click to collapse
as long as xposed is halway useless on LP, I'll personally stick to KitKats
if in doubt, I'm really interested in testing your new release - actually I'm pretty much tired with wealth of options in stock and stock derivated roms - when I was testing a CM11 build the only things I really missed from Touchwiz were stock multiwindow and stock camera
Hey thanks for your feedback!
anguslaw said:
i am going to try this rom , man. seems very good rom.
how do you compare the battery life of your rom to the original stock rom?
Click to expand...
Click to collapse
Mmmh, got no direct comparison.
Anyway as this is stock kernel, but with reduced background services and other stuff removed, there might be only a slight difference.
Background services may have significant influence on battery life if connected to the network.
Judge yourself... but keep in mind that Google services are completely removed in this ROM.
adamuadamu said:
as long as xposed is halway useless on LP, I'll personally stick to KitKats
if in doubt, I'm really interested in testing your new release - actually I'm pretty much tired with wealth of options in stock and stock derivated roms - when I was testing a CM11 build the only things I really missed from Touchwiz were stock multiwindow and stock camera
Click to expand...
Click to collapse
AFAIK multiwindow is non-functional in this release. You could set it in the settings, but the drawer is not showing up on home screen.
Tried to find out what happened or which part is missing, but no fix right now. Maybe HelpHub.apk is required, because i found some referals in the apk.
As i did not use MultiWindow it in the past, i don't miss it.
Anyway, camera works nice, found no flaws here :good:
Xposed for Lollipop has been created, but i guess you're looking for specific modules, which are not working right now...
Development for Xposed on LP has just begun :fingers-crossed:
Regards,
scholbert
i have tried it out this afternoon. very smooth and clean. but i find that i just cannot live without google. all my contact was sync to google. and i rely on google plus photos to autoback up my photos.
Sent from my GT-I9305 using XDA Free mobile app
is this rom continous update or not??