Hello all, so I have finally made my own kernel from source
Haven't added anything to it, but I wanting to OC it a bit.
I have been looking through the .C files of the source but can not come up with anything, the closest I have gotten is this located in the freq_table.c
Code:
/*********************************************************************
* FREQUENCY TABLE HELPERS *
*********************************************************************/
int cpufreq_frequency_table_cpuinfo(struct cpufreq_policy *policy,
struct cpufreq_frequency_table *table)
{
unsigned int min_freq = ~0;
unsigned int max_freq = 0;
unsigned int i;
But not sure where exactly this leads to set the parameters, any help will be greatly appreciated, thanks!
Ask Damian
Sent from my GT-I9000 using XDA App
check attachements (patches and whole files) to my post with insane kernel. (sig) This might give you a hint where to look, you are welcome to implement it differently (maybe will be more stable). The files are so-called raspdeep's oc code.
Can somebody point me on kernel for GB 2.3.4 supporting Voodoo Color? Thanks.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#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. Hard. A lot.
*/
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.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATION
Click to expand...
Click to collapse
If this thread becomes a mess, I'll lock it immediately
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
WIKI
Click to expand...
Click to collapse
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/N7000_Info
HOW TO INSTALL
Click to expand...
Click to collapse
First time installing CyanogenMod 10.2 to your Galaxy Note, or coming from another ROM:
- Read known issues ans FAQs
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of CyanogenMod 10.2:
- Copy CM10.2 ZIP to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Reboot
Upgrading from CyanogenMod 10/10.1:
- Read known issues ans FAQs
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- Wipe data, we're not sure if everything will work yet.
- Reboot
SCREENSHOTS
Click to expand...
Click to collapse
{
"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"
}
KNOWN ISSUES
Click to expand...
Click to collapse
Known bugs:
- some minor graphics glitches
- no camera fix has been merged
Remember we just merged yesterday (26th july), expect bugs in apps
DOWNLOADS
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2381499
CHANGELOG
Click to expand...
Click to collapse
http://changelog.bbqdroid.org/#/n7000/next
SUPPORT
Click to expand...
Click to collapse
Chat:
http://webchat.freenode.net/?channels=teamhacksung-support
irc.freenode.net #teamhacksung-support
Don't expect any support if you:
- are not running stock cm-kernel
- have installed any mods
- have modified system files
DEAR KANGERS
Click to expand...
Click to collapse
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't mean Out-of-Respect!!!
SUPPORT US
Click to expand...
Click to collapse
If you want to donate a few bucks for the work we're doing in our freetime:
I will get new battery today and test this 4.3
Wysłane z mojego GT-N7000 za pomocą Tapatalk 4
So dev thread got locked within just three days.
I see, Note N7000 people are the craziest and notorious trolls here in XDA. :laugh:
Thanks for your support @XpLoDWilD.
Thanks and sorry at the same time...
M3TALLICA said:
So dev thread got locked within just three days.
I see, Note N7000 people are the craziest and notorious trolls here in XDA. :laugh:
Thanks for your support @XpLoDWilD.
Click to expand...
Click to collapse
Cause Note1 got the worst official JB update from all devices out there...therefore everybody is praying for a hero that makes a rom that works as it should....
As long as I keep the N1, cm ROMs are far better then any other tw ROM out there...
Running latest build cm10.2...some small glitches already mentioned but looks promising so far...
Thanks a lot for devs that try to bring this to work...
Sent from my GT-N7000 using xda app-developers app
Building your own CM10.2
After building and using a CM10.1 for a few days now I started to try to build the experimental CM10.2 myself.
I used the How To in the CyanogenMod wiki and changed some settings related to 10.2 (or maybe better: I tried to change).
The history:
In the morning my first build succeeded and could be installed on the device. Testing it without factory reset and only cleaning the caches. It booted in the usual way. Then I got the offer to choose between Nova and Trebuchet launcher (I'm using Nova in 10.1). The selection of the launcher resulted in a restart. So not really successful.
After a factory reset I get the restart when choosing the language in the setup. My build configuration is definitely incomplete/wrong.
Now I switched to the provided built and with this one I could boot into CM10.2 without making a factory reset. Using it right now to connect with a ssh client to my build computer at home and trying a new build.
The idea:
Maybe there are other members here who want to make their own CM10.2 builds as early as possible. Or maybe some did already.
So I want to write down the necessary changes to the normal CM10.1 procedure and I hope that this might help to solve some problems.
With the "migration" of this thread from Original Development to General I assume it is ok to do so (if not I will delete it asap).
Changes in the original Tutorial:
How To Build CyanogenMod Android for Samsung Galaxy Note (International) ("n7000")
I followed the tutorial which is a really good one. I will list the changes I made for CM 10.2.
2.3 Initialize the CyanogenMod source repository
Switched from cm-10.1 to cm-10.2
Code:
$ cd ~/android/system/
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
2.8 Prepare the device-specific code
removed this. So if my new build will work this thread might get useless because there isn't much to change in the 10.1 tutorial
With these changes I can start to build CM 10.2 and get an installable zip.
Right now I'm building it again and will try later if "my" restart will disappear or some things more need to be changed.
And of course I hope some members might help me or add necessary parts.
Thanks in advance.
Thanks for the thread and sorry for the OT xplodwild
Sent from my GT-N7000 using xda premium
Yeah thank you XpLoDWilD and i am sorry too
it's a semi off-topic: i almost have one rule when i change/buy my phone: to be CM supported.
By far the best rom out there, not all the fancy things producer does (although NEMESIS project, it is one as the name states)(although i would like a center clock and a ram bar at the recent apps ), CM doesn't care about the age of the phone, or if one company must force end updating a rom, for the people to buy the next model (S thingy).
Thank you CM (i refer the the people, project and everything related to)!
Long Live CM
now you are spamming this thread too
In my oppinion, asking if the possibility of bricking one's device due to a EMMC bug and the fact that the new Android version uses a command that can trigger said bug IS development related. But heck, whatever. Then let me ask the same question here: could this ROM possibly brick my phone or was that taken care of during developement?
DeKubus said:
In my oppinion, asking if the possibility of bricking one's device due to a EMMC bug and the fact that the new Android version uses a command that can trigger said bug IS development related. But heck, whatever. Then let me ask the same question here: could this ROM possibly brick my phone or was that taken care of during developement?
Click to expand...
Click to collapse
i want to think that the developers already thought about that, and if there was any danger it was posted already...
why do we have the experimental builds, just to screw up our phones, see how many ppl flash 10.2 and screw their phones, statistical emmc chips fried?
I asked this question in the closed thread and because of that I took the liberty to repeat it in a PM.
fstrim (it is a part of the CM10.2 sources) command works on eMMC and the developers will check if this is a real threat or only a wrong assumption.
So we'll have to wait a little - the answers will come.
So this is the fun thread?
Sent from my GT-N7000 using Tapatalk 4 Beta
I hope it won't be (ab)used as such. As xplodwild made it clear by closing the other one without further warning.
I love CYANOGEN MODE.
I can't live with cyanamode...
That's why I bought gt n7000
Thank tlyou cm
Long live our CM
Sent from my GT-N7000 using xda premium
To answer the FSTRIM / EMMC brick bug: You should be safe. Right now CM kernels block all erase, and all Sammy kernels translate secure into nonsecure.
I found an info in other kernel development thread - and of course I do not know it this statement is true, but it seems logical:
fstrim won't work with MMC_CAP_ERASE disabled.
So with the safe CM kernels (here it is disabled) we still can't experience the brickbug.
But we won't get the trim benefits with 4.3 (see the XDA Portal today with a report about it).
The source of fstrim.c (in system/vold) is quite simple to read.
The magic is done in this line (part of an if-statement):
Code:
ioctl(fd, FITRIM, &range)
If the fstrim <-> MMC_CAP_ERASE relation is true, we are safe but will still suffer from the increasing lags.
Let's wait for a more reliable analysis by Entropy512 or other eMMC-Gurus.
The complete function here:
Code:
static void *do_fstrim_filesystems(void *ignored)
{
int i;
int fd;
int ret = 0;
struct fstrim_range range = { 0 };
struct stat sb;
extern struct fstab *fstab;
SLOGI("Starting fstrim work...\n");
/* Log the start time in the event log */
LOG_EVENT_LONG(LOG_FSTRIM_START, get_boot_time_ms());
for (i = 0; i < fstab->num_entries; i++) {
/* Skip raw partitions */
if (!strcmp(fstab->recs[i].fs_type, "emmc") ||
!strcmp(fstab->recs[i].fs_type, "mtd")) {
continue;
}
/* Skip read-only filesystems */
if (fstab->recs[i].flags & MS_RDONLY) {
continue;
}
if (fs_mgr_is_voldmanaged(&fstab->recs[i])) {
continue; /* Should we trim fat32 filesystems? */
}
if (stat(fstab->recs[i].mount_point, &sb) == -1) {
SLOGE("Cannot stat mount point %s\n", fstab->recs[i].mount_point);
ret = -1;
continue;
}
if (!S_ISDIR(sb.st_mode)) {
SLOGE("%s is not a directory\n", fstab->recs[i].mount_point);
ret = -1;
continue;
}
fd = open(fstab->recs[i].mount_point, O_RDONLY);
if (fd < 0) {
SLOGE("Cannot open %s for FITRIM\n", fstab->recs[i].mount_point);
ret = -1;
continue;
}
memset(&range, 0, sizeof(range));
range.len = ULLONG_MAX;
SLOGI("Invoking FITRIM ioctl on %s", fstab->recs[i].mount_point);
if (ioctl(fd, FITRIM, &range)) {
SLOGE("FITRIM ioctl failed on %s", fstab->recs[i].mount_point);
ret = -1;
}
SLOGI("Trimmed %llu bytes on %s\n", range.len, fstab->recs[i].mount_point);
close(fd);
}
/* Log the finish time in the event log */
LOG_EVENT_LONG(LOG_FSTRIM_FINISH, get_boot_time_ms());
SLOGI("Finished fstrim work.\n");
/* Release the wakelock that let us work */
release_wake_lock(FSTRIM_WAKELOCK);
return (void *)ret;
}
---------- Post added at 05:47 PM ---------- Previous post was at 05:44 PM ----------
XpLoDWilD said:
To answer the FSTRIM / EMMC brick bug: You should be safe. Right now CM kernels block all erase, and all Sammy kernels translate secure into nonsecure.
Click to expand...
Click to collapse
I just made my post and then saw this statement.
So no brick bug danger because of the blocked commands but we won't get the trim benefits in 4.3 for the N7000
On this ROM you cannot record in full HD but when you install lg camera it is working ok
Sent from my GT-N7000 using XDA Premium HD app
re TRIM, see also @Entropy512 comment here
all is nice with this rom.. cept for some graphical stuff in Feedly and during screen rotation..
it will run hot initially after that this rom runs as per normal
To get root working properly, need to disable root in developer settings, reboot the phone. After the phone reboots, enable root again. Root should work properly. Well, at least thats how i get my phone;s root working!
thanks!
A question, how do i see the list of notifications?
AOSP ROM for Explay Fresh/Wiko Rainbow and clones.
Code:
#ifndef DISCLAIMER_H
#define DISCLAIMER_H
#endif
/*
* 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.
*
* DO NOT LEECH MY DOWNLOADS, PLEASE RE-DIRECT YOUR FORUM /PAGE
* TO THIS THREAD, IF YOU LIKE MY WORK, YOU CAN SAY THANKS,
* AND MAYBE BUY ME SOME BEERS
*/
Not working:
Autofocus(on some devices)
Front Camera
Known bugs:
Wrong colors in camera on some devices
Black frame around menu list(only if you use "Menu" hardware button)
Working:
Everything else
Flash Instructions:
Backup
Download beta3.rar
Unpack beta3.rar
Put the full_lcsh6582_w_l-ota-xxxxxxxxxxx.zip on external SDCard
Flash base lollipop with SP Flash Tool(use Firmware Upgrade mode)
Flash the new_recovery1.img by SP Flash Tool(use scatter file included in beta3).
Flash zip archive with update in recovery(to enter recovery you need press Volume+ and Power buttons)
Flash GAPPS 5.0(take here http://forum.xda-developers.com/showpost.php?p=59691695&postcount=3) and SuperSU(download here https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip)
Enjoy
XDA:DevDB Information
Lollipop for S5501, ROM for all devices (see above for details)
Contributors
ariafan
Source Code: https://github.com/ariafan
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: Beta #3
Beta Release Date: 2015-06-23
Created 2015-07-11
Last Updated 2015-07-11
reserved
Thread closed at OP's request.
Team OctOs presents Oct-L.
They maintain a current release record and change-log on there website: http://www.teamoctos.com
Your warranty is now void.
Please Read entire Post . . . . . .
Disclaimer . . .
* Remember That flashing Rom can be dangerous to Your Devices .
I take no responsibility for any damages that can happen to your Device.
* 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 inc[/B]luded in this ROM
* before flashing it! YOU are choosing to these modifications, and if
* you point the finger at me for messing u make p your device, I will laugh at you
* DO NOT LEECH MY DOWNLOADS, PLEASE RE-DIRECT YOUR Forum /PAGE
* TO THIS THREAD, IF YOU LIKE MY WORK, YOU CAN SAY THANKS,
* AND MAYBE BUY ME SOME BEERS
*/
Tentacles Features :
Themes
Status bar
Notification bar
Notifications
Omni switch
Buttons
App circle bar
Gesture anywhere
System profiles
Privacy
SuperSu
Power Menu
What Works :
Sync
Storage Info Fixed (Settings -> Storage)
Rils
Wifi
Camera
Sensors
Sound
Bluetooth
IMEI detection
GPS/AGPS
Not Working :
Hotspot(working randomly)
Sound Recorder (Few apps)
Video recording (Recomended to use Camu)
HOW TO INSTALL
-CLEAN INSTALL NEW ROM
-INSTALL Octo-OS
-Do wipe dalvik/Art cache
-REBOOT .
Rom Downloads :
https://docs.google.com/uc?id=0B2cST0lK0rDnTnR1RUpMaUZySnc&export=download
Patch Download:
https://drive.google.com/file/d/0B5DM6ZSz3dh-eW50SEo0RmVnT3M/view?pli=1
Big thanks to :
* @ricky_adhitya
*Team octo-Os
* @pawan Diyal
* @Al3XKOoL
http://forum.xda-developers.com/show...php?p=61136529
Like us on : https://m.facebook.com/profile.php?id=898007540254046&_rdr
XDAevDB Information
Octo-L Rom
Contributors
Abhinav, Anup
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Any
Version Information
Status: Beta
Created 2015-09-15
Last Updated 2015-09-15
Prince Abhinav Gupta said:
Team OctOs presents Oct-L.
They maintain a current release record and change-log on there website: http://www.teamoctos.com
Your warranty is now void.
Please Read entire Post . . . . . .
Disclaimer . . .
* Remember That flashing Rom can be dangerous to Your Devices .
I take no responsibility for any damages that can happen to your Device.
* 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 inc[/B]luded in this ROM
* before flashing it! YOU are choosing to these modifications, and if
* you point the finger at me for messing u make p your device, I will laugh at you
* DO NOT LEECH MY DOWNLOADS, PLEASE RE-DIRECT YOUR Forum /PAGE
* TO THIS THREAD, IF YOU LIKE MY WORK, YOU CAN SAY THANKS,
* AND MAYBE BUY ME SOME BEERS
*/
Tentacles Features :
Themes
Status bar
Notification bar
Notifications
Omni switch
Buttons
App circle bar
Gesture anywhere
System profiles
Privacy
SuperSu
Power Menu
What Works :
Sync
Storage Info Fixed (Settings -> Storage)
Rils
Wifi
Camera
Sensors
Sound
Bluetooth
IMEI detection
GPS/AGPS
Not Working :
Hotspot(working randomly)
Sound Recorder (Few apps)
Video recording (Recomended to use Camu)
HOW TO INSTALL
-CLEAN INSTALL NEW ROM
-INSTALL Octo-OS
-Do wipe dalvik/Art cache
-REBOOT .
Rom Downloads :
https://docs.google.com/uc?id=0B2cST0lK0rDnTnR1RUpMaUZySnc&export=download
Patch Download:
https://drive.google.com/file/d/0B5DM6ZSz3dh-eW50SEo0RmVnT3M/view?pli=1
Big thanks to :
* @ricky_adhitya
*Team octo-Os
* @pawan Diyal
* @Al3XKOoL
http://forum.xda-developers.com/show...php?p=61136529
Like us on : https://m.facebook.com/profile.php?id=898007540254046&_rdr
XDAevDB Information
Octo-L Rom
Contributors
Abhinav, Anup
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Any
Version Information
Status: Beta
Created 2015-09-15
Last Updated 2015-09-15
Click to expand...
Click to collapse
Great work dude...
As a game addict i was bored to find out only 2 touch max is supported on my j5.anyone kindly tell me if its possible to increase this as some games are tough with just 2 touch.
Khanmodx said:
As a game addict i was bored to find out only 2 touch max is supported on my j5.anyone kindly tell me if its possible to increase this as some games are tough with just 2 touch.
Click to expand...
Click to collapse
I have just asked @Nick Verse yesterday about this.
It is possible to increase it, but we don't know yet what modification is needed.
If you or any other people wanna help, then go here: https://github.com/Galaxy-J5/kernel_samsung_j5lte/tree/cm-12.1/drivers/input/touchscreen .
We found some files like:
synaptics_i2c_rmi4.h
synaptics_dsx/synaptics_dsx_core.h
imagis_30xxc/ist30xxc.h
Also, in synaptics_i2c_rmi4.c there is following code:
PHP:
#define F12_FINGERS_TO_SUPPORT 10
.......
struct synaptics_rmi4_f12_extra_data {
unsigned char data1_offset;
unsigned char data15_offset;
unsigned char data15_size;
unsigned char data15_data[(F12_FINGERS_TO_SUPPORT + 7) / 8];
};
.......
/* Maximum number of fingers supported */
if ((query[1] & MASK_3BIT) <= 4)
fhandler->num_of_data_points = (query[1] & MASK_3BIT) + 1;
else if ((query[1] & MASK_3BIT) == 5)
fhandler->num_of_data_points = 10;
.......
/* Maximum number of fingers supported */
fhandler->num_of_data_points = min(ctrl_23.max_reported_objects,
(unsigned char)F12_FINGERS_TO_SUPPORT);
unsigned char data15_data[(F12_FINGERS_TO_SUPPORT + 7) / 8]; ---> [(10+7) / 8 ] = 2.
Saw a thread in xda where 10 multitouch points are possible in cm firmware onlyhttp://forum.xda-developers.com/showthread.php?t=1384927)link. But was not able to implement it coz of limited info about roms. Then a pal told me it hardware that i hve to use a hardware simulation but seems to tiring to do all that just to boost multitouch.