[LinOS][M][N] OPO 3.10 kernel (27/05) - ONE Original Android Development

[LinOS][M][N] OPO 3.10 kernel (27/05) - ONE Original Android Development

Hello guys,
Some of you guys will recognise me, I was trying to make progress on Sultan's 3.10 kernel on his topic. After a while I've wanted to do that from scratch, in new base, and now I can say it's done.
This kernel is the one all recent flagships' use. Also 3.10 kernels' support will end in Oct. 2017, while 3.4 ones will end in Apr. 2017.
In theory it should have better memory management, less battery consumption etc. It took me about 7-8 months to come to this point.
Currently everything works.
Extra features
* KCAL
* 6 new governors
* Touchscreen driver has been updated and optimized - also S2W added, you can find it in Kernel Aduitor
* Works with pelya's USB Keyboard app.
* New charger driver features:
They're placed in: /sys/devices/qpnp-charger-ed443000
You need to reach them from some terminal app or adb shell.
threea_charge
Making it 1 will activate experimental 2.5A charge. It's triggered if AICL mA is 2000(if you're not sure about AICL mA, simply disable AICL by below parameter), temperature is appropriate and screen is off.
Only use if you have 2.5A or above charger. Don't use QC's Quick Charge adapters.
Untested, but can't damage your phone.
disable_aicl
Making it 1 will disable AICL and charger driver will always try to take 2A from your AC/wall charger (there's no problem if you charger isn't 2A)
You need to replug adapter to see the effect.
max_aicl_rate
Max. charge current. (Not exactly if it's below 0 Celsius)
It should be one of those: 100,150,500,900,1200,1500,2000. Other values will be rounded. Values below then 100 and higher then 2000 won't be accepted.
Has no effect if AICL is disabled via above parameter.
If threea_charge is enabled and this parameter is 2000, max current will be 2.5A.
You need to replug adapter to see the effect.
fast_usb_charge Can also be found in Kernel Aduitor
Making it 1 will charge your phone through 900 mA if it's charging via USB port.
You need to replug adapter to see the effect.
charge_limit
It only accepts values between 0-100. Charger driver will cap charge percent to entered value. It's known that capping it to 50-60 percent increases battery life.
Making it 100 will revert the effect.
soft_aicl_vol
It must be between 4350 and 5000.
Default is OP2 value (4465 - but algorithm is different from LinOS and you shouldn't directly enter Sultan's or LinOS's value).
Don't change that if you don't know what it is.
Ramdisk changes
Last update: 17-02-2017
in fstab.bacon:
* F2FS filesystems must be mounted without noatime option.
* "/devices/platform/xhci-hcd" --> "/devices/*/xhci-hcd.0.auto/usb";
* "voldmanaged=usbdisk:auto" --> "voldmanaged=usb:auto";
in init.bacon.rc:
* qcom_oncrpc must be removed from loc_launcher (this is CM's mistake)
* netmgrd must also have system group
* qmuxd's user must be changed to root
in init.qcom.power.rc/init.recovery.bacon.rc:
* cpubw.40 must be changed to cpubw.47
Click to expand...
Click to collapse
These are only things different than CM ramdisk right now.
in anykernel patch format (all credits goes to @idprophecy)
## 3.10 ramdisk fixes
# fstab
if [ -f fstab.bacon ]; then
fstab="fstab.bacon";
backup_file $fstab;
elif [ -f fstab.qcom ]; then
fstab="fstab.qcom";
backup_file $fstab;
fi;
if [ -n $fstab ]; then
replace_string $fstab "/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs nosuid" "/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,nosuid" "/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs nosuid";
replace_string $fstab "/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs nosuid" "/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs noatime,nosuid" "/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs nosuid";
replace_string $fstab "/devices/*/xhci-hcd.0.auto/usb" "/devices/platform/xhci-hcd" "/devices/*/xhci-hcd.0.auto/usb";
replace_string $fstab "voldmanaged=usb:auto" "voldmanaged=usbdisk:auto" "voldmanaged=usb:auto";
fi;
# init.recovery.bacon.rc
if [ -f init.recovery.bacon.rc ]; then
qcomrecovery="init.recovery.bacon.rc";
backup_file $qcomrecovery;
fi;
if [ -n $qcomrecovery ]; then
replace_string $qcomrecovery "cpubw.47" "cpubw.40" "cpubw.47";
fi;
# init.qcom.power.rc
if [ -f init.qcom.power.rc ]; then
qcompower="init.qcom.power.rc";
backup_file $qcompower;
fi;
if [ -n $qcompower ]; then
replace_string $qcompower "cpubw.47" "cpubw.40" "cpubw.47";
fi;
# init.bacon.rc
if [ -f init.bacon.rc ]; then
qcomdevice="init.bacon.rc";
backup_file $qcomdevice;
elif [ -f init.oppo.common.rc ]; then
qcomdevice="init.oppo.common.rc";
backup_file $qcomdevice;
fi;
if [ -n $qcomdevice ]; then
replace_string $qcomdevice "# loc_launcher qcom_oncrps not needed" " group gps qcom_oncrpc inet" " # loc_launcher qcom_oncrps not neededn group gps inet";
replace_string_multiline $qcomdevice "# fix netmgrd service" "service netmgrd /system/bin/netmgrdn class mainn user rootn group radio" "service netmgrd /system/bin/netmgrdn class mainn user rootn # fix netmgrd servicen group radio system";
replace_string_multiline $qcomdevice "# fix qmuxd service" "service qmuxd /system/bin/qmuxdn class mainn user radio" "service qmuxd /system/bin/qmuxdn class mainn # fix qmuxd servicen user root";
fi;
## 3.10 ramdisk fixes
Downloads
Code:
Nobody knows is your warrant is still valid.
Also it's suspicious is there any warranty for OPO.
After you started to use this kernel, I'm not resposible for anything happened to your device.
* Encryption works but I cannot guarantee that it won't cause any data loss.
* They're all AnyKernel.
* There will be two types of build after 19/05, one with CM camera driver, one with CAF/Sultan camera driver.
27-05-2017:
With CM camera: https://www.mediafire.com/?7z672wl1y6xy275
With CAF/Sultan camera: https://www.mediafire.com/?sts35t5hd5ca3xr
19-05-2017:
With CM camera driver: https://www.mediafire.com/?4pkk3co7290lx1l
With CAF/Sultan camera driver: https://www.mediafire.com/?hohbwk9l805nrn0
09-04-2017: http://www.mediafire.com/file/h2k3moy0s6mxiht/09042017kernel.zip
A little nostalgia (It's too buggy, you have been warned)
26-08-2016: http://www.mediafire.com/file/6j5xw1j1lel1tra/260816kernel310.zip
Source code link is available bottom of this post.
Technical side
* It is based on LA.BF.2.1.2
* You can use both LA.BF and LA.BR prima, I'm using LA.BF one with some LA.BR commits.
* Tspp driver was causing bootloop, so i've disabled it. And I don't know is it used at all, it's disabled in apq8084 devices (like nexus 6) even.
* I'm compiling it with GCC 4.8. I've switched to Uber 6.0 after 09-01 build.
* KGSL drivers is pretty messed up after 30-08 build. It's my fault.
* And compiled DT is in in arch/arm/boot, it was different in 3.4 I think.
Pull requests are welcome.
You can use use/fork/develop this but you should give credit for 3.10 kernel on your releases.
Did you like my work?
I appreciate all the donations, it will keep me motivated, also I'm a student so it will help me in my life
Addendum: PayPal has been banned from my country, if PayPal denies your transaction and if you want to donate, I can give you my IBAN.
Credits
Sultan - this kernel would be impossible without his helps & his first 3.10 kernel attempt.
Ra1nst0rm - for helping me to upload repo - releasing this would be impossible due to creeping internet in here.
Mecca UL & idprophecy - for their insane effort to test and improve this kernel =)
XDA:DevDB Information
OnePlus One 3.10 kernel, Kernel for the OnePlus One
Contributors
erorcun, Sultanxda
Source Code: https://github.com/erorcun/android_kernel_oneplus_msm8974-3.10
Kernel Special Features: 3.10 kernel - better memory management and battery consumption in theory
Version Information
Status: Beta
Current Beta Version: 1.0
Created 2016-05-14
Last Updated 2017-05-27

Reserved

GREAT!

NICE!!!!

Proud cuz a turkish dude managed to do it
---------- Post added at 09:33 PM ---------- Previous post was at 09:28 PM ----------
This might be the biggest revolution to the OPO since the Sultan's CAF Rom and camera HAL.

Tested on f2fs Sultans stable Rom. Bootlooping on cm logo.
Sent from my A0001 using XDA-Developers mobile app

@DerRomtester
It's only for CM nightlies, i'm writing it to OP.
It could be related with f2fs too, I don't know.

erorcun said:
@DerRomtester
It's only for CM nightlies, i'm writing it to OP.
It could be related with f2fs too, I don't know.
Click to expand...
Click to collapse
Why don't you use anykernel so it also works on sultans rom but stock CAF camera drivers will be needed to work with oxygen blobs

nikhil18 said:
Why don't you use anykernel so it also works on sultans rom but stock CAF camera drivers will be needed to work with oxygen blobs
Click to expand...
Click to collapse
I can't make big changes anymore. It was freakin' hard to come to this point.
Maybe if I know diffs between sultan and cm kernel.

Testing

My country is famous with creeping internet, so I gave a chance to github import tool to import it from caf first, but it has been almost 1 day and progress bar still seems full, I think it got stuck.
I will be grateful to anyone who gives me LA.BF.2.1.2_rb1.5 kernel imported repo :silly: Ofcourse I can do it myself but I don't know when I can.
And I will add credits to one who upload it.

Nice to see someone continue 3.10 for bacon!
I'm going to try it soon.

Works beautifully with CM Nightly 15-05 on a secondary Multirom installation. GPS worked well for me, but during calls the other party couldnt hear my voice. So reluctantly removed for now. Hope you fix the issues and continue developing the kernel for our beloved OPO.

mucinch said:
Works beautifully with CM Nightly 15-05 on a secondary Multirom installation. GPS worked well for me, but during calls the other party couldnt hear my voice. So reluctantly removed for now. Hope you fix the issues and continue developing the kernel for our beloved OPO.
Click to expand...
Click to collapse
Yeah, GPS works well actually but it shouldn't be perfect since part of it crashes.
Thanks!

Source is up now, thanks to Ra1nst0rm.
Enjoy =)

@erorcun you are welcome
Will test it soon

erorcun said:
Source is up now, thanks to Ra1nst0rm.
Enjoy =)
Click to expand...
Click to collapse
Great work. Just checked your source.

Thats big step ahead :good:
Bluetooth works fine, GPS too, only f2fs doesnt.
Tested on nightly and RR

CraZY_BoY^ said:
Thats big step ahead :good:
Bluetooth works fine, GPS too, only f2fs doesnt.
Tested on nightly and RR
Click to expand...
Click to collapse
Thanks for testing bluetooth.

Nice development! Thanks for this!
Edit: Working nicely on a test install of Vanilla Unicorn (CM based)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Related

[Kernel] Rogue 1.4.3 "Rana" (Updated 11/20/11)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
***Built for 3G/4G and Wifi-Only Xoom's running 3.2.0, 3.2.1, and 3.2.2.***
-Rogue v1.4.3-
Rana
Presented By-
TDR
Bazar6
Steady Hawkin
Install Instructions-
-Make a nandroid in your current recovery then proceed
-Download zip file from link below
-Place zip on Micro SDcard
-Reboot into existing recovery
-Choose install zip and select the Rogue Kernel
-Confirm file, wait for it to finish flashing, then reboot
-Enjoy the Rogue Glory!!!
Download's:
Kernel-
Rogue 1.4.3 Rana
or
Rogue 1.4.3 N Rana (Stock clocks for GPU and some other core clocks (sclk, hclk, vde)
Add On's-
Flash any of these after the kernel
USB WWAN
Charge Light Toggle
Source-
Can be found on Github- HERE
Thank You-
Bigrushdog
Coolbho3000
Solarnz
Kcrudup
Cybertronic
Donate to TDR HERE
Stay Tuned For Future Releases!!!

-Partial Changelog-
1.4.3 Rana (Official Release)
+4G Xoom LoS fixed (synced patches from official Google/Moto source tree - Huge thank you to kcrudup!)
+Some other upstream patches
**Note: tun.ko module is now included with the kernel
**Possible issue: Xoom may lock up if suspended with USB OTG HDD connected
1.4.1 Electra (Official Release)
-No more support for Android 3.1
+Revamped installer, works on Android 3.2 and above (including Tiamat ROM 2.2.x)
+SIO (Simple I/O) I/O scheduler by default (CFQ and noop also available)
+SLQB (Queued Allocator) slab memory allocator
+Update modem driver from Qualcomm source
+Tegra framebuffer copy patch (via kcrudup)
*Configuration update with support for 4G Xooms (NOTE: there are reports of problems with some VZW Xooms)
*Fix tegra asm typo
*Fix typo in MDM6600 driver (thanks kcrudup)
1.3.1 Arcturus (Official Release)
+Rogue branding
+A bunch of upstream patches
+Handle corner case of non-US Android 3.2
+Added support for Android 3.2.2
+Even more upstream patches (thanks kcrudup and solarnz)
*Overhauled installation script (better detection of non-US Xooms, can force installation by toggling script asserts)
**Android 3.1 support is frozen and will be removed in future releases

-Special Instructions-
This version of Rogue comes packed with a maximum CPU frequency of 1.7GHz and user adjustable voltages for each frequency. Use these features responsibly! Do not select "Set on boot" unless you are confident the settings you chose are stable! Always make backups!
How to use the voltage control:
The stock frequencies and voltages in a kernel are not optimal for everyone. Userspace voltage control lets you either 'undervolt' (to save power) or 'overvolt' (to try and stabilize) any given CPU frequency to meet your needs.
Undervolting-
The easiest way to adjust these voltages is by using the app "Pimp my Cpu", available either from the Market or xda ([APP] 24 June 2011 : Pimp My Cpu 3.0 (OC/UV kernel control tool) - xda-developers). This app will let you to set an undervolt amount for each possible frequency, as well as fill some of the basic overclocking roles of a tool like SetCPU or Droid Overclock.
Note: at this moment, the app "Voltage Control" is not compatible with Launchpad 1.2.0.
Overvolting-
Unfortunately, Pimp my Cpu does not do overvolting, so you need to execute a shell command to set an overvolt amount.
Say for example 1600MHz isn't quite stable, and you want to give it a little help. From either adb shell or Terminal Emulator, execute the following commands:
su
echo "0 -25 0 0 0 0 0 0 0 0 0 0 0" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
The second line has a series of 13 numbers, mostly zeros. They represent the number of millivolts to subtract from the default voltage of each possible frequency, starting from the higest (1700MHz) to lowest (216MHz). So in the above example, we apply a negative 25 millivolt undervolt ( which transleted to a 25 millivolt overvolt) to the second fastest CPU frequency (1600MHz). Note that the minimum voltage is 770 millivolts and the maximum voltage is 1400 millivolts. If your new voltage exceeds these limits, it will not work.
Here is an example of bumping up 1500, just so you get how its done:
su
echo "0 0 -25 0 0 0 0 0 0 0 0 0 0" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
In Pimp my CPU, you will see the following as a result of the first command

Sweet man! Thanks for the hard work! I will give this a test run now.

Call me Noob but will this kernel work for Hammerhead 2.1?

diablo2224 said:
Sweet man! Thanks for the hard work! I will give this a test run now.
Click to expand...
Click to collapse
Thanks for the support bro!
Genshard said:
Call me Noob but will this kernel work for Hammerhead 2.1?
Click to expand...
Click to collapse
Yes it sure will

diablo2224 said:
Sweet man! Thanks for the hard work! I will give this a test run now.
Click to expand...
Click to collapse
let us know if you find a better stability with higher clock than 1.5 with voltage tweaks

joshndroid said:
let us know if you find a better stability with higher clock than 1.5 with voltage tweaks
Click to expand...
Click to collapse
That all depends on the Xoom...

Steady Hawkin said:
That all depends on the Xoom...
Click to expand...
Click to collapse
So true. The Xoom I use primarily has no issue at all running 1.7 Ghz night and day (it's the 3G model, although that doesn't really matter) but my wifi model (both bought on the same day) acts very poorly above 1.504. So, it's more luck than anything else, based on what others have posted as well, as to what speeds your Xoom will support. Goes without saying, be careful... I bricked an epic pushing it to far and foolishly ignoring the warnings it gave me where i could have prevented the expensive paper weight I ended up with.

The kernel seems to be working very well as expected. I've been running it for a bit now, and I am undervolted at -25 mV, and it's doing just fine. Can't tell if it's more stable than the previous build though because the previous build was pretty solid. No issues so far. Thanks again!

Awesome!!!
I flashed it.
Thx!!

I can't understand
what dose it mean
'Android 3.1 support is frozen and will be removed in future releases'
So this kernel are not currently support the Android 3.1??
or support now??

Hi, any instructions on how to use USB_wwan after insmod with
a 3g USB dongle?
Thanks!
Enviado desde mi MB860 usando Tapatalk

kokjsch said:
I can't understand
what dose it mean
'Android 3.1 support is frozen and will be removed in future releases'
So this kernel are not currently support the Android 3.1??
or support now??
Click to expand...
Click to collapse
It is supported in this kernel, but in the future we likely will not support it.

Thanks to answering my question.

lhurtado said:
Hi, any instructions on how to use USB_wwan after insmod with
a 3g USB dongle?
Thanks!
Enviado desde mi MB860 usando Tapatalk
Click to expand...
Click to collapse
Hi, I'm still not sure about using a 3G USB Dongle, but it should work with wired tethering from a phone.
Here are the instructions from bigrushdog.
USB Tether: Plug OTG cable into Xoom. Plug phone with microUSB cable into OTG cable. On phone, enable USB Tether. On Xoom, run the following in terminal or script manager (Scripter, GScript, Tasker) of your choice.
dhcpcd usb1
setprop net.dns1 8.8.8.8
The Xoom will not show any indication that there is a network connection. But pull up your browser and surf away.
Click to expand...
Click to collapse

Thanks Steady, stable as always

thanks.
one question, can not access wifi with HC3.2.2 on wi-fi only xoom(MZ604) whether this kernal can resolve that or we need to wait for new rom based on 3.2.2?
also which governor/scaling is best for your kernal?

musashiken said:
Hi, I'm still not sure about using a 3G USB Dongle, but it should work with wired tethering from a phone.
Here are the instructions from bigrushdog.
Click to expand...
Click to collapse
Thanks! I misunderstood the use of this module.

I flashed the 'N' version of this kernel and then I flashed the Charge lite toggle. Is there anything else I need to do to enable this? I flashed twice and the light still isn't on while charging.
One other thing, the only reason I haven't tried the non 'N' version of the kernel is because I use SetCPU instead of PimpMyCPU. Can you use SetCPU in order to set the overclock freq or is there a specific reason for using PimpMyCPU? I have done overclocking on my Droid Incredible so I am not a noob at it but at the same time I just wanted to ask before hand.
Xoom 3.2

[DEV][ROM] CYANOGENMOD 10.1[Galaxy 551][ARMV6-PROJECT] [PERM-DISCONTINUED]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
This is it, The CyanogenMod 10.1 by Ankur, purely built from source, and it is fast.
We are the parts of armv6 team
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Click to expand...
Click to collapse
New : Now Comes with ROM Manager support* (Included in ROM, don't use play store version. I JUST WARNED YOU !)
-Confirmed Working
Boot
Network/RIL
Mobile Data
2G/3G
Camera
Image Capture
Video Capture
2D Acceleration
3D Acceleration
Touch
Audio
Video without lag (240p)
SD Card
Physical Keyboard
Bluetooth
Root
ADB
Auto Rotation
GPS
Wifi
USB Mass Storage
Video Capture
FM Radio
Not Working
Media Scanner
HW Acceleration (360p videos lagging badly)
Known Bugs
Keyboard : To use virtual keyboard disable physical keyboard from Language and Input -> Default, after every reboot.
Media Scanner : Use Bluetooth file transfer app and other alternative web browser.
Sensor : In call sensor not work
XDA:DevDB Information
CyanogenMod 10.1 Galaxy Callisto, a ROM for the Android General
Contributors
ankur850, androidarmv6
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 2.6.x
ROM Firmware Required: Custom Recovery - CWM / TWRP
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2013-08-29
Created 2013-10-15
Last Updated 2013-10-15

Downloads & Changelog
#Build 5 - RC 3

Note 1 : Google Apps already included.
Note 2 : First boot may take 8-10 min.
Note 3 : Wipe data before flashing rom, don't wipe data after flashing rom.
FLASHING INSTRUCTION
Download "cm-10.1-20130827-UNOFFICIAL-callisto.zip".
Copy/move these zip to SD Card
Reboot into CWM Recovery.
Wipe Data/ Factory Reset. [Important - Don't wipe after flashing]
Install zip form sdcard > "cm-10.1-20130827-UNOFFICIAL-callisto.zip"
Advanced > fix permission
Reboot system now
Done !
CHANGELOG
27/08/2013
Code:
[ADD] ROM Manager support | OTA Update (app included in rom, don't use play store version, I JUST WARNED YOU)
[ADD] Link2SD
[UPDATE] Play Store 4.3.11
[REMOVE] Wifi-Tether
REMOVE[] USB-Tether
[REMOVE] Gmail (to free some space)
27/07/2013
Code:
[ ADD ] Wifi-Tether
[ ADD ] Usb Tether
[ ADD ] TaskManager
[ BUGFIXED ] Audio
[ BUGFIXED ] Camera
[ BUG FIXED ] FM
25/07/2013
Code:
[ ADD ] StreeView
[ ADD ] Gmail
[ ADD ] YouTube
[ UPDATE ] Play Store to 4.2.9
[ CHANGE ] wpa_supplicant
[ BUG FIXED ] USB Mass Storage
[ BUG FIXED ] WIFI
[ BUG FIXED ] GPS
[ BUG FIXED ] Alarm Clock
10/07/2013
Code:
[ CHANGE ] Ril Client
[ CHANGE ] Kernel
[ ADD ] HWcomposer lib
[ FIX ] SD Card, vold
[ UPDATE ] RC 5 source
[ UPDATE ] Google Apps
01/03/2013
Code:
Initial Build
[ WORKING ] BOOT
FAQ 
Code:
[COLOR="Red"]Q[/COLOR]. Where can i find performance and development settings?
[COLOR="Green"]A[/COLOR]. Go to About Phone in settings and click on build number 5-7 times,
and u have those options in your settings now.
[COLOR="Red"]Q[/COLOR]. When will the next release be available?
[COLOR="Green"]A[/COLOR]. First Rule of XDA is not to ask for ETA, so a new build will be
available as soon as i have some free time and some changes are made.
[COLOR="Red"]Q[/COLOR]. Why device is crashing and randomly rebooting ?
[COLOR="Green"]A[/COLOR]. Go to Performance setting and change the clock speed to 748 or minimum.
[COLOR="Red"]Q[/COLOR]. Why device is getting bootloop after flashing this rom ?
[COLOR="Green"]A[/COLOR]. Buddy, follow the instruction correctly and do every step that was in instruction.
[COLOR="Red"]Q[/COLOR]. How do i take a logcat?
[COLOR="Green"]A[/COLOR]. Your best buddy for this case is GOOGLE :)
Device Config
github.com/ankur850/android_device_samsung_callisto
Generic Source
github.com/androidarmv6
Kernel Source
github.com/ankur850/android_kernel_samsung_callisto

Addons and other Script
Addons and other Script
FacebookSync : Facebook contacts Sync
Apk SEEDER If u want your device to be lagfree, Must have app.
RAM Manager- Play Store Set it to balance for Multitask.
Note : USE either RAM Manager or Seeder, dont use both, they both may interfere with each other.
Note : If any other script/app you are using for performance let me know if it work.
MediaScanner - ReScan Media - for fix media scanner issue.
BlueTooth File Transfer - for fix BlueTooth file Reciever

Code:
- XDA for this great place
- Whole [URL="https://github.com/androidarmv6?tab=members"]armv6 team[/URL] for maintain the repo
- [URL="github.com/CyanogenMod"]CyanogenMod[/URL] for its source
- [URL="http://forum.xda-developers.com/member.php?u=4255685"]Ganster41[/URL] for his hack in libs
- WillingMagic for his original development
- Shaan
- [URL="http://forum.xda-developers.com/member.php?u=1107425"]lambgx02[/URL] for APK SEEDER
- [URL="forum.xda-developers.com/member.php?u=4170211‎"]Imbawind[/URL] for Adrenaline Engine
- [URL="forum.xda-developers.com/member.php?u=4148720‎"]TheWhisp[/URL] For kernel source
- [URL="http://forum.xda-developers.com/member.php?u=4894739"]Dodit Prodipta[/URL] - ROM Tester
- [URL="forum.xda-developers.com/member.php?u=4884066"]Praveen aka AshuGite[/URL] For work on performance - ROM Tester
- [URL="http://forum.xda-developers.com/member.php?u=4088531"]Abhinav Singh aka shiva4849[/URL] - ROM Tester
- Google !offcourse

1st to download.....
cool Ankur.... finally towards a stable build......
....
WiFi is working good tested again....
Check Below
also Quadrant Standard Benchmark Test For the rom

Flashing....
Inviato dal mio GT-I5510 con Tapatalk 2

Flashed but same errors phone fc... what to do...
Provide the new kernel link
Sent from my GT-I5510 using xda premium

AshuGite said:
Flashed but same errors phone fc... what to do...
Provide the new kernel link
Sent from my GT-I5510 using xda premium
Click to expand...
Click to collapse
got the same result
even after fix permission
back to cm 10
Edit:
when i tried to reflash
it's say installation aborted

AshuGite said:
Flashed but same errors phone fc... what to do...
Provide the new kernel link
Sent from my GT-I5510 using xda premium
Click to expand...
Click to collapse
link updated

followed instructions working good....
tested video capture working fine....

Thank you genius!
Seriously man, you're a rockstar!

:'( :'(
Can't taste it.
my phone still not repaired (display problem)
Samsung is not sending the required item to repair my phone.F**k you SAMSUNG!!

Smooth-ass!
The rom is very very smooth
Call quality is very good
only camera fcs
once the wifi fix arrives, this rom will be the best thing that has ever happened to this phone
cheerio ankur!

DOwnloading!!
Can't wait to test this awesome rom! thanks ankur!
EDIT : Stuck in bootloop! :/

vvaklnprm said:
Can't wait to test this awesome rom! thanks ankur!
EDIT : Stuck in bootloop! :/
Click to expand...
Click to collapse
Did u followed the steps as mentioned.....
Sent from my GT-I5510 using xda premium

Same stuck in bootloop problem
I am posting this on behalf of schengawegga, as he is not able to post in this thread
Hi AsheGite,
i´ve got the same problem as vvaklnprm:
"EDIT : Stuck in bootloop! :/ "
And i´ve got the same problem with the CM10 too, but the solution of this problem at CM10 was the boot.img from this Post (Number 2): http://forum.xda-developers.com/show....php?t=2171876
2).Stablitiy
Instability of cm10 is due to default value is set to 800+mhz of Kernel that cause instability and cpu strain and frequent restarts
Grab this boot.img...Link(for Callisto only aka Galaxy 551)
a)Default is set to 729 mhz
b)some Minor Changes in ramdisk
Could you make a boot.img that is booting with at least 729MHz?
I think than it will work at vvaklnprm and my callisto too.
Regards
Schengawegga

vvaklnprm said:
I am posting this on behalf of schengawegga, as he is not able to post in this thread
Hi AsheGite,
i´ve got the same problem as vvaklnprm:
"EDIT : Stuck in bootloop! :/ "
And i´ve got the same problem with the CM10 too, but the solution of this problem at CM10 was the boot.img from this Post (Number 2): http://forum.xda-developers.com/show....php?t=2171876
2).Stablitiy
Instability of cm10 is due to default value is set to 800+mhz of Kernel that cause instability and cpu strain and frequent restarts
Grab this boot.img...Link(for Callisto only aka Galaxy 551)
a)Default is set to 729 mhz
b)some Minor Changes in ramdisk
Could you make a boot.img that is booting with at least 729MHz?
I think than it will work at vvaklnprm and my callisto too.
Regards
Schengawegga
Click to expand...
Click to collapse
just flash the rom and patch along with wipe data, fix permission.
Move towards Setting and change frequency to 748 mhz in Performance Setting

