Sorry for my English.
I tried all the rom, all, and no work for me either. Use two ext2 partitions for data and system. Using the latest zimage, haret and initrd 2.6.32, tested all options with default.txt
When I install, the first time, everything is right, but the second time I boot android, everything goes wrong. After installing, wait 15 minutes before touching anything.
What else I can try?
WM 6.1
radio 1.70.19.09
SD 8GB class6 with fat32, ext2, ext2, linuxswap
Thanks.
Go to NAND ?
vellowax said:
Go to NAND ?
Click to expand...
Click to collapse
Now prefer haret.
My bootlog.txt
** /dev/block/mmcblk0p1
** Phase 1 - Read FAT (compare skipped)
Attempting to allocate 7032 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Free space in FSInfo block (1093801) not correct (1078495)
Fix? yes
Next free cluster in FSInfo block (640022) not free
Fix? yes
1961 files, 119676 free (1078495 clusters)
sh: 2: unknown operand
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop1 is mounted
/dev/block/loop1: clean, 710/65536 files, 97021/262144 blocks
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop0 is mounted
/dev/block/loop0 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/loop0: 625/65536 files (12.8% non-contiguous), 19711/262144 blocks
My default.txt
#alloctest 0x2000
set RAMSIZE 0x08000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd initrd.lzma
#
# The following kernel parameters are useful
# ppp.nostart - Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
# lcd.density - Defaults to 160, 128 shows more on screen
#
set cmdline "ppp.nostart=0 pm.sleep_mode=0 lcd.density=120 mddi.width=240 mddi.height=320 no_console_suspend board-kaiser-keypad.atttilt=0 board-htckaiser.panel_type=2 hw3d.version=1 board-kaiser-battery.battery_capacity=2160 board-kaiser-battery.haret_divisor=2200 board_htckaiser.pmem_size=4 board_htckaiser.pmem_adsp_size=1 clock-7x00.a11=400"
boot
Please explain what goes wrong on the second boot.
What is showing on the screen at the end?
Everything you posted looks right, as far as I can see.
n2rjt said:
Please explain what goes wrong on the second boot.
What is showing on the screen at the end?
Everything you posted looks right, as far as I can see.
Click to expand...
Click to collapse
Thanks for your help.
On the second boot every few minutes installation screen appears (the rays forming X) and finally the screen turns white and kaiser does not respond and I have to go back to WM.
Can be the problem have installed this WM rom?
I can install android in NAND if that solve my problems, I like it android.
Sorry for my English.
Maybe when you turned off after the first boot, the filesystem was not cleanly dismounted. It might help to clear the dalvik cache during the boot, using the boot menu. To open the boot menu, push the middle of the screen when Linux starts to boot. Choose the option to clear the dalvik cache. When that finishes, choose the "Exit" option. I don't know, but it might help.
NAND will give fewer problems, but still has problems dismounting the filesystem cleanly when shutting down.
n2rjt said:
Maybe when you turned off after the first boot, the filesystem was not cleanly dismounted. It might help to clear the dalvik cache during the boot, using the boot menu. To open the boot menu, push the middle of the screen when Linux starts to boot. Choose the option to clear the dalvik cache. When that finishes, choose the "Exit" option. I don't know, but it might help.
NAND will give fewer problems, but still has problems dismounting the filesystem cleanly when shutting down.
Click to expand...
Click to collapse
Thanks, I'll do it again (clear dalvik cache), I tried it once after reading a lot, but did not help.
Clear dalvik cache but problems persist, now the kaiser after working a few hours, as before, the screen stays black and does not respond, back to WM.
At least now do not see the X and white screen. If everything is like most people, why do not I have the same results?
HOWTO: Change keymaps/update rootfs in neopeek ext2 buids
Today, I will show you how to change your phone keymaps (which buttons initiate different action) and fix wifi error in neopeek build (see bottom of post). Please read all instructions first before starting!!
Changing Keymaps
In the past,
-power button wake screen
-home button bring up menu
-center button is "enter"
-back button is back
-call initiate
-end button close screen
Updated ROOTFS contains:
-power button wake and close screen
-end button is end(can be change in spare parts hack)
-center button now menu
-home button is actually home button
If you're in linux, here are the steps:
1) plug in SD Card
2) Open ext2 partition
3) open init.etc folder
4) open keymaps folder
5) download latest rootfs here: http://files.xdandroid.com/rootfs/
; then download to desktop and rename to ROOTFS.IMG
6) mount with terminal, input these commands:
Code:
sudo mkdir ~/Desktop/ROOTFS
sudo mount -o loop ~/Desktop/ROOTFS.IMG
7) go to terminal and input:
Code:
sudo nautilus
8) with the augmented privileges file browser (the one you just opened), go to this directory: filesystem/home/<your user here>/Desktop/ROOTFS
9) Open init.etc in rootfs folder and then keymaps folder
10) copy all the files in keymaps folder to the directory /init.etc/keymaps on your ext2 partition.
Fixing Wifi Error
This also works if your wifi is not working after updating a kernel.
Replace contents of folder wifi (/init.ect/wifi) with one from latest rootfs..
I tested with an outdated build (SuperFroyo RC2) and it worked.
If you're in windows, see 3rd post!
Now you have new, updated keymaps (or fix wifi error) on your older rom!
Notice that newer neopeek ext2 roms have updated keymaps. If your android build already has the updated buttons, there is no need to update again.
Will try the procedure if for any reason I would decide to use builds other than frg83 RC5 where key map changes are already incorporated. Certainly very helpful for Android newbies like me.
If you're in Windows, you can use Ext2fs driver (google it) and Gizmo Drive software.
Before work: Install driver and software
1. Plug in SD
2. Mount rootfs.img in Gizmo Drive (or use Explorer context menu on Vista/7)
3. Modify layouts or character maps in /init.etc/
4. Unmount drive
That's all!
This also works if your wifi is not working after updating a kernel.
Replace contents of folder wifi (/init.ect/wifi) with one from latest rootfs..
I tested with an outdated build (SuperFroyo RC2) and it worked.
For those of you who have a seperate Ext2 partition and can therefor not modify the rootfs.img file, here's what to do:
1. Download Ext2Read
2. Extract the file Ext2Explore.exe somewhere. Right-click: "Run as administrator" (Vista/Windows 7)
3. You should now be able to browse the Ext2-partition on your device
You can then use Corias's instructions to mount a rootfs.img that you downloaded, for example to extract updated keymaps.
Ext2Read's the only software out of 3 that I tried (Ext2FSD, Ext2IFS and Ext2Read) that actually worked under Windows 7 and that managed to read the partition over USB.
I tested this using my pc running Windows 7 64bit and my Diamond (Diam100)
Script Version!
Code:
This time I present to you a script that will in theory (and so far for me, in reality) save us some battery without having to risk our hardware with undervolting! I present to you...
[B]CPU Sleeper[/B]
[QUOTE]Honestly the Script can be made to work with any Dual Core / Quad Core! The Only Problem is you need to be Rooted!
~ Currently the issue with CM9, is that the boot becomes incomplete while in init.d folder without Modification to the sysinit..
~ however, with any rooted device you can download the script & continue to use it via a script manager app on every boot.
~ With the Script Manager App, this script virtually can run on any Multi-Processor CPU
Hope that clears things Up,
~~Eugene[/QUOTE]
[U]What is it?[/U]
Its a fairly simple script that will put CPU 1 OFFLINE when the screen turns off. Once the screen comes back on, it will allow CPU 1 back ONLINE.
[U]How does it work?[/U]
Since we have dual core CPUs, we have a CPU 0 and a CPU 1, core 1 and core 2, while the screen is off we really only need to have 1 core active, this script will make sure CPU 1 shuts off while the screen is off, then resumes normal usage when the screen comes back on.
[B][COLOR="red"]WARNING! READ THIS![/COLOR][/B]
This script relies on init.d OR script manager! CM9, for some reason, tends to run this at the exact same time it runs some other script (I forget atm which) and it will clash, causing no boot! CM9 users MUST use the script manager version install! Flex Reaper appears to work fine with it as init.d. I strongly urge you to use the script manager version of this, NOT the flashable version. Always make a nandroid backup before modifying the system, including this!
[U][COLOR="Red"]Instructions[/COLOR][/U]
Available in 2 versions, script only version which you can place wherever you want and run however you want, or a CWM/TWRP flashable zip that will place the file for you in /system/etc/init.d and set permissions.
[I]Version 1: Flashable[/I]
Same as any of my flashable releases, I did most of the work for you!
Make a full backup
Download to external SD card
Install from SD card
Pick the cpu sleeper zip file
it'll be almost instant
reboot
Shouldn't be any need to clear caches or anything like that.
[I]Version 2: Script only[/I]
This can be run in 2 ways, via init.d support, or via script manager. Both are pretty similar, and can be done a number of ways, however this is the basis of how.
[U]Init.d supported kernel:[/U]
Make a backup!
Download the script file, making sure no extensions get added onto the file. Copy the file to /system/etc/init.d and set the permissions to the following:
XOX
XOX
XOX
Once done, reboot the system, and it will take effect when your system is finished rebooting.
[U]Script Manager[/U]
This method is probably the better method, and should work with any kernel/ROM. Download the script file, making sure no file extensions get added, and copy it to /system/etc. Set the file permissions to:
XOX
XOX
XOX
Once done, load up script manager, select browse as root (if it isn't already set from the crossix mod method in the guide) then browse to /system/etc and select the script file S98cpu_sleep, then select ROOT and BOOT options. After this is set, reboot system.
[U]What do I do if I can't boot after using this?[/U]
You made that backup, right? Ok, then here is what you do.
Hold the power button until the tablet powers off
Press and hold the volume down button, next to the screen lock switch
Press and hold Power (while holding volume down)
Once the recover kernel message comes up, release the buttons
In CWM go to advanced, mounts, mount system, then format system
In TWRP, go to wipe, then wipe system
In CWM go to restore, advanced restore, restore ONLY system
In TWRP select restore, then uncheck all so ONLY system is checked
After restoring system, wipe cache and dalvik cache, then reboot system.
System should boot normally.
[B]Downloads[/B]
Available in 2 versions, script only version which you can place wherever you want and run however you want, or a CWM/TWRP flashable zip that will place the file for you in /system/etc/init.d and set permissions.
Dual Core:
Download: [COLOR="Red"]Script Only - Recommend Install via Script Manager App[/COLOR]
[URL="http://d-h.st/N1N"]CPU Sleeper script only[/URL]
Quad Core:
Download: [COLOR="Red"]Script Only - Recommend Install via Script Manager App[/COLOR]
[url=http://www66.zippyshare.com/v/9249467/file.html]cpusleep[/url]
Thanks to [COLOR="DarkGreen"]pio_masaki[/COLOR] for rewriting the OP
App Version:
Code:
[B]CPU Sleeper[/B]
~Free to all Memebers
~ Must Be Rooted to use App
[B][COLOR="Blue"]What is it?[/COLOR][/B]
Its a fairly simple App that will put CPU 1/2/3 OFFLINE when the screen turns off. Once the screen comes back on, it will allow CPU 1/2/3 back ONLINE.
[B][COLOR="Blue"]How does it work?[/COLOR][/B]
Since we have Dual & Quad core CPUs, we have a CPU 0 and a CPU 1/2/3, core 0/1/2/3, while the screen is off we really only need to have 1 core active "CPU0", this App will make sure CPU 1/2/3 shuts off while the screen is off, then resumes normal usage when the screen comes back on.
[B][COLOR="Blue"]Compatibility?[/COLOR][/B]
Works with any Dual Core & Quad Core Devices!
~ICS
~Gingerbread
[B][COLOR="Blue"]Battery Saving?[/COLOR][/B]
Battery savings all depends on Usage & idle times.
[U][COLOR="Red"]Instructions[/COLOR][/U]
download the App, install & either manually run it, or set to run every boot-up
[B]Downloads[/B]
[url=http://www20.zippyshare.com/v/85067559/file.html]CPU Sleep.apk[/url]
Credits:
Handlerexploit for the creation of the App.
Curious as to why this was deleted and the CWM zip removed. ?
I'm also wondering if this will conflict in any way with a SetCPU profile I have for 'screen off' that limits CPU to 486 max, 384 min, ondemand. I set that up earlier today, just to see if there was any benefit, before flashing this.
Thanks for the link to the i9300 thread.
Now that I look at what's in the zip, I don't see an init.d folder in my /system/etc directory, so I'm guessing it did nothing when I flashed it? MOF, I searched the entire phone for "s98" and it returned nothing.
Looks like a double
Q&A for [KERNEL][AOSP/CAF][NOV 16] Glitch for Flo/Deb - r303
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][AOSP/CAF][NOV 16] Glitch for Flo/Deb - r303. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Root not working
Hello!
First of all :good: :good: :good: I am using your kernel more or less since I own the Nexus 7 (2013) in combination with Multirom and some custom ROMs, installed as secondary. It is working like a charm and I never saw any problems on "KK".
With "L" root is not (yet?) working for me. This might however been caused by the way of using it. I have two scenarios: 1.) "L" as secondary ROM and 2.) "L" as primary ROM. For both cases I used Tassadar's build. For the latter I copied the installed secondary ROM to the primary slot. With Tassadar's kernel I have root. When installing GlitchKernel root is gone. By flashing Tassadar's boot.img I regain root. As far as I can say right now this -- regaining root -- does not work for the secondary ROM.
To have it said: I also tried flashing GlitchKernel and Chainfire's SuperSU directly afterwards before rebooting with no effect. One thing I haven't tried is to NOT inject Multirom after flashing your kernel.
It would be great if you could help. If there is anything I could/should test, let me know!
Finally, my prayers are also with you!!!
Best Regards,
tungdil
@tungdil
Hello tungdil,
I'll start by asking what revision of Glitch are you running ?
r300 didn't come with root support out of the box, and it is required to flash a root-enabled boot.img (the ramdisk in it to be exact) prior to flashing r300 to enable the rooting technique of your choice (SELinux Permissive (potentially with system R/W access) or just Chainfire's partial root "trick"). Lollipop's security enhancements are modifying how root works for us (users), so until some kind of standard takes place I did want to wait and see.
However, considering many users didn't find that easy (either to understand or to find what boot.img to get for what result), I did release r303. This new revision comes with various ramdisk patches you can enable through Aroma to get anything from Chainfire's partial root to full root with SELinux Permissive, system partition R/W access and PIE bypassing (it will obviously lower Lollipop security though).
I'm using this new revision on primary and secondary roms using MultiROM with no rooting issue.
If you're running r300, get the r303 update. If you're already on r303, what apps are you running that won't get root access ? You may want to use more patches to "open the can".
Have a nice day !
Tk-Glitch said:
@tungdil
Hello tungdil,
I'll start by asking what revision of Glitch are you running ?
r300 didn't come with root support out of the box, and it is required to flash a root-enabled boot.img (the ramdisk in it to be exact) prior to flashing r300 to enable the rooting technique of your choice (SELinux Permissive (potentially with system R/W access) or just Chainfire's partial root "trick"). Lollipop's security enhancements are modifying how root works for us (users), so until some kind of standard takes place I did want to wait and see.
However, considering many users didn't find that easy (either to understand or to find what boot.img to get for what result), I did release r303. This new revision comes with various ramdisk patches you can enable through Aroma to get anything from Chainfire's partial root to full root with SELinux Permissive, system partition R/W access and PIE bypassing (it will obviously lower Lollipop security though).
I'm using this new revision on primary and secondary roms using MultiROM with no rooting issue.
If you're running r300, get the r303 update. If you're already on r303, what apps are you running that won't get root access ? You may want to use more patches to "open the can".
Have a nice day !
Click to expand...
Click to collapse
Hello Tk-Glitch!
Thanks a lot for your feedback! My feeling is I am doing something wrong because you wrote you don't have problems using it with MultiROM. But let me answer your questions:
Actually I tried both r300 and r303 using the following sequence:
"install" with TWRP (or delete and inject if it is the secondary ROM) the boot.img which is packaged with Tassadar's lrx21p_flo.zip. Note: I do have root afterwards
Flash GlitchKernel, reconfigure everything in the Aroma installer. Usually I don't use permissive mode or PIE Patch but have tried it as well with no success
Reboot, which results in not having root.
For the primary ROM: Re-install the Tassadasr's boot.img; which results in having root again.
That means, I start with a situation where root is working (btw. Kernel: 3.4.0-g0356b90-00001-gd0e79e3 [email protected] #240)! Yesterday I have also updated the bootloader to 04.04 with no effect. Just right now I tried it again and after flashing Glitch-N7-r303.zip (leaving all options as is but selecting PIE patch and permissive mode) the Kernel is: 3.4.0-Glitch-N7-AOSP-r303 [email protected] #1, dated 16.11.14 08:08:49 PST but I don't have root.
The following "apps" are not working AFWall+, MultiROM Manager, Reboot Menu Widget, and su itself if directly "called" from within Terminal Emulator. Just to have it said: ES File Explorer also won't work, but that's because it needs at least the PIE patch. The log of SuperSU tells, for example for AFWall+:
Code:
iptables v1.4.20: can't initialize iptables table ... : Permission denied
When I try launching su from the Terminal, SuperSU will ask to confirm root access even if I previously allowed root acces permanently. If I allow root nothing happens and the Terminal is "dead". The same applies for the other apps. I also tried this via an adb shell with the same effect, i.e. from the adb shell with root I'll see:
Code:
[email protected]:/ $ whoami
whoami: unknown uid 2000
1|[email protected]:/ $ su
[email protected]:/ #
and without
Code:
[email protected]:/ $ whoami
whoami: unknown uid 2000
1|[email protected]:/ $ su
i.e. the shell will not return.
Anything else I could test or check?
Best regards,
tungdil
Solved
Hello Tk-Glitch,
I "just" saw that Chainfire released an update to SuperSU (Beta 2.23) and ... that did it for both, primary and secondary ROM. I was on SuperSU Beta 2.19 before. My installation procedure for 2.23 was as follows:
Start with root NOT working for the primary ROM and working for the secondary ROM
For primary ROM use a TWRP queue for flashing GlitchKernel r303 and SuperSU Beta 2.23, and for the secondary ROM first flash GlitchKernel and then SuperSU
reboot and ... :good:
Notes:
currently not using the PIE patch when installing Glitch kernel, i.e. no root for ES File Explorer. All other apps I mentioned above do have root!
the same installation procedure did not work with SuperSU 2.19
Best regards!
tungdil
@tungdil
Hi again tungdil,
It's nice you got it sorted, though it convinces me something must be wrong with your installation process. Latest SuperSU is able to mod the ramdisk to enable root support (pretty similar to what Glitch r303 is supposed to do), so yes it works, though the question is why didn't it work with r303 for you ?
It may very well be an error on my side (I'll verify that), though it worked for me and most it seems, as you're the only one to encounter the issue since r303 release, or at least to talk about it. I checked my secondary ROM to be sure, but I'm indeed running SuperSU 2.19 on it.
By the way, injecting multirom shouldn't be required with Glitch, and leaving it checked will only lead to multirom detecting it's not needed and skip the injection (so basically you don't have to worry about it).
If you're okay, let me ask a few questions :
- Do you have screen timeout disabled in TWRP ? And if you don't, are you able to hit the reboot button after Glitch install ?
- What ROM are you running ?
- Could you please install r303 and save the installation log for me ?
- Could you please copy the /fstab.flo content from a ROM you got Glitch installed to for me?
- Why to use "delete and inject" for secondary ROM instead of "classic" install ?
Thank you !
Hello Tk-Glitch,
thanks a lot for your feedback and giving me the chance to learn something. I'll be happy to supply additional information:
- Do you have screen timeout disabled in TWRP ? And if you don't, are you able to hit the reboot button after Glitch install ?
Click to expand...
Click to collapse
The screen timeout in TWRP is not disabled but set to 300, and it is possible to hit the reboot button (or do something else before rebooting).
- What ROM are you running ?
Click to expand...
Click to collapse
As mentioned I am using the ROM which Tassadar has packaged (lrx21p_flo.zip).
- Could you please install r303 and save the installation log for me ?
Click to expand...
Click to collapse
Yes! I did a fresh install, i.e. added another secondary ROM and stored the LOG. Note: I didn't touch the "options" during install so everything was as preset. After GlitchKernel I flashed SuperSU 2.19 and verified via adb shell that root is not working.
Contents of the log (mr_update.zip.log.txt):
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : Glitch kernel
ROM Version : N7-AOSP
ROM Author : Tk-Glitch
Device : Nexus 7 (2013)
Start at : Wed Nov 19 21:24:46 2014
installing samsung updater extensions
Installing Glitch kernel...
Extract: /tmp/buildconfig.sh
Extract: /tmp/busybox
Extract: /tmp/compatibility.sh
Extract: /tmp/compatibility2.sh
Extract: /tmp/glitch-settings.conf
Extract: /tmp/systemcheck.sh
Cleaning up
about to run program [/tmp/systemcheck.sh] with 1 args
Installing system files for real.
Extract: /system/bin/fstrim
Extract: /system/etc/init.d/99glitchsetup
about to run program [/tmp/buildconfig.sh] with 1 args
about to run program [/tmp/busybox] with 4 args
Fluxi's MSM Hotplug enabled
Renaming binaries...
/system/bin/mpdecision -> mpdecision_bck
/system/bin/thermald -> thermald_bck
about to run program [/tmp/compatibility.sh] with 1 args
Extract: /tmp/abootimg
Extract: /tmp/cmdline.cfg
Extract: /tmp/edit_ramdisk.sh
Extract: /tmp/edit_ramdisk_permissive.sh
Extract: /tmp/fstab.tmp
Extract: /tmp/glitch.zImage
Extract: /tmp/max_oc.sh
Extract: /tmp/restore.sh
Extract: /tmp/sepolicy.tmp
Applying init settings
about to run program [/tmp/busybox] with 4 args
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.472290 seconds, 33.9MB/s
about to run program [/tmp/abootimg] with 6 args
writing boot image config in /tmp/bootimg.cfg
extracting kernel in /tmp/zImage
extracting ramdisk in /tmp/initrd.img
about to run program [/tmp/max_oc.sh] with 1 args
about to run program [/tmp/edit_ramdisk.sh] with 1 args
2372 blocks
CIF hack found!
about to run program [/tmp/abootimg] with 9 args
reading config file /tmp/cmdline.cfg
reading kernel from /tmp/glitch.zImage
reading ramdisk from /tmp/initrd.img
Writing Boot Image /tmp/boot.img
Glitching your device...
about to run program [/tmp/busybox] with 4 args
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.952729 seconds, 16.8MB/s
Finished!
script result was [Finished!]
Installer Sucessfull (Status 0)
End at : Wed Nov 19 21:24:49 2014
- Could you please copy the /fstab.flo content from a ROM you got Glitch installed to for me?
Click to expand...
Click to collapse
Yes, of course. Here we go ... Note: I compared this fstab.flo with a version from a secondary ROM which has root. They are in fact identical!
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-[CODE]
name/metadata
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc wait
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl1 /sbl1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl2 /sbl2 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl3 /sbl3 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/tz /tz emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/rpm /rpm emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/aboot /aboot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl2b /sbl2b emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl3b /sbl3b emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/tzb /tzb emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/rpmb /rpmb emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/abootb /abootb emmc defaults defaults
[/CODE]
- Why to use "delete and inject" for secondary ROM instead of "classic" install ?
Click to expand...
Click to collapse
Since Tassadar's boot image was working for me this was the easiest way. Just extract boot.img from lrx21p_flo.zip and use "delete and inject" for exchanging the boot image. Note: While writing this post I verified what I found yesterday, i.e. after flashing GlitchKernel and SuperSU 2.19 I do not have root. Flashing SuperSU 2.23 enables root. Reflashing Glitch and 2.19 leads to no-root again.
Best regards,
tungdil
Additional Information
Hello TK-Glitch,
it's me again
I did some further "research" in my secondary "L- ROMs" (the one I created for providing the information above and the one that does have SuperSU 2.23 installed and has root). I had a more detailed look on the boot images. In both cases your kernel is installed. I pulled the boot images using adb and unpacked them using unpackbootimg and then also unpacked the ramdisk. Binary the two images are not identical since the Glitch kernel configuration was slightly different:
Code:
console=ttyHSL0,115200,n8 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 l2_opt=1 vdd_uv=1 max_oc0=1728000 max_oc1=1728000 max_oc2=1728000 max_oc3=1728000 min_clock=384000 abc
v.s.
Code:
console=ttyHSL0,115200,n8 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 l2_opt=3 vdd_uv=3 max_oc0=1890000 max_oc1=1890000 max_oc2=1890000 max_oc3=1890000 min_clock=162000 abc
but I could not see any difference in the RAMdisk and the other main components dspite the fact that SuperSU 2.19 was used in one case and 2.23 in the other.
[EDIT] After reading TK-Glitch's next Post I realized that I made a mitsake and picked a wrong boot image when trying to compare so the following is wrong:
Tassadar's boot image is, of course, very different. One thing that I saw (because I remembered that SuperSU 2.23 "...fixes a number of SELinux policy issues...") is the difference in selinux-version. In Tassadar's image I find:
Code:
Android/aosp_flo/flo:5.0/LRX21M/scott11042320:userdebug/test-key
while your selinux_version says:
Code:
google/razor/flo:5.0/LRX21P/1570855:user/dev-keys
[/EDIT]
Maybe I am wrong but I think my problem was caused by the combination of Tassadar's build of the ROM and the Glitch kernel and, I was just lucky that the latest Beta of SuperSU helped curing it.
Best regards,
tungdil
Latest glitch and lollipop stock
I can't unlock many times the screen I have enable the swipe options
@tungdil
Thank you for your patience and researches tungdil !
The files SuperSU 2.23 would modify are most likely init.rc and sepolicy I guess. These are the two only files Glitch is potentially patching in the extracted ramdisk(from the current boot.img) when using root settings (fstab.flo is for F2FS partition mounting). Glitch doesn't come with its own ramdisk to enhance compatibility and will instead extract the current one, patch it with the options you've selected then repack it with the Glitch zImage in a new boot.img that'll be flashed at the end of the Aroma installer script. The selinux_version you have came either with the rom's default kernel or the previous kernel you flashed, not from Glitch itself.
I did ask in my previous post what ROM you were using because I thought you weren't using the same one both as internal and secondary. I may be right in thinking they're not the same when I'm looking at your selinux_version files content if you didn't switch kernels. You know what you did anyway.
It could indeed very well be something in Tassadar's build or some ramdisk changes he made breaking my patches. I didn't test his rom thinking that after an AOSP built rom and the official Google image were both getting root for me after applying Glitch it would work for every other AOSP based Lollipop roms. I may have been wrong.
I'll check Tassadar's build and search for a fix. Thanks again tungdil !
Hi again, Tk-Glitch!
Thanks for your comments! I appreciate having the chance to learn something.
.. the selinux_version you have came either with the rom's default kernel or the previous kernel you flashed, not from Glitch itself.
Click to expand...
Click to collapse
Oh, I see! I should have had a closer look at your flashable zip. After doing so, and looking into what "I found" I had to realize I made a mistake in picking the wrong boot image for the analysis (I have multiple secondary ROM's installed) In fact the selinux_version is, of course, the same (google/razor/flo:5.0/LRX21P/1570855:user/dev-keys) before and after flashing Glitch kernel.
I did ask in my previous post what ROM you were using because I thought you weren't using the same one both as internal and secondary
Click to expand...
Click to collapse
They should be the same (as mentioned forget about selinux-version I guess it was just too late yesterday night).
I tried to explain how I installed the ROM in my first post: "... For both cases [secondary and primary ROM] I used Tassadar's build. For the latter [primary] I copied the installed secondary ROM to the primary slot [using TWRP] ...".
If there is anything else I could do to help let me know! I'd be more than happy.
Best regards,
tungdil
@tungdil
I can understand better now, thanks for the confirmation.
My english is pretty limited to be honest so I may be understanding things wrong sometimes. I can also feel that I'm not able to express fully what I'd like to from time to time. It can be another limiting factor in some cases where my explanations or questions could be unclear for someone speaking better than I am.
I didn't find the time yet to check for Tassadar's build so I'm not in need for more for now. I'll get back to you as soon as I've made some progress on the matter - even if it's just to keep you informed - as it could also help someone else.
Thank you for your support and dedication.
Have a nice day tungdil
W.O.W
Thank you for this kernel!! It turns my adreno 320 to adreno 330
I'm on Lollipop (stock,rooted) and I'm having ghost touches with the latest version of glitch installed. I had an older version installed when I was on PA 4.6 but I did not have this issue. Any solutions?
Hey @Tk-Glitch,
First of all i want to say thank you for this wonderful Kernel .
I'm using the r307 Glitch Kernel in combination with Stock 5.0.2 rooted Rom.
The perfomance ist just awesome, unfortunately the battery is draining to quick compare to stock Kernel.
I would to ask what setup you're running and which settings you use. With CPU 1700mhz and GPU 450mhz i hardly reach 4-5 hours Sot of normal web browsing. Could you or anybody recommend me your personel settings.
Thank you in advance .
pranauk said:
I'm on Lollipop (stock,rooted) and I'm having ghost touches with the latest version of glitch installed. I had an older version installed when I was on PA 4.6 but I did not have this issue. Any solutions?
Click to expand...
Click to collapse
Strange to say the least since you didn't have issues previsouly. I've seen ghost touches on a friend's N7 and the only true fix was unplugging and replugging the display cable on the motherboard. BTW, ghost touches are almost always linked to the bad manufacturing of the N7.
I don't have any myself, on both r306 and r307, but my tab was never affected.
pk-sanja said:
Hey @Tk-Glitch,
First of all i want to say thank you for this wonderful Kernel .
I'm using the r307 Glitch Kernel in combination with Stock 5.0.2 rooted Rom.
The perfomance ist just awesome, unfortunately the battery is draining to quick compare to stock Kernel.
I would to ask what setup you're running and which settings you use. With CPU 1700mhz and GPU 450mhz i hardly reach 4-5 hours Sot of normal web browsing. Could you or anybody recommend me your personel settings.
Thank you in advance .
Click to expand...
Click to collapse
My battery is lasting much longer since Lollipop, so you may want to check for wakelocks.
These days I'm using 1.7GHz CPU, 600MHz GPU, -75mV on each CPU step, -100mV on each GPU step, ondemand governor, Glitchy L2/cache OC, and S2W/DT2W disabled.
Hope it helps !
@Tk-Glitch
Thank you for your answer Tk-Glitch, i will check the wakelocks.
And thank you for sharing your setup,
i will test it in my device. May you share how much mw Volt you need for 1,7Ghz and how i undervolted -100mw on GPU in all steps?
pk-sanja said:
@Tk-Glitch
Thank you for your answer Tk-Glitch, i will check the wakelocks.
And thank you for sharing your setup,
i will test it in my device. May you share how much mw Volt you need for 1,7Ghz and how i undervolted -100mw on GPU in all steps?
Click to expand...
Click to collapse
Of course mate.
My CPU needs 1.025V for 1.7GHz (PVS 3). For the GPU, I did make the GPU undervolting selectable (for all steps at once) in Aroma. You can tweak the values in the glitch script (init.d) if needed.
@Tk-Glitch
I see very nice , mine does 1050mV in 1,7Ghz not much differenc. Ups my mistake i thought the GPU undervolting in Aroma Installer is behaving like the CPU undervolting, only for the lowest Frequenz.
Thank you very much for you time, at home i will do a full factory reset and flash your kernel of top with the settings.
Have a nice day Tk-Glitch.
@pk-sanja
My pleasure.
Have a nice day as well pk-sanja