Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
GSM (n5100)
Wifi (n5110)
LTE (n5120)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Big thanks to @nickdollahz for his support and debugging with touch
Nice. Finally got an updated port. Also we have official N5100/N5110 Cyanogenmod support now. So it might be easier to port using the official source. Great work. Gonna test it right now. Also only need to change asserts and it should work fine for n5110 since they have the same mount points.
Edit: Just Flashed... Touch is not working properly. Need to Flip the touch screen drivers.
nickdollahz said:
Nice. Finally got an updated port. Also we have official N5100/N5110 Cyanogenmod support now. So it might be easier to port using the official source. Great work. Gonna test it right now. Also only need to change asserts and it should work fine for n5110 since they have the same mount points.
Edit: Just Flashed... Touch is not working properly. Need to Flip the touch screen drivers.
Click to expand...
Click to collapse
Ah, I will try to compile with flipping things
What I did with TWRP was to build with these flags:
RECOVERY_TOUCHSCREEN_FLIP_Y := true
RECOVERY_TOUCHSCREEN_SWAP_XY := true
or u can edit the kernel:
Swap Max_x and max_y and set swap_xy and invert_y to true.
/arch/arm/mach-exynos/kona-input.c
Code:
static struct synaptics_platform_data synaptics_ts_pdata = {
.gpio_attn = GPIO_TSP_INT,
.max_x = [STRIKE]799[/STRIKE] 1279,
.max_y = [STRIKE]1279[/STRIKE] 799,
.max_pressure = 255,
.max_width = 100,
.x_line = 26,
.y_line = 41,
.swap_xy = [STRIKE]false[/STRIKE] true,
.invert_x = false,
.invert_y = [STRIKE]false[/STRIKE] true,
#if defined(CONFIG_SEC_TOUCHSCREEN_SURFACE_TOUCH)
.palm_threshold = 28,
#endif
.set_power = synaptics_ts_set_power,
.hw_reset = synaptics_ts_reset,
.register_cb = synaptics_ts_register_callback,
#if defined(CONFIG_TOUCHSCREEN_SYNAPTICS_S7301_KEYLED)
.led_control = synaptics_ts_led_control,
.led_event = false,
#endif
#if defined(CONFIG_TOUCHSCREEN_SYNAPTICS_S7301_KEYS)
.button_map = &synpatics_button_map,
.extend_button_map = &synptics_extend_button_map,
.support_extend_button = false,
.enable_extend_button_event = false,
#endif
};
Update 6.01.2
Give feedback if it fixed touch
It is not flipped correctly. Pressing top hit bottom.
You can contact me and I can test the builds in real time if you want until u get the touch working but looks like u didnt flip the y axis.
nickdollahz said:
It is not flipped correctly. Pressing top hit bottom.
You can contact me and I can test the builds in real time if you want until u get the touch working but looks like u didnt flip the y axis.
Click to expand...
Click to collapse
I did flip y
Will compile a version with debugging code enabled and pm you
Work Also with N5110 ?
Inviato dal mio GT-N7100 con Tapatalk 2
If you flip axis AromaFM will have wrong touch orientation.
Landscape touch will be fixed on p31XX using this in init.rc (or "recovery/root/init.recovery.espresso.rc" in our case maybe this will fix it for you too.
Code:
# Set touchscreen to landscape mode for recovery
write /sys/devices/virtual/sec/tsp/pivot 0
this will set touchorientation from portrait to landscape.
---------- Post added at 11:05 PM ---------- Previous post was at 11:03 PM ----------
(if recovery got compiled without using flip or switch flags)
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
. @nickdollahz can try flashing AromaFM in TWRP to see if touch is right there too, if not try my solution.
simo.scorpion said:
Work Also with N5110 ?
Inviato dal mio GT-N7100 con Tapatalk 2
Click to expand...
Click to collapse
It will work for the N5110 but the proper asserts need to be set first or u will have to modify the updater scripts.
Android-Andi said:
If you flip axis AromaFM will have wrong touch orientation.
Landscape touch will be fixed on p31XX using this in init.rc (or "recovery/root/init.recovery.espresso.rc" in our case maybe this will fix it for you too.
Code:
# Set touchscreen to landscape mode for recovery
write /sys/devices/virtual/sec/tsp/pivot 0
this will set touchorientation from portrait to landscape.
---------- Post added at 11:05 PM ---------- Previous post was at 11:03 PM ----------
(if recovery got compiled without using flip or switch flags)
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
. @nickdollahz can try flashing AromaFM in TWRP to see if touch is right there too, if not try my solution.
Click to expand...
Click to collapse
The Touch drivers are in portrait mode but the framebuffer is in landscape mode. This is a Galaxy Note 8 problem. Since Aroma and the recovery touch are implemented separately. The solution I use when I ported TWRP was fixing the recovery at the kernel level. If you made the changes I posted earlier and compiled TWRP both TWRP and Aroma will work. properly. This is what I did with my TWRP port with working Aroma. I later shared this with civato for his CWM port which also included an older version of PhilZ he had worked on earlier.
I already know the solution just I dont have the source to fix it. All that needs to be done is do the source modification and compile it normally. or you can try flipping them both in aroma and in the recovery using the build flags.
So to be clear without any modifications both Aroma and every touch screen based recovery have messed up drivers. Solution is to flip them at the kernel level or try and flip them independently for aroma and the recovery.
Phil3759 said:
I did flip y
Will compile a version with debugging code enabled and pm you
Click to expand...
Click to collapse
Looking forward to this PM.
nickdollahz said:
It will work for the N5110 but the proper asserts need to be set first or u will have to modify the updater scripts.
The Touch drivers are in portrait mode but the framebuffer is in landscape mode. This is a Galaxy Note 8 problem. Since Aroma and the recovery touch are implemented separately. The solution I use when I ported TWRP was fixing the recovery at the kernel level. If you made the changes I posted earlier and compiled TWRP both TWRP and Aroma will work. properly. This is what I did with my TWRP port with working Aroma. I later shared this with civato for his CWM port which also included an older version of PhilZ he had worked on earlier.
I already know the solution just I dont have the source to fix it. All that needs to be done is do the source modification and compile it normally. or you can try flipping them both in aroma and in the recovery using the build flags.
So to be clear without any modifications both Aroma and every touch screen based recovery have messed up drivers. Solution is to flip them at the kernel level or try and flip them independently for aroma and the recovery.
Looking forward to this PM.
Click to expand...
Click to collapse
I did not modify kernel sources
I just sent you a PM with a link to a debug version
Follow instructions in PM and send me the log
That version has Swapped XY and Flipped Y
Let's see what's missing :good:
@Phil3759 please build your incredible recovery also for N5110!! THX
nickdollahz said:
What I did with TWRP was to build with these flags:
RECOVERY_TOUCHSCREEN_FLIP_Y := true
RECOVERY_TOUCHSCREEN_SWAP_XY := true
or u can edit the kernel:
Swap Max_x and max_y and set swap_xy and invert_y to true.
/arch/arm/mach-exynos/kona-input.c
Code:
static struct synaptics_platform_data synaptics_ts_pdata = {
.gpio_attn = GPIO_TSP_INT,
.max_x = [STRIKE]799[/STRIKE] 1279,
.max_y = [STRIKE]1279[/STRIKE] 799,
.max_pressure = 255,
.max_width = 100,
.x_line = 26,
.y_line = 41,
.swap_xy = [STRIKE]false[/STRIKE] true,
.invert_x = false,
.invert_y = [STRIKE]false[/STRIKE] true,
#if defined(CONFIG_SEC_TOUCHSCREEN_SURFACE_TOUCH)
.palm_threshold = 28,
#endif
.set_power = synaptics_ts_set_power,
.hw_reset = synaptics_ts_reset,
.register_cb = synaptics_ts_register_callback,
#if defined(CONFIG_TOUCHSCREEN_SYNAPTICS_S7301_KEYLED)
.led_control = synaptics_ts_led_control,
.led_event = false,
#endif
#if defined(CONFIG_TOUCHSCREEN_SYNAPTICS_S7301_KEYS)
.button_map = &synpatics_button_map,
.extend_button_map = &synptics_extend_button_map,
.support_extend_button = false,
.enable_extend_button_event = false,
#endif
};
Click to expand...
Click to collapse
Just sent you a PM with a new build
I will implement your kernel fix since it seems it won't mess other smdk devices (only a kona driver it seems)
However, I want to first fix the recovery touch code
Many many thanks for all your help :good:
I dont think it is your recovery code. All touch recoveries have the issue. It is Galaxy Note 8 related. Even the Note 10.1 doesn't have that problem. I suppose it has something to do with it being a phone that sometimes acts like a tablet. The kernel fix is a dirty fix that I came up with but it works on all the Note 8 variants. There is probably a more elegant way to put the device touch screen drivers in landscape mode but I have not discovered it yet.Testing new build now.
Update 6.01.9
Mainly fixes touch, big thanks to @nickdollahz for his support
If it is fine, I will release n5110 and try to fix touch at the kernel level this time, to get you a working aroma
By the way, do I need to flip things also for N5110?
N5110
http://d-h.st/users/philz_touch/?fld_id=29535#files
Thanks Phil....i try in the afternnon
Inviato dal mio GT-N7100 con Tapatalk 2
Phil3759 said:
By the way, do I need to flip things also for N5110?
Click to expand...
Click to collapse
hi phil3759
just tested it and it needs to rotate 90 clockwise for aroma file manager
besides, the back key did not function with aroma too
simo.scorpion said:
@Phil3759 please build your incredible recovery also for N5110!! THX
Click to expand...
Click to collapse
It seems to be on the way!
Phil3759 said:
By the way, do I need to flip things also for N5110?
Click to expand...
Click to collapse
Yes, you will need to. Recovery for n5100 and N5110 are identical besides the assert stuff since they share the same mount point. N5100 is the 3g and N5110 is the wifi only version. The kernel fix will work for both devices.
Related
This is a CM10 Official nightly patcher for SU660
this patcher automatically fix for SU660 stuff
- fix updater-script for CWM5 of SU660
- fix partition number from 9 to 10 in the vold.fstab
- fix HOME key in the Generic.kl gpio-keys.kl
and you can select kernel for SU660
- normal kernel (152MB carveout)
- 112MB carveout kernel
- 1500MHz overclocked kernel with OV/UV feature. (Please see attached files for kernel developer. It could be used for P990)
this kernel is based on the lge-kernel-star (jellybean branch) managed by arcee
https://github.com/CyanogenMod/lge-kernel-star
you can also select wireless.ko module (Experimental. DEEP SLEEP enabled)
Installation
0. official ICS users have to downgrade to the GB firmware.
1. extract this fixer (fixall.bat is the main batch file)
2. download CM10 nightly zip and copy it into extracted folder
3. drop zip onto fixall.bat (zip and batch file must be in the same location)
4. cm-10*-su660-fixed.zip will be obtained.
5. install cm-10-*fixed.zip in the CWM
6. install gapps jellybean version.
the latest patcher will be uploaded at the openstar2x project home.
http://code.google.com/p/openstar2x/downloads/detail?name=su660-cm-nightly-v0.8.zip
http://code.google.com/p/openstar2x/downloads/detail?name=su660-cm-nightly-v0.9.zip to fix HOME key for the cm10 nightly 20121103 update
http://code.google.com/p/openstar2x/downloads/detail?name=su660-cm-nightly-v0.10.zip limit max clock for overclocked kernel
http://code.google.com/p/openstar2x/downloads/detail?name=su660-cm-nightly-v0.12.zip fixed BSOD of overclocked kernel
http://code.google.com/p/openstar2x/downloads/detail?name=su660-cm-nightly-v0.13.zip latest cm10 fix merged (wireless.ko fix by amcee included)
http://code.google.com/p/openstar2x/downloads/detail?name=su660-cm-nightly-v0.14.zip enable PM_MAX for wireless.ko to fix battery problem / force TZ value
Please see also the official announcement of CM10 nightly by arcee
http://forum.xda-developers.com/showthread.php?t=1964240
ChangeLog
● set noauto_da_alloc correctly in order for I/O speed (11/05)
● gpio-keys.kl added to fix HOME key (11/04)
● fixboot script added to fix ramdisk (11/04)
● set maximum clock speed for overclocked kernel (11/04)
kernel ChangeLog
● fixed BSOD of overclocked kernel (11/06)
● fixed initial bootlogo corruption (11/06)
● limit max speed at boot time (11/04)
● ZRAM+snappy
kernel option changes
● CONFIG_SWP_EMULATION remove
● set deadline I/O scheduler by default
kernel patches
● ramhack patch: http://forum.xda-developers.com/showpost.php?p=33298583&postcount=177
- additional fix to use this patch for CM10 http://forum.xda-developers.com/showpost.php?p=33993473&postcount=636
● BSOD fix: http://forum.xda-developers.com/showpost.php?p=33764329&postcount=18
FAQ
reserved
Thanks wkpark. You simply rock
I just used the kernel posted at aragorn7 thread and it works well. Now things seem better
+1
Sir Anything for p990?
haha! now p990's users come here on hoping of a custom kernel! su660 rocks. you rock wkpark!
---------- Post added at 01:39 AM ---------- Previous post was at 01:36 AM ----------
the wireless module with DEEP SLEEP enabled will fix the battery drain by wifi, right?
Wkpark really rocks Coz he's most talented Dev of LG ..Master of Android
i really want to click the thank button 100000000 times!
Very good, thank you so much
thank! very nice work
but i can not use home key with 3/11 build, i chosen normal kernel.
Hi Wkpark..
Sorry for off topic.
.
Can we get inline call recording for our kernel ?
I asked this queation in many threads but no answer..
Hope you will.
aries.1482 said:
thank! very nice work
but i can not use home key with 3/11 build, i chosen normal kernel.
Click to expand...
Click to collapse
the v0.9 out to fix HOME key.
some keyboard layout added and it has no HOME key entry.
so I just add HOME key to newly added 'gpio-keys.kl' layout.
4ever1lov3 said:
the wireless module with DEEP SLEEP enabled will fix the battery drain by wifi, right?
Click to expand...
Click to collapse
I don't know exactly but the wireless kernel module is the reason of the faster battery drain and the DEEP SLEEP option just activated for experimental reason,
How i can running two kernel hack RAM and OC CPU 1500MHz in parallel?
hi wpark can you port this for the P990 or we need to wait another dev? thank you for you work
currently working on OC too. But couldn't get it to a stable state on my device and so left it. Then I found your patch and still not booting. So I believe my device can't handle it and so I'm leaving it for now Not really needed imho .. damn smooth
Benee said:
currently working on OC too. But couldn't get it to a stable state on my device and so left it. Then I found your patch and still not booting. So I believe my device can't handle it and so I'm leaving it for now Not really needed imho .. damn smooth
Click to expand...
Click to collapse
Soo Benee are you working to create a good kernel for our P990 based on new Source Code? Thank you man GOOD WORK!!:laugh:
v0.12 is out
http://code.google.com/p/openstar2x/downloads/detail?name=su660-cm-nightly-v0.12.zip
first of all, BSOD fixed I guess
I found the following error in dmesg
Code:
...
<4>[ 5.468524] tegra_dvfs: vdd_cpu: stats above 1237 mV will be squashed
<3>[ 5.475446] [B]Failed to set dvfs regulator vdd_core[/B]
<3>[ 5.480983] star_sensor_late_init: Failed to set vddio_vi to 1.8v
...
dig around and found some error at regulator_check_consumers() in the driver/regulator/core.c
Ive searched diff/blame with recent source and finally i found the following fix by Mark Brown
http://nv-tegra.nvidia.com/gitweb/?...ff;h=4aa922c024b2a194d7b68b22a66dfcf86e7838b3
Code:
index 7287000..9493f61 100644 (file)
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -158,6 +158,13 @@ static int regulator_check_consumers(struct regulator_dev *rdev,
struct regulator *regulator;
list_for_each_entry(regulator, &rdev->consumer_list, list) {
+ /*
+ * Assume consumers that didn't say anything are OK
+ * with anything in the constraint range.
+ */
+ if (!regulator->min_uV && !regulator->max_uV)
+ continue;
+
if (*max_uV > regulator->max_uV)
*max_uV = regulator->max_uV;
if (*min_uV < regulator->min_uV)
without this fix BSOD always happened with overclocked kernel using the old GB bootloader after deep sleep
i use v12 kernel with Cm10 1107! it failed to boot the first time. the phone freezes at the boot animation (means that the boot animation does not even animate). i have to pull the battery out and put it in to reboot. don't know if this's a bug or not!
---------- Post added at 02:09 PM ---------- Previous post was at 01:53 PM ----------
i just got my phone freeze when using camera. and i have to pull out the battery to reboot. and it freeze at the boot animation another time. so may be this is a bug! i use the OC kernel and set 1200 to be the max clock!
4ever1lov3 said:
i use v12 kernel with Cm10 1107! it failed to boot the first time. the phone freezes at the boot animation (means that the boot animation does not even animate). i have to pull the battery out and put it in to reboot. don't know if this's a bug or not!
---------- Post added at 02:09 PM ---------- Previous post was at 01:53 PM ----------
i just got my phone freeze when using camera. and i have to pull out the battery to reboot. and it freeze at the boot animation another time. so may be this is a bug! i use the OC kernel and set 1200 to be the max clock!
Click to expand...
Click to collapse
Yes, me too
Only for cm-10.1-20130217-NIGHTLY or newer.
Click to expand...
Click to collapse
Flash attached files using the latest CWM recovery at your own risk.
Using CyanogenMod's android_kernel_samsung_espresso10. Forked from codeworkx work, updated to the latest Samsung JB kernel source, heavily modified for better performance
300MHz - 1.52GHz available CPU frequency, limited @ 1.008GHz on boot (this kernel safe for every device if you leave it as is).
CPU frequency really limited @ scaling_max_freq value :victory:
CPU voltage control support
GPU overclocked by default @ 384MHz
Performance governor on boot, interactive after boot completed for faster boot, "sleep too deep" bug free
CFQ as the default scheduler
LZO compressed boot image and kernel for faster decompression
TCP congestion westwood
Using CM 10.1 JB 4.2.2 power HAL interface from PAC ROM, patched as my advice and compiled by Nick0703
KK-Boot's tweaks applied. Since this kernel based on KK-Boot's kernel, all credits on KK-Boot applies here as well
Tsjoklat's bootanimation workaround fix included, edited slightly because this kernel boot process too fast
blackhawk-kernel-0.3 has been tested on PAC ROM. There is no version without overclock for now!
CHANGELOG, blackhawk-kernel-0.4:
Click to expand...
Click to collapse
Set accelerometer and load touchscreen module with a proper parameter depend on ro.sf.hwrotation value, ro.sf.hwrotation=270 -> portrait and ro.sf.hwrotation=0 -> landscape. Copy a proper camera HAL interface (saved somewhere) to /system/lib/hw
mms136.c code snipped:
Code:
#endif
};
/* Ketut P. Kumajaya, March 2013: build as a module, add module parameter */
/* Changed in: mms136.c, melfas_isp.c, Kconfig, and Makefile */
static bool pivot = true; /* may configurable kernel config still needed */
module_param(pivot, bool, 0444);
MODULE_PARM_DESC(pivot, "Enable swap (x,y) coordinate");
static int ts_read_reg_data(struct ts_data *ts, u8 address, int size, u8 *buf)
{
/system/etc/init.d/01boot contents moved to /system/etc/init.post_boot.sh, CM init.d is correct as an initial boot script but I want kernel tuning applied after boot completed. This /system/etc/init.post_boot.sh is a template for user kernel configuration. Don't use any init.d script for kernel setup, it could be slow down device boot process
Using CM 10.1 JB 4.2.2 power HAL interface from PAC ROM
blackhawk-kernel-0.4 has been tested on PAC ROM.
EDIT: 0.4 for P3100 only for now, P311x have a different accelerometer sysfs file! I will fix it ASAP, depend on user feedback.
P311x user, please try 0.4.1. The auto rotation script now much clever to parsing accelerometer sysfs file. Waiting for your feedback!
Waiting for your review, do not forget to press my thanks button or better my DTM button
Thank you for your great work, as always, ketut! Running great on my p3113 on 02/18.
Only taken it for a quick spin but seems very snappy, everywhere. Just solid work man.
Awesome Im gonna give it a try right now
Oh yes...this is what I was waiting for!!
EDIT: im getting bootloop...any specific way of installing?
EDIT(again ): working now!
peRFect! said:
Oh yes...this is what I was waiting for!!
Click to expand...
Click to collapse
Yes this wat I mentioned in cm10.1 thread yesterday.....
Sent from my GT-P3100 using xda premium
Will this work with the Baked Blackbean ROM? its running on 4.2.1, and I believe it is AOKP based. Thanks.
Quick review:
Worked fine on official cm10.1 and in Dark Fantasy(unofficial)
No over heating.....,no force close....no random reboot......wakes well from deep sleep. .....
You tube HD video streams nicely even in 2g connection
I have not checked any benchmark.... Off possible I will do that also.....
Finally...
§ ketut u have done an fantastic job so quickly...... Million thanks for ur hard work dear bro......§
Sent from my GT-P3100 using xda premium
ketut.kumajaya said:
Flash attached files using the latest CWM recovery at your own risk. Still not found a way to lock the CPU @ 1.08GHz on boot, the OC version max frequency 1.2GHz for now and GPU clock 384MHz by default.
- Using the newer kernel source from opensource.samsung.com, codeworkx change applied
- LZO compressed boot image and kernel for faster decompression
- Performance governor on boot, interactive after boot completed for faster boot.
- ROW as the default scheduler
- "Sleep too deep" bug free of course
Waiting for your review, do not forget to press my thanks button or better my DTM button
Click to expand...
Click to collapse
Awesome...ure a truly great dev ketut!
great work Ketut !!!
i will surely try soon
love how this community is coming together for support of all types of roms ......
Everythink work great ! Thanks Ketut you`re the best .
Whoaa exellent work bro !!! Gonna give it a try soon as i get my tab back . Anyway , does this kernel make Directory Bind apps worked ?
question about ram available
Hi there
I just wanted to know how much ram is available in this kernel cuz stock jb had an increase of ram to 771 mb while the cm 10.1 rom screenshots showed 690 mb ram.. so does this kernel has 770 mb or 690 mb usable ram?
Correct me if i'm wrong.
a1shakes said:
Hi there
I just wanted to know how much ram is available in this kernel cuz stock jb had an increase of ram to 771 mb while the cm 10.1 rom screenshots showed 690 mb ram.. so does this kernel has 770 mb or 690 mb usable ram?
Correct me if i'm wrong.
Click to expand...
Click to collapse
cm10.1 20130218 build gives 774mb of usable ram! (installed the nightly with ketuts kernel)
hi all,i'm use rom cm10.1 buildt 18 and i want OC my tab up to 1.2 Ghz.I have to flash cm-10.1-blackhawk-kernel-0.1-oc-p31xx.zip or flash both of them cm-10.1-blackhawk-kernel-0.1-p31xx.zip and cm-10.1-blackhawk-kernel-0.1-oc-p31xx.zip.
Thanks and srr my English
Doesn't work for me. After flashing I get multi coloured screen on startup
Sent from my GT-P3100 using xda premium
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Forget to add, I use cyanogen 10.1 , 4.2.2
Sent from my GT-P3100 using xda premium
indigold said:
Doesn't work for me. After flashing I get multi coloured screen on startup
Sent from my GT-P3100 using xda premium
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Forget to add, I use cyanogen 10.1 , 4.2.2
Sent from my GT-P3100 using xda premium
Click to expand...
Click to collapse
What is multi colored screen on start up....
???????
Adi....
★WHY CAN'T YOU HIT THANKS BUTTON IFF AM HELPING YOU★
Boots up showing d Samsung logo,then a kind of error coloured screen comes up
Sent from my GT-P3100 using xda premium
indigold said:
Boots up showing d Samsung logo,then a kind of error coloured screen comes up
Sent from my GT-P3100 using xda premium
Click to expand...
Click to collapse
Am also have same issue but this kernel work perfectly for me.....
Adi....
★WHY CAN'T YOU HIT THANKS BUTTON IFF AM HELPING YOU★
I am not comfortable with it
THIS IS MY 16 ANDROID DEVICE. I AM NO NOOB
indigold said:
I am not comfortable with it
THIS IS MY 16 ANDROID DEVICE. I AM NO NOOB
Click to expand...
Click to collapse
Ow wat an great combination of we both.....
U r ok with aokp kernel. ....but am not able to boot.....
Am ok with this kernel. .....but u r not....????
Oh let 3rd person to enter.....with 18 release. .....
Adi....
★WHY CAN'T YOU HIT THANKS BUTTON IFF AM HELPING YOU★
CyanogenMod (pronounced /saɪ.'æn.oʊ.dʒɛn.mɒd/) is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices.
http://wiki.cyanogenmod.org/w/About
Code:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Instructions
1. Download the zip(s) - firmware and Google Apps additional package (optional)
2. Download and install a compatible recovery
3. Wipe data, system & cache partitions and flash firmware
4. Optional: install the Google Apps additional package
"Always do a clean flash when coming from other roms or versions:
Stock -> cm-11.0: clean flash
Build 1116 - -> Build 1122: dirty flash should be sufficient"
Known Issues:
- XBMC and some games touch input will fail. A work around would be to purchase a bluetooth keyboard, they are pretty cheap from ebay, or use your existing one to navigate inside XBMC until we solve the problem.
- audio routing does not work when making calls with viber, hangout or skype while connected to bluetooth headset.
- MHL output the colours wrong and audio does not route to tv.
- Google movies will crash if you want to download locally.
cm-11-20150520-UNOFFICIAL-chagallwifi.zip
cm-11-20150520-UNOFFICIAL-chagallwifi.zip.md5sum
LATEST 17/6/2016
cm-11-20160617-UNOFFICIAL-chagallwifi.zip
cm-11-20160617-UNOFFICIAL-chagallwifi.zip.md5sum
Google Apps additional package:
http://wiki.cyanogenmod.org/w/Gapps
TWRP:
http://forum.xda-developers.com/gal...recovery-twrp-2-7-1-0-touch-recovery-t2817100
device tree
kernel for exynos 5420
vendor
Thanks to CyanogenMod team and thanks to:
Nvertigo67 fixing many bugs, eousphoros for starting the intital port to klimwifi, suzook for letting us hog his thread , crpalmer , to allow
finally to create the build for SM-T800.
Special big thanks to Nvertigo67 for his ongoing hard work on this rom.
How to soft reset your tablet:
If for any reason your tablet freezes or you flash the wrong kernel and the tablet stops responding, please do the following:
Hold the power key + volume down + home button for at least 10 - 15 seconds, the tablet should go to download mode. press the volume down key, the tablet will restart.
if you want to go to recovery, then while you are still in download mode, as soon as you click the volume down, quickly hold the power button + volume up + home button key, this should then take you to your recovery screen.
last edited 05/20/2015
For Users who prefer to disable the capacitive buttons, and are annoyed by flashing capacitive light now and then, simply flash one of the following kernels with twrp and restart.
no_capacitive_buttons_chagallwifi_CM_7_11_2014.zip (tested and stable)
no_capacitive_buttons_chagallwifi_CM_8_11_2014.zip
added extra governors
below are the standard kernel that are found in the roms:
chagall-ingo-v1.zip
chagallwifi_cm_7_11_2014.zip
08_11_14_CM11_kernel.zip
added extra governors
These will work only on cm11 chagallwifi, please don't flash this kernel if you are running stock Samsung firmware, your device will not boot.
Guideline on flashing written by Nvertigo67:
Very dirty flash:
flash rom
flash gapps
[optinal but recommended for some apps to work i.e. Titanium] flash chainfires SuperSU
Dirty flash:
[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system
wipe cache
wipe dalvik-cache
flash rom
flash gapps
[optional] flash SuperSU
Clean flash
factory reset in recovery - (without wiping /data/media) this resets your settings and deletes your installed apps
[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system
wipe cache
wipe dalvik-cache
wipe data (without wiping /data/media) this resets your settings and deletes your installed apps
flash rom
flash gapps
[optional] flash SuperSU
Very clean flash
factory reset in recovery - (without wiping /data/media) this resets your settings and deletes your installed apps
[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system
wipe cache
wipe dalvik-cache
wipe data (without wiping /data/media) this resets your settings and deletes your installed apps
wipe internal memory
flash rom
flash gapps
[optional] flash SuperSU
"Always do a clean flash when coming from other roms or versions:
Stock -> cm-11.0: clean flash
Build 1116 - -> Build 1122: dirty flash should be sufficient"
I recommend ALWAYS a "Clean flash", though myself I do many times "Dirty flash"es while testing. Whenever I run in issues, I reflash the "Clean flash" way. On the issues with Camera2 I even did "Very clean flash"es - to ensure no old data is interfering.
On many threads it is MANDATORY to have done a "Clean flash" before reporting issues. Not so here - and I want to leave it this way. But always ask yourself: how many times have I done a dirty flash? Have I tested and edited files? Is it time to "Clean flash"?
I count on users good judgment - all participants on this beta-test has shown this so far.
BTW: Thank you for helping making this rom better!
Nvertigo
<removing post to let OP post>
Here are the newest builds. From now (Christmas 2014) I change the structure of this posting. The most recent build will be no longer at the end of the posting but right at the beginning of the post right after credits, issues, installation, recomedations and sources.
Credits:
@Barracuda77777 (without his contributitions and encouragement there would be no cm11 rom. He alone saved me from loosing myself in source code! Whenever I got stuck he came up with the brilliant change or the day saving idea. Thank you, brother!)
@UpInTheAir (most of the code changes in the kernel from the last 10 days before Christmas are from his SkyHigh kernel. He let me use his code, and most important: he explained with endless patience to me what I was doing... To reflect this the default branch of our kernel is no longer cm-11.0 but cm-11.0-sh [sh for small sister of SkyHigh]. Thank you, mate!
@crpalmer (for picassowifi device and kernel gits - the base @Barracuda77777 and me sstarted of from)
@eousphoros (for his device git: the base for @crpalmers work)
@halaszk88, @faux123 and all the others I forgot
Known Issues:
xbmc (and some games) does not take touch input
MHL has no sound and wrong colors
If you map MENU to a capacitive key (no matter if key itself or "long press", it will not work - workaround: do not map MENU to anything at all, then the apps are forced to show action overflow menu (aks 3 dot menu)
Installation:
I recommend twrp 2.7.1.1 for backup, restore and flashing. Others my work, but twrp 2.8.1.0 has problems
Do a nandroid backup (and try at least once a restore to be sure it works - reboot to recovery in between backup and restore)
Download and check md5 checksum
read thread (reread postings 1 to 5)
Always do a "clean flash" as described in #3 (if you are already on our cm11 rom you can try a "dirty flash" as described in #3 - if you come from any other rom "clean flash" is mandatory!)
Recomended:
I use chainfires SuperSU - though I like koushs rom-buildin superuser because it is opensource, TitaniumBackup only works with Chainfires SuperSU
Third party installations of busybox may affect rom; read this.
Source code:
Device: https://github.com/nvertigo/android_device_samsung_chagallwifi
Kernel: https://github.com/nvertigo/android_kernel_samsung_chagallwifi
Binaries: https://github.com/nvertigo/android_vendor_samsung_chagallwifi
Script to repack and resign flashable zip to make some symbolic links in /system while flashing: https://github.com/nvertigo/repackrom
Standard build branch for device and vendor is cm-11.0, for kernel cm-11.0-sh.
WARNING: try to not ask already answered questions - this will lead to bad karma, which leads to unwanted side-effects in your life. Kidding, of course - but really try to read the thread.
Build 0101 (Happy New Year Build)
Mainly a maintain release. Small performance/battery enhancements: Added power efficient workques and bfq again (thanx to @UpInTheAir); added biomic optimizations again (we had them some time ago, but @Barracuda77777 and me thought they were responsible for some unstabillity issues - after barracuda had found the reason was something else, I forgot to readd again - till now). f2fs code is updated and is no module any longer but build in kernel (I'm trying to migrate rom to f2fs with no success so far, it's not bootin at the moment).
I recommend the settings this build comes up with (cfq, 400 (aka 200) MHz min speed, interactive, to name the most important. But you can play with and find the best for your personal usecase. (simple settings via Settings->Performance; advanced fine tuning can be done in 01systemtuning in /system/etc/init.d - if you don't know what that means, leave file alone!). Brancheas are cm-11.0 for device and vendor and cm-11.0-sh for kernel.
01moduleload: remove f2fs module from loading, 'cause we need it in kernel to boot from. Nvertigo
change actual mounts of /system /cache and /data to f2fs Nvertigo
cleaned up overlay. Nvertigo
Fix Typo credit NBruderman barracuda7
tune bionic a bit - works on manta. Nvertigo
f2fs: filesystem version 3.4.y [20140903] dennes544
set permissions of block/bfq*[ch] to 0644. Nvertigo
enabled bfq iomscheduler. Nvertigo
workqueue: fix permission for power_efficient [neobuddy89] UpInTheAir
CPUFREQ: ondemand: use power efficient wq! [halaszk] UpInTheAir
workqueue: add system wide power_efficient workqueues (squash commits
bfq-iosched: tuning for SSD [anarkia1976] UpInTheAir
scheduler: update BFQ-v7r4 to BFQ-v7r5 for 3.4.0 [Paolo Valente] UpInTheAir
scheduler: BFQ-v7r4 for 3.4.0 [Paolo Valente] UpInTheAir
MD5: 0890de20a55f97c2a382ddbf9ec7b079
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20150101-UNOFFICIAL-nvertigo-chagallwifi.zip
Click for older changelogs:
Build 1224 (Christmas Build)
Besides updating upstream I tried to reduce battery usage. Therfore I extensivly changed kernel code (thanx to @UpInTheAir; see above). I added /system/etc/10systemtuning as a playground (documentation and exsamples are in the file itself - if you don't understand leave it alone, works fine "as is").
repo sync at 23/12 21:30h UTC
changed min freq to 200 MHz (actualy 400 MHz) in /system/etc/init.d/10systemtuning
changed toolchain for building the kernel to arm-eabi-4.8 Nvertigo
added /system/etc/10systemtuning for - you guessed it - system tuning. Nvertigo
media_codecs.xml: changed OMX.google.h264.decoder to OMX.ffmpeg.h264.decoder to fix broken preview of video thumbnails. Nvertigo
compiler: changed CROSS_COMPILE to arm-eabi-4.8 for out of tree building. Nvertigo
arch/arm/mach-exynos/sec_misc.c: dereference pointer to make sizeof() work with arm-eabi-4.8
Samsung warnings Christopher R. Palmer
cpufreq: tidy up UpInTheAir
beautyfied last commit: changed some spaces back to tabs again. Nvertigo
sched: LOAD_FREQ (4*HZ+122)
kernel: sched: LOAD_FREQ (4*HZ+61)
lib: memcopy & string use glibc version [Miao Xie] UpInTheAir
mali gpu: lower treshold for 177 to 30 and for 266 to 50 to prevent lagging after idle. Nvertigo
add a runtime dependency checker [AndreiLux] UpInTheAir
update cyanogenmod_chagallwifi_defconfig to 3.4.105 Nvertigo
CHROMIUM: clocksource: allow clocksources to be selected earlier during boot [Andrew Bresticker] UpInTheAir
gpu: ion: system_heap: add support for 2MB allocations [Mitchel Humpherys] UpInTheAir
arch/arm: compile with full -mfpu=neon-vfpv4 & hard float UpInTheAir
enable CONFIG_KERNEL_MODE_NEON Nvertigo
ARM: implement KERNEL_MODE_NEON [halaszk] UpInTheAir
enable CONFIG_USB_ANDROID_SAMSUNG_MTP again. Nvertigo
Compile stock and Samsung MTPs together [AndreiLux] UpInTheAir
block: deadline: allow 0ms deadline latency, increase the read speed [tuxiaobing] UpInTheAir
block: deadline: Optimize for non-rotational [myfluxi] UpInTheAir
Revert "Usual tuning of deadline for flash." Nvertigo
exynos cpu: disabled 250 MHz, enabled 200 and 100 MHz. Nvertigo
mali gpu: lowered min freq to 100 MHz, enabled 533MHz, optimized up/down stepping. Nvertigo
Download:
MD5: f710f5b26d0d342b4414ea9221eb5487
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141224-UNOFFICIAL-nvertigo-chagallwifi.zip
Same build as yesterday, but mic is working now:
MD5: b20000c9075719b242f212abb7d2fe93
ROM:https://www.dropbox.com/s/35tbuj4nu4ca2e9/cm-11-20141029-UNOFFICIAL-nvertigo-chagallwifi.zip?dl=0
Camera seems to be fixed
camera libs reworked - now using wrapper
keyboard bluetooTh fixed
1000 fixes I forgot - see git
Repo synced 5pm GMT
MD5: 4fa6c50d42c661c0f426a76051f6ff9f
ROM: http://162.220.240.98/ftp/nvertigo/cm-11-20141101-UNOFFICIAL-nvertigo-chagallwifi.zip
New try to fix camera2 (reverted three commits - if not clean flashed delete data from camera2 and gallery3d)
Readded some codecs
Cleaned /system/etc/wifi (to get wifi running in the first place, I had make a mess: copied to much files, did not symlink, but had the same files several times. Now only nessecaty files and symlinks in place)
cleanup: took out framework entries for, barometer, step detector, step counter. Not needed barracuda7
min/max cpugrequencies selectable (settings/performance)
as always: 1000 small things
Update: binary blobs to latest firmware: NJ1
MD5:d12610c30a1a875ed7e0f43a387c85c2
Rom:http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141104-UNOFFICIAL-nvertigo-chagallwifi.zip
1106 Build
Tuned bionic
Kernel: patched in most of fixes/optimizations from picassowifi (thanx to crpalmer!) in. (not including the patchup to .104)
Kernel: optimized deadline for flash-devices
Kernel: don't block the flusher thread waiting on IO
Build from github.com/nvertigo/android_*_samsung_chagallwifi branch my-work.
MD5: 96ca0e513eebc52189171859fb192056
http://charlesingo.mine.nu/ftp/nvertigo//cm-11-20141106-UNOFFICIAL-nvertigo-chagallwifi.zip
1111 build
I've undone the optimizations when ironing out the cast issue. Not included at this build:
biomic otimization
deadline optimization
Don't block flusher on IO
New Features:
High Touch Sensivity (aka Globe Mode; for some mystherical reason it's in Languahe/Input)
Adaptive Backlight (don't know if it has great effect, if you are using autobrightness, but it does no harm when using both of them)
Fixes:
cast screen (thanx to barracuda helping me to find the commits, that brake it; thanx to the user pointing me to castreceiver for making my n10 to a chromecast for testimg)
Disable Buttons when softkeys are active now working
Regressions:
When using Buttons they will flash on standby. At the moment I can either get the disabling when using softkeys to work (staying disabled after standby and reboot) or I can get rid of the flashing. It's some strange interaction with sensorlib [this is settings lights on and imidietly off again and makes the flashing] I had to do further inverstigation.
This is a workaround for flashing buttons
Still not working:
xbmc
ANT+
MHL
MD5: 711a4eaefb6ff1720dd9364e8258b505
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141111-UNOFFICIAL-nvertigo-chagallwifi.zip
Build 1116
This is a kind of stable release. I incorperated everything what proved to be stable or working. No new features, one bugfix. Mainly I'vemgone back to the congiguration where the capacitive buttons aren't flashing when active - to avoid reactivating of capacitive buttuns after first lock/unlock cycle when using softkeys (aka,on-screen-keys) flash this kernel. REMEMBER to activate softkeys BEFORE reboot to recovery and flashing kernel without tc300k driver!
To get back the capacitive keys flash this one.
Also I have disabled tethering, 'cause it's not really of any use and not working on our 3g/4g-free device.
I have changed my build environment from oracel-java-1.7 to icedtea-7 (bootsttaoed and build locally on my gentoo system). Though cm build script is spitting warnings it builds just fine.
Capacitve keys work as they should: they don't flash on standby - backlight is configurable.
Bugfix:
increased dalvik.vm.heapminfree from 512Kb to 2Mb for our large display
Features added:
added flash friendly filesystem (f2fs) support to kernel (and recovery - which is NOT! included in zip)
MD5: cc074fa69e9e91215a2d85aa2d50278b
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141116-UNOFFICIAL-nvertigo-chagallwifi.zip
Kernel without capacitive keys driver: chagall-20141116-wo-tc300k.zip
Original kernel from 1115 rom with capacitive keys driver: chagall-20141116.zip
Build 1122 (first daily driver release)
As stated I try to develop towards stability and useability, not towards features and speed. Fot those of you waiting for a SkyHigh kernel with all the settings, OV, UC I'be bad news: some of the kernel enhancements does not play nice with our rom.
But back to the new build: I've decided to take everything which is not fully supported by our rom out: last time I kicked tethering, this time I took out the on screen navbar (we are missing a sysfs interface to disable capacitive keys permanently while usimg onscreen navbar - the workaround with capacitive-keys-driver-free kernel broke language settings; so it was time to get a feature we can't completly support out of the rom). But before you you cry: There will be an alzernative! Hurray will publish a step-by-step HowTo to get onscreen navnar and disable capacitive keys. So even without the setting in the rom you have the freedom to use what you want.
By cleaning out the rom this is the first time I feel able to recomment this rom as a true daily driver! (Of course this doesn't mean it's bugfree, but it's stable, fast, featurefull and usefull.)
Fixes:
haptic feedback on capacitive keys (thank you @svardman !)
fix capacitive buttons / fix broken languahe support by taking out setting from rom
New:
make kernel modular
add eseay to use /system/etc/init.d/01moduleload script (simply add module to MODLIST and execute script on shell or reboot)
make some fs (which are not needed for boot) modular and load them automaticaly on boot
added kernel support for nfs3 (not activated in 01moduleload)
added xpad.ko (not activated in 01moduleload)
MD5: a2d9452255998f455540ecaae3c789f2
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141122-UNOFFICIAL-nvertigo-chagallwifi.zip
Build 1128
This build will be the last for a couple of weeks. I won't have access to my development host for about 7 weeks. When home again I will probably work on cm12.
XBMC and MHL is still not fixed - and fixing them is beyond my scope. Whoever feels able to fix them is highly invited to join development.
All other issues shoild be fixed. As for the two last builds: It's stable, fast and has a wuize decent battary life comparable to stock.
Who wants to use onscreen nav bar and disable capacitive keys should follow the procedure posted by @hurray in this posting
Changes:
kernel rebased on sammy NJ2 and updated to 3.4.104
repo syncd 20141128 8:00 h UTC
MD5: 231bb35d0a5d305ea8229cc9dcbefd6d
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141128-UNOFFICIAL-nvertigo-chagallwifi.zip
Build 1206 Santa Claus
Maintainance release. Kernel updated to 3.4.105. repo synced.
MD5: d5fb397ee8fb48b7937ebcf3b9c691ea
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141206-UNOFFICIAL-nvertigo-chagallwifi.zip
Amazing build! You guys are the best!
Thank all devs very much for their hard work!
The resulting Rom runs petty well and is for sure ready to be a daily driver.
I need the capacitive buttons
That why I will install the other version
Thank you so much for making this rom.
But can I ask what is the 'No Capacitive buttons at the kernel level'
Mean cannot use the back and task???
Only can use the home button???
Thanks again
ares. said:
I need the capacitive buttons
That why I will install the other version
Thank you so much for making this rom.
But can I ask what is the 'No Capacitive buttons at the kernel level'
Mean cannot use the back and task???
Only can use the home button???
Thanks again
Click to expand...
Click to collapse
I will post a kernel that enables capacitive buttons soon in the 1st post.
Sent from my SM-T800 using Tapatalk
Barracuda77777 said:
I will post a kernel that enables capacitive buttons soon in the 1st post.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
I'm just doing a clean build with working mic and all the capacitive buttons fixes.
Be patient. But you can always use my yesterdays build with the modified mixer_paths.conf from barracuda77777.
hurray said:
Thank all devs very much for their hard work!
The resulting Rom runs petty well and is for sure ready to be a daily driver.
Click to expand...
Click to collapse
Pretty well???? It kicks stock tw crap! Samsung should hire these guys!
thanks for you guys' hard work, although I am not a cm user
btw, I would suggest to make it a preference and let users to choose whether to enable the captive buttons instead as to minimize your effort to maintain the port, as well as some users may need working buttons for some reasons so they don have to flash another kernel in the middle of work or playing games, for instance
New Nvertigo Build
New Nvertigo Build up.
post#5
---------- Post added at 02:34 PM ---------- Previous post was at 02:31 PM ----------
ykkfive said:
thanks for you guys' hard work, although I am not a cm user
btw, I would suggest to make it a preference and let users to choose whether to enable the captive buttons instead as to minimize your effort to maintain the port, as well as some users may need working buttons for some reasons so they don have to flash another kernel in the middle of work or playing games, for instance
Click to expand...
Click to collapse
It'small about freedom of choice: you have the choice between a rom entirely without capacitive buttons (barracuda), and a rom with the choice to dis-/enable it...
---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------
suzook said:
Pretty well???? It kicks stock tw crap! Samsung should hire these guys!
Click to expand...
Click to collapse
Thanx for your kind words - but first of all: thank you fo your patients with us two thraedjackers!
---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------
Can someone please test:
- BT-Headset
- BT-Keyboard
- HDMI-Out (thinkmsammy hasma prporietary cable for that one - might be wrong)
- all kind of media
Thank you.
Bluetooth-Keyboard works very well (tested with a MS Wedge Keyboard).
I am on the build from Barracuda77777.
Also from me, thank you very very much for the awesome work!
Just a question. Don't know if thats even possible. Wouldnt it be much easier for you to maintain just one build and let the user decide during flashing if he wants to use capacitive buttons or not. Perhaps this would be possible by using "Aroma Installer" or something like this.
Again, kudos from me.
nvertigo67 said:
New Nvertigo Build up.
post#5
---------- Post added at 02:34 PM ---------- Previous post was at 02:31 PM ----------
It'small about freedom of choice: you have the choice between a rom entirely without capacitive buttons (barracuda), and a rom with the choice to dis-/enable it...
---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------
Thanx for your kind words - but first of all: thank you fo your patients with us two thraedjackers!
---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------
Can someone please test:
- BT-Headset
- BT-Keyboard
- HDMI-Out (thinkmsammy hasma prporietary cable for that one - might be wrong)
- all kind of media
Thank you.
Click to expand...
Click to collapse
I can confirm BT-Keyboard works
HDMI-Out - 'KIND OF' works it looks like the color yellow is missing? And audio does not get routed to the tv via the HDMI out - ( the color, and audio ) both work okay with TW Rom. If we can get this to work it would be amazing - let me know if there are any logs I can give that would help.
Tested HDMI out on a 10 pin mhl adapter with no luck. same adapter works on htc one m8 gpe.
nvertigo67 said:
New Nvertigo Build up.
post#5
---------- Post added at 02:34 PM ---------- Previous post was at 02:31 PM ----------
It'small about freedom of choice: you have the choice between a rom entirely without capacitive buttons (barracuda), and a rom with the choice to dis-/enable it...
---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------
Thanx for your kind words - but first of all: thank you fo your patients with us two thraedjackers!
---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------
Can someone please test:
- BT-Headset
- BT-Keyboard
- HDMI-Out (thinkmsammy hasma prporietary cable for that one - might be wrong)
- all kind of media
Thank you.
Click to expand...
Click to collapse
jrock60 said:
Tested HDMI out on a 10 pin mhl adapter with no luck. same adapter works on htc one m8 gpe.
Click to expand...
Click to collapse
I got some output using my cable using nvertigo67's rom - did you get no output at all ? Did the dongle work with the stock rom ? The problem with wtih mine is the color yellow is missing, and audio is not being routed via the HDMI cable ( i think there is currently an issue with audio and BT headsets as well ??)
Im running:
cm-11-20141028-UNOFFICIAL-chagallwifi.zip
The cable did not work on touchwiz
jrock60 said:
Im running:
cm-11-20141028-UNOFFICIAL-chagallwifi.zip
The cable did not work on touchwiz
Click to expand...
Click to collapse
If your cable did not work with TW then it will not work with CM - my cable was working perfectly with TW - and with CM11 ROM its running into the color/audio issues but i still do get an output.
One problem with the BT-Keyboard - in the TW rom when you have a keyboard connected it disables the softkeyboad on the screen ( this doesn't) seem to happen for the CM11 ROM
Proximity sensor fix for CM based ROM
/* Info */
This thread is made to avoid speaking about this subject under devs threads. To save their time.
In this thread your going to find a step by steps way to fix Proximity sensor on our devices.
I'm working over a flashable .zip to automate process.
/* Disclaimer */
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
/* Supported device */
Galaxy S4 LTE + International (GT-I9506, ks01lte) : working.
HLTE : working.
Basically I think all the ROMs based over Cyanogenmod for Samsungs devices.
/* What you need to know */
This is only tested on
- KS01LTE on CM12 from Arter97 and CM11 of Solk2.
- HLTE based on CM12 version of temasek.
Other variants, other OS may not be fully compatible
/* Thanks to */
All devs who are working for our device. @arter97 @solk2 @temasek @DeHAWK @jonte28 @budda1996 @Genie's
The Cyanogenmod team.
@hilefin who gave me the way to fix proximity sensor and helped me in first step.
/* Downloads */
Coming in the close future.
Created 2015-01-09
Last Updated 2015-01-09
XDA:DevDB Information
Proximity sensor fix for CM based ROM, Tool/Utility for the Samsung Galaxy S 4
Contributors
likesatan
Version Information
Status: Testing
Created 2015-01-13
Last Updated 2015-01-14
Step by steps method
/*Requirement*/
TWRP or CWM recovery.
Terminal app (Go google play) with super user rights.
/*Backup*/
Reboot into recovery mod and save your EFS partition and nothing else.
It will save you time in case of troubles.
/*Step by steps way*/
1.
Go to "Google Play" download "Terminal".
Grant super user rights to Terminal app.
Open new terminal session.
2.
Type "/system/xbin/su -l"
3.
Type cd /sys/devices/virtual/sensors/proximity_sensor/
4.
With the proximity sensor uncovered.
Type "cat state" and write down the value (74 in my case).
5.
Type "cat prox_cal"
Write down the first value between parenthesis (this is the offset).
Eg. (0,31,75) take 0.
6.
Sum both values.
In my case it was (74+0) = 74.
7.
Convert the value to hex. Link.
In my case, 74(dec)=4A(hex).
8.
Instead of 4A, put your value.
Type "echo -en $'\x4A' > /efs/prox_cal"
9.
Type "chown system:system /efs/prox_cal"
10.
Type "chmod 644 /efs/prox_cal"
11.
Type "sync"
12.
Type "reboot"
13.
Done.
Last Updated 2015-01-09
Flashable ZIP
/*Under development*/
I'm porting this step by step process to a flashable ZIP.
Coming in the future.
/*Requirement*/
TWRP or CWM recovery.
/*Backup*/
Reboot into recovery mod and save your EFS partition and nothing else.
It will save you time in case of troubles.
/*BATCH CODE*/
If you want to help here is the batch code.
I think it's working. Have to test it.
Code:
#! /bin/bash
/system/xbin/su -l
SOMEVAR='n'
SOMEVAR='HEX'
n=0
HEX=0
cd /sys/devices/virtual/sensors/proximity_sensor/
Cat state
Cat prox_cal
Echo -n "Please type the sum of the first number and the second the first in parentesis. Eg first number 45. Second (23,00,17). Sum is 68."
Read n
HEX=`echo "obase=16;ibase=10; $n" | bc`
echo -en $'\$HEX' > /efs/prox_cal
chown system:system /efs/prox_cal
chmod 644 /efs/prox_cal
sync
echo "Done ! Touch the screen to reboot"
timeout /t -1
reboot
Then I'm going to use this tool to convert it.
Last update 2015-01-09
/*Known issues*/
Cat state is giving you 255 value.
255 is highest value. Meaning your sensor is thinking is covered with blanket.
Their is dust on sensor.
[Fix]
Clean with "canned air" duster.
Thanks to @ode_
/*Problems*/
In case of trouble you can flash your EFS backup you first made in TWRP/CWM recovery.
Other issue ?
This thread is made for that.
Any questions ?
Juste ask.
Last Updated 2015-01-09
FAQ
FAQ under construction.
Thank you for compiling this information. Can you clarify the statement, "Type "/system/xbin/su -l"". Is that last character a lower case letter L, or is it the vertical line character |?
---------- Post added at 08:50 PM ---------- Previous post was at 08:34 PM ----------
I got it. It took several attempts, so the recommendation to backup the efs partition was well received. Thanks! It works great!
---------- Post added at 08:52 PM ---------- Previous post was at 08:50 PM ----------
I cleaned my Note 3 thoroughly with a dry rag, and still my values were 214 and 76. Seems very high.
TU Homer said:
Thank you for compiling this information. Can you clarify the statement, "Type "/system/xbin/su -l"". Is that last character a lower case letter L, or is it the vertical line character |?
Click to expand...
Click to collapse
It's a lower case letter L !
I got it. It took several attempts, so the recommendation to backup the efs partition was well received. Thanks! It works great!
Click to expand...
Click to collapse
You're welcome so your proximity sensor is fixed now !
I cleaned my Note 3 thoroughly with a dry rag, and still my values were 214 and 76. Seems very high.
Click to expand...
Click to collapse
No it's going to work fine ! Had a huge value and It worked.
Regards,
Likesatan
"This is only tested on
- KS01LTE on CM12 from Arter97"
Why this ?
I dont have any proximity problems, if ppl mean that display should dim while holding phone near ear etc.
iBuu said:
"This is only tested on
- KS01LTE on CM12 from Arter97"
Why this ?
I dont have any proximity problems, if ppl mean that display should dim while holding phone near ear etc.
Click to expand...
Click to collapse
Because I only test this on my phone and ROM : i9506 - CM12.
Some people have tried it on HLTE it's working too !
As I haven't a lot people testing it on multiples device I dont know if it's working on all devices.
It should work on all CM based roms for samsungs devices.
Regards,
Likesatan
Reminder from personal experience; after battery was out and rebooted phone with grease on front glass over proximity sensor and my phone did recalibration, and my proximity sensor start act weird, kinda broken way.
All what I did after that was battery out(20sec)/in again, cleaning front glass and rebooted and proximity sensor started to work normally.
is it apply to CM 12 latest nightlies ?
sanioclement said:
is it apply to CM 12 latest nightlies ?
Click to expand...
Click to collapse
Yes it is ! I tried it over them
likesatan said:
Yes it is ! I tried it over them
Click to expand...
Click to collapse
Screenshots would be great in step by step description
Regards.
Easy Fix
1.Make sure u have root access
2.Download and install sensor kinetics pro from
3.Open it and scroll down to proximity sensor and turn it off
Awesome. This worked like charm. Even on my note2. Thank you somuch for shaing
Another Placeholder thread, there is definitely seperate rules...
Android-Desire said:
Another Placeholder thread, there is definitely seperate rules...
Click to expand...
Click to collapse
And why placeholder? He post step by step what you must make. Is a guide. And helped a lot of ppl.
Sent from my GT-I9506 using XDA Free mobile app
sevenlife said:
And why placeholder? He post step by step what you must make. Is a guide. And helped a lot of ppl.
Sent from my GT-I9506 using XDA Free mobile app
Click to expand...
Click to collapse
No zip to flash -> Placeholder, again different rules for different people.
Proximity sensor
Sorry for the ignorance...but what is exactly the proximity sensor?
i9500
Is it working on installed a CM 12.1 i9500? Need root?
Thanx
Hey everyone ! This is an unofficial version of Carbon ROM LP-5.1.1 for Asus Zenfone 5.
I've designed it using some fragile source codes. This includes the source codes from quanganh2627 & tank0412.
Before you begin:
Code:
You know the story:
I'm not responsible if you device is wrecked....
....
....
Your warranty will be void(duh)!
....
....
And so on...
And the ROM has most common problems as expected from an AOSP/CM based ROM :silly:
Bug list:
1. Vibration doesn't work
2. Initial boot time is late
3. Battery backup is kinda low on extreme usage only
4. SystemUI crashes randomly
5. Setting would crash if you open info about Carbon ROM from Carbon Fibre option in settings
6. Occasional lags here and there
7. FM radio is not tested yet
8. Any other device apart from a500cg is also not tested. If interested you may.
9. GPS is not yet tested due to lack of time
10. Crashes of AOSP keyboard after theme change (occurs only at first)
11. HW key customization.
What is working: : :fingers-crossed:
1. Dual Sim
2. Brightness
3. Sounds
4. Customization
5. Multi-user mode
6. Memory card support
7. Pretty much everything else works quite fine.
Download:
System.img
Boot.img
Gapps
How to flash it:
( Actually the installation guide is provided with the .rar file downloaded. )
1. Download the system, boot & gapps from the links above.
2. Please make sure you have ADB & Fastboot available. If not please Google it or it's available in many thread too.
3. Now extract the "CarbonROM IMG Compressed.rar" to the ADB/Fastboot directory.
4. Copy the "boot.img" & "open_gapps-x86-5.1-pico-20160410.zip" to the same directory.
5. Reboot to recovery and clear user data.
6. Now from the recovery reboot to bootloader.
7. In the bootloader/droidboot/fastboot mode tpe in the following commands:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash update open_gapps-x86-5.1-pico-20160410.zip
8. And you're done.
9. Please note that the first boot might take some time.
Thanks for giving it a shot...
XDA:DevDB Information
Carbon ROM for Zenfone 5, ROM for the Asus Zenfone 5
Contributors
PaletroxZ, tank0412, quanganh2627
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Any 5.x.x based ROM
Based On: Carbon ROM
Version Information
Status: No Longer Updated
Created 2016-04-10
Last Updated 2016-11-04
--Error--
--Reserved--
--Error Again--
--Reserved Again--
Thanks @PaletroxZ i was actually waiting for this rom
shobint7 said:
Thanks @PaletroxZ i was actually waiting for this rom
Click to expand...
Click to collapse
You're welcome mate.
Sent from my ASUS_T00F using XDA-Developers mobile app
Good work! Welcome back! xD
Can you share your device tree? I want to look at it because i want to see all my mistakes. (I tried to build Carbon rom and i failed)
---------- Post added at 06:26 PM ---------- Previous post was at 06:20 PM ----------
And try this patch to fix vibrator:
https://github.com/quanganh2627/android_device_asus_a500cg-1/blob/aicp-r29/vibrator.patch
---------- Post added at 06:34 PM ---------- Previous post was at 06:26 PM ----------
And use zip archives instead of rar.
tank0412 said:
Good work! Welcome back! xD
Can you share your device tree? I want to look at it because i want to see all my mistakes. (I tried to build Carbon rom and i failed)
And try this patch to fix vibrator:
https://github.com/quanganh2627/android_device_asus_a500cg-1/blob/aicp-r29/vibrator.patch
And use zip archives instead of rar.
Click to expand...
Click to collapse
For vibrator is better to use this patch because quanganh's patch disables Low-Priority vibration.
Also, @PaletroxZ try this
- For late initial boot time
Code:
WITH_DEXPREOPT := true
Also I agree with tank, better use ZIP or 7-Zip to compress.
Hope it helps, great work!
Any ScreenShot?
Maybe i'll try sometime
Good job sir
Sent from my ASUS_T00F using Tapatalk
tank0412 said:
Good work! Welcome back! xD
Can you share your device tree? I want to look at it because i want to see all my mistakes. (I tried to build Carbon rom and i failed)
---------- Post added at 06:26 PM ---------- Previous post was at 06:20 PM ----------
And try this patch to fix vibrator:
https://github.com/quanganh2627/android_device_asus_a500cg-1/blob/aicp-r29/vibrator.patch
---------- Post added at 06:34 PM ---------- Previous post was at 06:26 PM ----------
And use zip archives instead of rar.
Click to expand...
Click to collapse
Okay mate I will. But there are also some mix up I did apart from the device tree. I'll PM you the download link . Thanks for helping us all out with the guides and ROMs mate...
dgadelha said:
For vibrator is better to use this patch because quanganh's patch disables Low-Priority vibration.
Also, @PaletroxZ try this
- For late initial boot time
Code:
WITH_DEXPREOPT := true
Also I agree with tank, better use ZIP or 7-Zip to compress.
Hope it helps, great work!
Click to expand...
Click to collapse
Thanks @dgadelha I'll give this a shot and let you know of the outcome ...
ShuviterDjogja said:
Any ScreenShot?
Maybe i'll try sometime
Good job sir
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
I've attached the screenshots in the screenshots section mate.
Very good! New dev for zenfone 5. ?
clloud77 said:
Very good! New dev for zenfone 5.
Click to expand...
Click to collapse
lol he's not new. He's been making SleekStock Rom for us
ChristopherXI said:
lol he's not new. He's been making SleekStock Rom for us
Click to expand...
Click to collapse
Thanks My friend
Best part of this ROM
@PaletroxZ........bro.....the best part of this ROM is.......touch screen gets disabled when im in a call. I found other roms keep it enabled and caused me to turn on loud speaker/dialer/call hold/airplane mode etc. keep up your good work. :good: so far only 1 prob i have. like other custom roms, im facing the same camera black out issue.
a8962383 said:
@PaletroxZ........bro.....the best part of this ROM is.......touch screen gets disabled when im in a call. I found other roms keeps it enabled and caused me to turn on loud speaker/dialer/call hold/airplane mode etc. keep up your good work. :good: so far only 1 prob i have. like other custom roms, im facing the same camera black out issue.
Click to expand...
Click to collapse
Thanks mate . And could you elaborate the camera black out issue?
PaletroxZ said:
Thanks mate . And could you elaborate the camera black out issue?
Click to expand...
Click to collapse
My primary/back camera is always blank/dark/black when ever i open any camera app. It captures photos only when the flash is ON. Otherwise it takes black images. First, I thought it was related to hardware but i gave a try with stock(locked bootloader and only UL-ASUS_T00F-WW-2.21.40.30-user.zip, other zips couldn't fix it) and it worked fine. So the issue lies with unlocked bootloader/camera driver i guess, not with hardware. Moreover, when i turn on my front camera, it says "Camera failed to launch. Please reboot your device." pls check the attached log.
a8962383 said:
My primary/back camera is always blank/dark/black when ever i open any camera app. It captures photos only when the flash is ON. Otherwise it takes black images. First, I thought it was related to hardware but i gave a try with stock(locked bootloader and only UL-ASUS_T00F-WW-2.21.40.30-user.zip, other zips couldn't fix it) and it worked fine. So the issue lies with unlocked bootloader/camera driver i guess, not with hardware. Moreover, when i turn on my front camera, it says "Camera failed to launch. Please reboot your device." pls check the attached log.
Click to expand...
Click to collapse
I just looked at it.
connectLegacy: camera HAL module version 1 doesn't support connecting to legacy HAL devices
Other errors called by E/Camera_Conf and this:
[ 04-11 20:30:03.381 231: 5000 E/Camera_AtomAIQ ]
Error retrieving sensor params
[ 04-11 20:30:03.382 231: 5000 E/Camera_ControlThread ]
Error initializing 3A controls
[ 04-11 20:30:03.382 231: 5000 E/Camera_ISP ]
Xe Flash is supported only for primary camera!
[ 04-11 20:30:03.497 231: 5000 E/Camera_ScalerService ]
Atom_MessageQueue error: ScalerService queue should be empty. Find the bug.
[ 04-11 20:30:03.497 231: 5000 E/Camera_HAL ]
Error initializing ControlThread
So strange. Thats all.
a8962383 said:
My primary/back camera is always blank/dark/black when ever i open any camera app. It captures photos only when the flash is ON. Otherwise it takes black images. First, I thought it was related to hardware but i gave a try with stock(locked bootloader and only UL-ASUS_T00F-WW-2.21.40.30-user.zip, other zips couldn't fix it) and it worked fine. So the issue lies with unlocked bootloader/camera driver i guess, not with hardware. Moreover, when i turn on my front camera, it says "Camera failed to launch. Please reboot your device." pls check the attached log.
Click to expand...
Click to collapse
Hmm... Looks quite complicated. By the way did you check with other Camera Apps or try re-locking the bootloader? And I never got such issue. So which model are you precisely using, like a500cg or a502cg etc, which one??
PaletroxZ said:
Hmm... Looks quite complicated. By the way did you check with other Camera Apps or try re-locking the bootloader? And I never got such issue. So which model are you precisely using, like a500cg or a502cg etc, which one??
Click to expand...
Click to collapse
I have tried PixelMaster camera, CM default cam, CM cam2, Google Cam.........but the same issue persisted. My device is a500cg.
Mir Shahjahan said:
The ROM looks great. Thanks for this amazing work. I hope you'll fix all the bugs especially GPS
Click to expand...
Click to collapse
Other errors could be fixed but not the GPS. It's allmost impossible
a8962383 said:
I have tried PixelMaster camera, CM default cam, CM cam2, Google Cam.........but the same issue persisted. My device is a500cg.
Click to expand...
Click to collapse
Okay mate I'll look into it.
Mir Shahjahan said:
The ROM looks great. Thanks for this amazing work. I hope you'll fix all the bugs especially GPS
Click to expand...
Click to collapse
ChristopherXI said:
Other errors could be fixed but not the GPS. It's allmost impossible
Click to expand...
Click to collapse
I hope so too. Will need to check that out.