pls try to read instructions carefully....
Enable developer and performance tab and then set cpu frequency...
Also for solution to keyboard prblm i suggest using hackers keyboard app and make it default instead of aosp keyboard... attaching ss follow the settings...
Code:
[url=https://play.google.com/store/apps/details?id=org.pocketworkstation.pckeyboard&hl=en]Hacker's Keyboard Google Play[/url]
Also to improve performance donload below packages....
And remember do it on own risk....
Code:
[url=forum.xda-developers.com/showthread.php?t=2361379]Pure Performance Pack CM[/url]
....
[url=http://www.4shared.com/zip/U1a3zQsU/Cyanogenmod_101_Performance_pa.html]CM10.1 Performance Pack mod by AshuGite[/url]

links please!
can't wait to try it out
EDIT: doesn't boot at all and i followed instructions perfectly

[ROM] CM-10.2 | AOSP 4.3 Jellybean [KANG] [Oct-11]

| CyanogenMod 10.2 - Android 4.3.1 - Jellybean |
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include
/*
* Your warranty is now likely void.
*
* I am not responsible for bricked devices, dead SD cards,
* spontaneous combustion, or any other host of cosmic penalties
* which may befall you, your family, or your phone.
*
*/
If you ask any questions that are answered in the first two posts your question will be ignored. If you don't search prior to posting you will be ignored. If you don't read you will be ignored. If you've done all that and still don't have an answer then feel free to ask your question. Ambiguity doesn't help anymore. Elaborate. It's that simple.
Click to expand...
Click to collapse
Built from CM source
Service
Text
Call
Audio
WiFi
Google Now
Bluetooth
GPS
MMS
Video playback
Audio playback
Camera
Camcorder
UMS
You tell me
Do NOT use superwipes
Wipe everything except sdcards
** (if you are simply applying an update to this rom base this might not always be required)
*** ((but do not report bugs if you didn't full wipe))
Flash ROM
Flash GAPPS
Reboot
???
Profit
To enable Developer Options and Performance go to Settings, About Phone and repeatedly press Build Number.
If you use ADB read this: PSA by CM
If you use reboot to recovery read this: PSA by CM
Regarding new Superuser: PSA by CM
android1234567 for figuring out initial boot. if it wasnt for his stubberness we probably still would be rebooting to recovery
Evervolv for their wonderful kernel which my kernel is 98% based on
elginsk8r for his work on the glacier device tree and kernel. These repos were the base of my build
And any and all users in this thread who contirbuted or will contribute to making this ROM as stable as possible
NineInchNails for being an awesome dev partner, moral support and friend!
dastin1015 for being an awesome dev partner and friend!
android1234567 for being an awesome dev partner and friend!
android1234567 for all the help with the kernel, without you we wouldn't have new kernel
A bunch of thanks to arco, for all his updates to our kernel, our display libs, our media libs, and for fixing the video playback glitching, and for being a good friend and dev mentor.
All my supporters!
I really didn't want to do this but people keep asking so here is a donation link if you want to buy me a coffee or pack of smokes (I go through a lot sitting on the PC messing around lol) go ahead. But not required or expected by any means
Note: The name on the paypal account may say patricia, this is because it's a family paypal account.
Thanks and happy flashing!
Download link is in 2nd post

Oct-11
* Fixed Torch not staying on when screen off
* Lots of camera fixes
* Fixed mic with some VoIP apps (Tango, Viber
* ramdisk init script cleanup (evervolv)
* A whole bunch of kernel updates including headset and display code re-writen (Evervolv)
* Kernel updated to Linux 3.0.99
* Build tagged 4.3.1_r1
* A lot of other updates I'm probably forgettting, plus all upstream changes
Sep-17
* Fixed SD card mount
* Fixed brightness/sensors
* Added CMAccount
* Upstream: Android tagged "Android 4.3_r3"
* Any upstream changes at time of compile
* Note; sorry for the delay
Sep-6
* Fixed front facing camera
* General cleanup
* Any upstream changes at time of compile
Aug-24
* Fixed Torch FC
* Attempt to fix data drops for some people
* Any upstream changes at time of compile
Aug-22
* Fixed front facing camera
* Any upstream changes at time of compile
Aug-19
* Fixed mounting SDcard over USB
* No longer using prebuilt audio libs from 10.1
* Couple overlooks to the media libs compiling (weren't grabbing correct headers)
* Bugfix: Root access will now be enabled by default without having to do the "trick"
* Any upstream changes at time of compile
** Note: please use the updated gapps (8/13) linked below or you will most likely have issues
Aug-13
* Initial release everything seems to be working well
ChronicKernel
Kernel now based on Evervolv's kernel with a few changes by me, including:
* Compiled with linaro
* Removed/Disabled KSM
* Removed ZRAM
* Optimized and compiled with with the "Optimize a lot, or -o3 option)
* Added more I/O schedulers
* Tweaked voltages a bit
* PMEM memory mapping tweak to remedy soft-reboots with AOSP 4.2/4.3/CM-10.1/10.2
These settings were changed by me to help make the kernel more stable with our ROM, observed with tests by me. if you want to use another kernel please feel free. but support will not be provided unless you are running the kernel included with the ROM
Other Features of the kernel include:
* OC to 1900Mhtz (default 1024Mhtz, Recomended: 1200Mhtz)
* Undervolted
* Added CPU Governors: Smartassv2, lazy, lagfree, interactiveX
* User-configurable CPU OC
* User-configurable CPU default governor (ondemand = default)
* User-configurable I/O scheduler (default = DEADLINE)
Team Hydra Github (main): https://github.com/Team-Hydra
CyanogenMod Github: https://github.com/CyanogenMod
ROM : cm-10.2-20131011-Albinoman887-glacier.zip
GAPPS: : HERE or HERE (Mirror)
Goo.im Repo : CLICK HERE
* This ROM can also be downloaded directly with GooManager *

first create the folder structure for your source. I suggest creating android/system n your home directory.
Now cd into this directory enter this command
Code:
repo init -u git://github.com/Team-Hydra/android.git -b cm-10.2
repo sync
( if you have a pretty decent /internet connection (10-20mbps+) you can add -j and then a number ater repo sync i recomend something like repo sync -j10 )
Once you have done that your ready to go. simply run:
Code:
. build/envsetup.sh
./vendor/cm/get-prebuilts
lunch cm_glacier-userdebug
mka bacon
make sure before you start a new build to always run make clobber
If anyone would like to help bug bash with me feel free. if you make any progress send me a pull request
P.S. I HIGHLY recomend setting up ccache if you are going to compile a lot you can read more about ccache here: Initializing a Build Environment and scroll down to the "set up ccache" section
Happy Developing,
Albinoman887

1st
First!

Lol yes! 4.3 let the porting begin! thanks so much for this man.
Sent from my HTC Glacier using xda app-developers app

oouuu yeaah nice work man:good:
bug: everytime I reboot my notification light is on and says my battery its charging - I just plug in and unplug from charger and its ok...just want to report, no big deal
update: I have this bug still even I flash other rom, maybe its hardware problem...sry if I am wrong but never encountered this problem until now

Thank you!
Thank you for taking the time and effort to build cm 10.2! I've spent a few minutes poking around, and discovered that su doesn't function for me. TB tells me that /system/bin/su fails, terminal shows it doesn't work but no error message is produced. Logcat says:
Code:
D/su ( 4659): starting daemon client 10041 10041
E/su ( 4660): connect failed with 2: No such file or directory

I also am with the same issue. I've flashed superuser and it didn't stick
Sent from my myTouch 4G using xda premium

Try flashing Koush's experimental 4.3 root
Sent from my HTC Glacier using xda app-developers app
---------- Post added at 09:44 PM ---------- Previous post was at 09:32 PM ----------
I'd like to say that with this release of 4.3, everyone should really try and help out with the headset issue.
Older kernels won't work anymore so you cannot flash .62 or .64s anymore, meaning we are all stuck with the issue unless we all try fixing it.
I dont know much but I will say that we should try and get dmesg and last_Procs (or whatever it is) as we can.
I'm not saying it wasnt important before, but now we are really left with the issue. The devs have tried a lot and now the users gotta help even more.
I think Elgin tells you the commands in his evervolv thread. Hopefully we can all fix this issue
Sent from my HTC Glacier using xda app-developers app

jggimi said:
Thank you for taking the time and effort to build cm 10.2! I've spent a few minutes poking around, and discovered that su doesn't function for me. TB tells me that /system/bin/su fails, terminal shows it doesn't work but no error message is produced. Logcat says:
Code:
D/su ( 4659): starting daemon client 10041 10041
E/su ( 4660): connect failed with 2: No such file or directory
Click to expand...
Click to collapse
Hi Albionman,
I tried few different superusers, even the new experimental 4.3 but no luck.
also couldnt see "users" the new feature in 4.3
batterywise & performance wise its silky smooth so far...thank you for this

JukiCro said:
oouuu yeaah nice work man:good:
bug: everytime I reboot my notification light is on and says my battery its charging - I just plug in and unplug from charger and its ok...just want to report, no big deal
Click to expand...
Click to collapse
I don't have this issue just camera didn't work until reboot. Also camera jb+ fixes the green line but flash is better timed in the stock camera. So far very nice rom. Thanks
Sent from my GT-P3113 using xda premium

not as stable as the 4.2 rom unfortunately
USB Mass Storage doesn't work for me AT ALL. Tells me I can safely remove the SD card when I try to turn it on. I did a full wipe and everything too...
got an "error retrieving information from server" when I try downloading from the play store
and camera force closes
Just got one random reboot too. Guess I'll be reverting back to 4.2 for now :'(

jggimi said:
Thank you for taking the time and effort to build cm 10.2! I've spent a few minutes poking around, and discovered that su doesn't function for me. TB tells me that /system/bin/su fails, terminal shows it doesn't work but no error message is produced. Logcat says:
Code:
D/su ( 4659): starting daemon client 10041 10041
E/su ( 4660): connect failed with 2: No such file or directory
Click to expand...
Click to collapse
usb mas storage works. i just tested it.... unless i forgot to apply the fix to your build or something
and the SU isssue. i need to put this in the OP its a bug with 10.2. enable developer options by going to about phone and tapping build number repeatedly. then go to developer options and switch root access to apps and adb and back to apps. then it will work

OK i updated the op with the superuser trick. its in bold towrds the bottom of the first post. please point any questions to that. thanks

SU Works
Thank you for showing us the SU trick, works like a charm. However, the USB storage issue is present. It first says safe to remove then resets, after a second attempt the process initiates and goes nowhere.

Doogitronix said:
Thank you for showing us the SU trick, works like a charm. However, the USB storage issue is present. It first says safe to remove then resets, after a second attempt the process initiates and goes nowhere.
Click to expand...
Click to collapse
You are right SU working and USB storage have issue also when open gallery phone goes to reboot and FFC unfortunately gallery crashed.
Sent from my myTouch 4G using xda app-developers app

Doogitronix said:
Thank you for showing us the SU trick, works like a charm. However, the USB storage issue is present. It first says safe to remove then resets, after a second attempt the process initiates and goes nowhere.
Click to expand...
Click to collapse
hview said:
You are right SU working and USB storage have issue also when open gallery phone goes to reboot and FFC unfortunately gallery crashed.
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Logcats would help a lot from these errors. Get a logcat app from the store, run it and try to do the things that are going wrong for you. Get last-ksmg if you are having reboots. Use paste bin to post your results. Look up cnote74's paceman he has link to instructions on how to log errors. The more info you can give the devs, from different phones would help them a lot.
Sent from my HTC myTouch 4g using xda app-developers app

camera is fine for me,
have screen flickering more often then before,
SU problem, yeah I had bug when I run titanium backup but I went to settings - superuser - closed it, and its fine
and about USB storage...I just pull out my sd card and stick it in computer, becouse since I flashed my first jb 4.2.2 I have that bug with every rom and it sucks, but I can live without it
anyway great job keep it up:good:

GronHog said:
Logcats would help a lot from these errors. Get a logcat app from the store, run it and try to do the things that are going wrong for you. Get last-ksmg if you are having reboots. Use paste bin to post your results. Look up cnote74's paceman he has link to instructions on how to log errors. The more info you can give the devs, from different phones would help them a lot.
Sent from my HTC myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
Logcat app: http://forum.xda-developers.com/showthread.php?t=1123129
Enjoy!

logcat for camera issues
This is a logcat for my camera issue
Not sure if I've done it right

[Q] Knock-On LG G2 feature on Redmi

Hi All,
Whether the LG G2's Knock On (Double tap to wake) feature can be incorporated in Redmi 1S. I am ok with a good launcher which support this feature as I cant root the device as its enabled for official mails
Thanks in Advance

It can be implemented only through kernel. Unless xiaomi releases kernel sources, nothing can be done!

Gh0sT.RPG said:
It can be implemented only through kernel. Unless xiaomi releases kernel sources, nothing can be done!
Click to expand...
Click to collapse
Yes , all mokee , aosp , cm11 ,carbon, pac etc are using the stock kernels , though there were talks of using some other devices kernel which was next-to-almost-compatible with Redmi.
on cm11 i tried flashing their kernel with update v45, even that failed and gave me bootloops.

kapil.git said:
Yes , all mokee , aosp , cm11 ,carbon, pac etc are using the stock kernels , though there were talks of using some other devices kernel which was next-to-almost-compatible with Redmi.
on cm11 i tried flashing their kernel with update v45, even that failed and gave me bootloops.
Click to expand...
Click to collapse
you changed the ramdisk?

saurabhrck said:
you changed the ramdisk?
Click to expand...
Click to collapse
I just changed bootanimation and init.qcom.post.boot.sh for mpdecision tweak and max/min freq ..
before the kernel flash I have booted phone 20+ times in last weeks, never bootlooped.

kapil.git said:
I just changed bootanimation and init.qcom.post.boot.sh for mpdecision tweak and max/min freq ..
before the kernel flash I have booted phone 20+ times in last weeks, never bootlooped.
Click to expand...
Click to collapse
I just tried to repack latest cm11 kernel for mokee as mokee is using old kernel. I changed the ramdisk, the device boots up but wifi is not working. but the thing is I can't find any wifi module in those kernel to swap. do you have any suggestion regarding thsi wifi module

can we use mokee wlan.ko ?
saurabhrck said:
I just tried to repack latest cm11 kernel for mokee as mokee is using old kernel. I changed the ramdisk, the device boots up but wifi is not working. but the thing is I can't find any wifi module in those kernel to swap. do you have any suggestion regarding thsi wifi module
Click to expand...
Click to collapse
It could be because mokee old kernel has this wlan.ko as loadable module
Can you try replacing the cm11's ko with the one attached ?
Code:
[email protected]:# find /system -name wlan.ko
/system/lib/modules/wlan.ko
[email protected]:# ls -l /system/lib/modules/wlan.ko
lrwxrwxrwx root root 2014-11-12 07:20 wlan.ko -> /system/lib/modules/pronto/pronto_wlan.ko
[email protected]:# md5sum pronto_wlan.ko
8f99e1923e2a25f0f7cc57ff62e5683d pronto_wlan.ko
when I enable Wifi
# lsmod
wlan 3616884 0 - Live 0x00000000 (O)
relevant console logs in mokee startup
<6>[ 1.414962] wcnss_wlan probed in built-in mode
<6>[ 11.033752] wcnss_wlan triggered by userspace
<6>[ 12.138179] wcnss_wlan_ctrl_probe: SMD ctrl channel up
<6>[ 555.845568] wlan: loading driver v3.2.3.172
<3>[ 555.964780] wlan: WCNSS WLAN Version 1.5.1.2, Host expected 1.4.1.2
<6>[ 555.964799] wlan: WCNSS software version 120418
<6>[ 555.964811] wlan: WCNSS hardware version WCN v2.0 RadioPhy vUnknown with 19.2MHz XO
<6>[ 556.014001] wlan: driver loaded

kapil.git said:
It could be because mokee old kernel has this wlan.ko as loadable module
Can you try replacing the cm11's ko with the one attached ?
Code:
[email protected]:# find /system -name wlan.ko
/system/lib/modules/wlan.ko
[email protected]:# ls -l /system/lib/modules/wlan.ko
lrwxrwxrwx root root 2014-11-12 07:20 wlan.ko -> /system/lib/modules/pronto/pronto_wlan.ko
[email protected]:# md5sum pronto_wlan.ko
8f99e1923e2a25f0f7cc57ff62e5683d pronto_wlan.ko
when I enable Wifi
# lsmod
wlan 3616884 0 - Live 0x00000000 (O)
relevant console logs in mokee startup
<6>[ 1.414962] wcnss_wlan probed in built-in mode
<6>[ 11.033752] wcnss_wlan triggered by userspace
<6>[ 12.138179] wcnss_wlan_ctrl_probe: SMD ctrl channel up
<6>[ 555.845568] wlan: loading driver v3.2.3.172
<3>[ 555.964780] wlan: WCNSS WLAN Version 1.5.1.2, Host expected 1.4.1.2
<6>[ 555.964799] wlan: WCNSS software version 120418
<6>[ 555.964811] wlan: WCNSS hardware version WCN v2.0 RadioPhy vUnknown with 19.2MHz XO
<6>[ 556.014001] wlan: driver loaded
Click to expand...
Click to collapse
which rom's is it? If I wanna repack cm11's kernel to mokee I will need the cm11's .ko file. right? so which rom's is it?

saurabhrck said:
which rom's is it? If I wanna repack cm11's kernel to mokee I will need the cm11's .ko file. right? so which rom's is it?
Click to expand...
Click to collapse
I am on mokee which has wlan as loadable module and may be thus shipped in ROM.
if CM has this inbuilt , you may have to disable the wifi and then insmod this ko.
pac also has this loadable
# cd /armani/ROMS/pac_armani_4.4.4.RC-2_20141026-175447/system/lib/modules/pronto
# md5 pronto_wlan.ko
MD5 (pronto_wlan.ko) = 6fc7aba9195e29702dac09dd384bdb00

it worked! all modules are working now. had to copy cm11's pronto_wlan.ko to mokee after kernel flash. and reboot!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

saurabhrck said:
it worked! all modules are working now. had to copy cm11's pronto_wlan.ko to mokee after kernel flash. and reboot!
Click to expand...
Click to collapse
Glad , it helped.
Can you please make a small writeup about how to use a newer stock kernel with mokee/CM
( I think this is what you achieved , right ? )

saurabhrck said:
it worked! all modules are working now. had to copy cm11's pronto_wlan.ko to mokee after kernel flash. and reboot!
Click to expand...
Click to collapse
Can you make a flashable image of the new kernel for mokee? THX
LE I found latter the post you've made on developer...

kapil.git said:
Glad , it helped.
Can you please make a small writeup about how to use a newer stock kernel with mokee/CM
( I think this is what you achieved , right ? )
Click to expand...
Click to collapse
I already made s thread in dev subforum.

Gh0sT.RPG said:
It can be implemented only through kernel. Unless xiaomi releases kernel sources, nothing can be done!
Click to expand...
Click to collapse
kernel source has already been released. are you try to compile the kernel with dttw or s2w?

[ROM][5.1.1][OFFICIAL] CyanogenMod 12.1 for S3 Neo[LEGACY]

[ROM][5.1.1][OFFICIAL] CyanogenMod 12.1 for S3 Neo[LEGACY]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: PLEASE ALSO READ ALL OF THE FAQ IN THE SECOND POST. IT COVERS MANY OF THE COMMON PROBLEMS AND QUESTIONS!
CyanogenMod 12.1 is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lolipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
The source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Changelog:
https://www.cmxlog.com/12.1/s3ve3g/
Requirements:
Custom recovery (either TWRP or CyanogenMod)
Soon other things will be added
Known Bugs/Issues: (fixed nightly date)
NFC
If camera not working flash this: LINK
Offline charging(02.09.2016)
(Please don't ask ETA for any bug fixes)
Bug reports for this ROM should be officially submitted via CyanogenMod's Jira bug tracking sytstem. Please fully read the FAQ entry on bugs and bug submission before submitting any tickets.
FAQ, other information:
Soon
Download:
https://download.cyanogenmod.org/?device=s3ve3g
Note to users: I'm not responsible if you brick your phone. See the disclaimer above.
Note to admins/moderators: I'm not a developer / contributor of CyanogenMod and not associated with Cyanogen, Inc. in any way. If this thread is inappropriate, please move/delete it.
Thanks to These People:
Zola
@rox
Abhisek Devkota
Samsung Devs
CyanogenMod Devs
XDA:DevDB Information
Cyanogenmod12.1, ROM for the Samsung Galaxy S3 Neo
Contributors
n1kolaa, Zola III
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: No Longer Updated
Stable Release Date: 2016-08-22
Beta Release Date: 2015-10-19
Created 2015-09-23
Last Updated 2018-05-14

How to report problem with new kerel or rom?
tonyp said:
We're on a development site - at least in theory.
To help out development without actually having some knowledge it's really important to know how and when to get logs.
Lately more and more people in this section do grab appropriate logs, which is a good thing and has already helped in fixing a bunch of bugs.
To stop (especially new) people from constantly asking how to get logcats I decided to hand out a quick reference on how to grab logs efficiently via adb / terminal / app.
There is an app which can export apps (see the end of this post), but you should learn how to get logs via adb anyways, as a dmesg is often crucial in case of debugging bsods.
I won't post instructions in how to get adb working - you can use Google or take this CM wiki entry as a starting point.
The three most important log types are:
logcat: the logoutput of the Android system
radio logcat: the log outpur ot your System / BB / RIL communication
kernel log (kmsg / dmesg): the kernel messages
Additionally there's the last_kmsg which is a dump of the kernel log until the last shutdown.
Normal Logcat:
Code:
adb logcat -v time -d > logcat.log
Radio Logcat:
Code:
adb logcat -b radio -v time -d > logcat_radio.log
Note: Cyanogenmod (based) ROMs require the following setting to export kernel logs via adb:
Settings - Developer Options - Root access - choose: "Apps and ADB"
Kernel Log:
Code:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
Code:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
For getting the logs via the Terminal Emulator app the commands differ a little:
Get logs via Terminal Emulator:
Normal Logcat:
Code:
logcat -v time -d > /sdcard/logcat.log
Radio Logcat:
Code:
logcat -b radio -v time -d > /sdcard/logcat_radio.log
Kernel Log:
Code:
su -c dmesg > /sdcard/dmesg.log
Last_kmsg:
Code:
su -c "cat /proc/last_kmsg" > /sdcard/last_kmsg.log
Notes:
-v time will include timestamps in the logcats
-d will export the complete log.
If you want to save a continuous log you can remove the -d parameter - then you need to cancel the logging process via CTRL+C.
To export a continuous kernel log use adb shell su -c "cat /proc/kmsg" > dmesg.log (and cancel it via CTRL+C again).
Exporting logs with an app:
I used to recommend Lumberjack for grabbing logs, but it doesn't work with Jellybean properly anymore and fails to export the dmesg.
I googled for a while and found a great (and fully open sourced) alternative to export logs: SysLog
With this great app there are no more excuses - at least open the app, export all 4 log types and attach the zip file from /sdcard/SysLog to your bug report.
Before anyone asks (duh!), Kernel log = dmesg, Last kernel log= last_kmsg, main log = logcat, modem log = radio log.
Lumberjack still is great to have a look at logs on the phone, but for exporting you probably should use SysLog as it does it quickly and reliable
SysLog (source):

Click to expand...
Click to collapse
#o#
tonyp said:
When to post which kind of logs:
If you got any kind of ROM problems - especially problems with Apps like force closes, attach a logcat.
If there are problems while calling or with your signal attach a radio logcat to the normal logcat.
In kernel threads or on issues which might be kernel related (from A as auto brightness to Z as ZRAM) you need a kernel log
If you had a sudden reboot attach a last_kmsg, then we can check if it's been kernel related
As our phone has always been on the edge of bsod's and freezes, some special notes about them as well:
If you had a bsod and/or freeze a logcat dmesg after rebooting is useless, as it doesn't show anything from before the reboot
There are two things you can do:
While the phone's screen is black connect the cable to your computer and check if the device is accessable via adb (check e.g. with "adb devices").
If it is export the dmesg like explained above. If not go on to step 2:
Note that two of the bsod problems of the ICS/CM kernel have been fixed by pengus by the logs I managed to get while the phone has been in a bsod - which means this is crucial!
Pull the battery and insert it again as quickly as possible. Why? The phone does hold a so called last_kmsg in RAM.
It's non-permanent memory, which means it doesn't survive a loss of power - sometimes we're in luck by a quick pull though.
If we're not in luck the file will be empty or contain scrambled characters.
Last but not least some general remarks:
If you don't provide useful logs we can not help you in 95% of the cases in case we can't reproduce it.
Buf even if we could reproduce it - let's assume one of YOUR apps is force closing. Why should we install the app to reproduce the problem and get the logs ourselves.
YOU want help, so YOU should provide the log.
Every real dev with some coding knowledge will need logs to fix the bugs.
This site is called xda-developers - which means that the initial intention of this forum is the actual development itself - and not "making your phone cool".
The least you can (and must) do is to provide useful help with a clear problem description and attached logs when you run into some issues
Click to expand...
Click to collapse

Donations for s3 dual sim
Use "Send payment" option on paypal
@Ahmad Tawfik: 1,62 USD; 1,18 USD
@S3-Neo 5 USD
@naik2902 6.00 USD
@aelfinn 5.51 USD
@St.Ungulant 5.49 USD
Ulrich 10.99 USD!
@Droidaner 13.49 US
I need about 50 euros for used dual sim phone

FAQ POST
Q: When you will realse CM13.0?
A: DON'T ASK FOR ETA(ETA = Estimated Time of Arrival)

Reserved #2

Is offline charge working with this kernel?
Edit:
sorry but I did not read the 1st post

Everything is fine
Installed and booted without issue. Kernel seems to be changed. :good: :highfive:

Is that working on Resurection Remix 5.5.6 ?

Removed

Ahmad Tawfik said:
Offline charge isn't working for me
Click to expand...
Click to collapse
Read OP...
" ##Bugs:##
no bugs so far(offline charging like cm12.1) "
Btw thanks n1kolaa!

Zokhii said:
Read OP...
" ##Bugs:##
no bugs so far(offline charging like cm12.1) "
Btw thanks n1kolaa!
Click to expand...
Click to collapse
I hope you like it
Np It will be assome to rate it 5 starts and make review.

ahmo67 said:
Is that working on Resurection Remix 5.5.6 ?
Click to expand...
Click to collapse
if its based on cm12.1 it shoud.
Take a backup if you not shure.

Mediafire folder is empty for me

jad88 said:
Mediafire folder is empty for me
Click to expand...
Click to collapse
https://www.mediafire.com/folder/3c3y68hehuv9t/n1kernel

MediaFire links not working...

n1kolaa said:
https://www.mediafire.com/folder/3c3y68hehuv9t/n1kernel
Click to expand...
Click to collapse
It's the same... Maybe it's my browser

Is this kernel base on Rox kernel?
And can you add this future for color calibration --> http://forum.xda-developers.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080
We need this futures.
---------- Post added at 01:48 PM ---------- Previous post was at 01:34 PM ----------
jad88 said:
It's the same... Maybe it's my browser
Click to expand...
Click to collapse
Download one buy one !

Sectorian said:
Is this kernel base on Rox kernel?
And can you add this future for color calibration --> http://forum.xda-developers.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080
We need this futures.
---------- Post added at 01:48 PM ---------- Previous post was at 01:34 PM ----------
Download one buy one !
Click to expand...
Click to collapse
I wont add it. Its based on Rox kernel

I had to login to my mediafire account. It works on latest RR. (Flashed with flashify)

Sorry, one question. If i flash your kernel, did i lose my data?

Develop Bugs

welcome