What would've happend if I tried to flash CM10.1 for N7105 to my i9305?
As far as I know, these devices are basically the same!
And I would flash it after I change the build.prop and mount partition, would this work?
sebbe312 said:
What would've happend if I tried to flash CM10.1 for N7105 to my i9305?
As far as I know, these devices are basically the same!
And I would flash it after I change the build.prop and mount partition, would this work?
Click to expand...
Click to collapse
Maybe, I had been speculating this as well actually. Modify the ramdisk to fit an I9305 and you should be good to go, I doubt it could be damaging to your device but I won't take any responsibility on that.
sebbe312 said:
What would've happend if I tried to flash CM10.1 for N7105 to my i9305?
As far as I know, these devices are basically the same!
And I would flash it after I change the build.prop and mount partition, would this work?
Click to expand...
Click to collapse
Please do not try to flash any boot.img from N7100 or N7105!!!!
You simply burn your melfas touch screen chip!
I allready change a device and there is not any solution for that, we allready try everything with AndreiLux and nothing work's, chip is simply burned!
Rekoil said:
Maybe, I had been speculating this as well actually. Modify the ramdisk to fit an I9305 and you should be good to go, I doubt it could be damaging to your device but I won't take any responsibility on that.
Click to expand...
Click to collapse
The reason the touch screen chip is burned is on the melfas firmware the actual kernel have.
So if you change the ramdisk then your melfas chip it will dead too.
Need to compile a new kernel from the source.
ausdim said:
Please do not try to flash any boot.img from N7100 or N7105!!!!
You simply burn your melfas touch screen chip!
I allready change a device and there is not any solution for that, we allready try everything with AndreiLux and nothing work's, chip is simply burned!
The reason the touch screen chip is burned is on the melfas firmware the actual kernel have.
So if you change the ramdisk then your melfas chip it will dead too.
Need to compile a new kernel from the source.
Click to expand...
Click to collapse
Well good thing I didn't try this then
ausdim said:
Please do not try to flash any boot.img from N7100 or N7105!!!!
You simply burn your melfas touch screen chip!
I allready change a device and there is not any solution for that, we allready try everything with AndreiLux and nothing work's, chip is simply burned!
The reason the touch screen chip is burned is on the melfas firmware the actual kernel have.
So if you change the ramdisk then your melfas chip it will dead too.
Need to compile a new kernel from the source.
Click to expand...
Click to collapse
So we're back to square one then..? :-/
never flash anything not made specifically for your phone
WestAussie said:
So we're back to square one then..? :-/
Click to expand...
Click to collapse
You're a pretty pessimistic Aussie aren't you No, we are not back to square one. Fact is this still helps us a lot, we can now compare the differences between the source trees for the I9300 and the N7105 CM10.1 kernels, cherrypicking what we need for our device.
Rekoil said:
You're a pretty pessimistic Aussie aren't you No, we are not back to square one. Fact is this still helps us a lot, we can now compare the differences between the source trees for the I9300 and the N7105 CM10.1 kernels, cherrypicking what we need for our device.
Click to expand...
Click to collapse
You mean the differences between the i9305 and N7105, right? Since we're struggling to port CM 10.1 from the i9300 to the i9305 as it is anyway...
WestAussie said:
You mean the differences between the i9305 and N7105, right? Since we're struggling to port CM 10.1 from the i9300 to the i9305 as it is anyway...
Click to expand...
Click to collapse
No, the I9305 is basically an N7105 with a different panel and touch layer (note: same type of chip, different power supply due to size of panel), I meant that we can compare the differences between configs for the N7105 and the I9300 because that will tell us how to modify the N7105 tree for our device.
Related
Here's a dumb question... I thought a kernel is incorporated with a certain rom. But when i read thru the dev thread, it sounds like there are different version of kernels and we can install different Kernels to different roms??? What exactly do the Kernels do? What would make the differences? Thanks in advance.
Kernels control the resources and filing system of the phone. Different kernels have different lag fixes, some over clock the processor. Some kernels re-orientate roms so i9000 roms work on the captivate.
He also makes some kick ass chicken. Sorry, couldn't help myself.
http://en.wikipedia.org/wiki/Kernel_(computing)
mcord11758 said:
Kernels control the resources and filing system of the phone. Different kernels have different lag fixes, some over clock the processor. Some kernels re-orientate roms so i9000 roms work on the captivate.
Click to expand...
Click to collapse
So, would you say the kernel makes a rom work on a specific phone ???
minlee85 said:
So, would you say the kernel makes a rom work on a specific phone ???
Click to expand...
Click to collapse
In some cases but they accomplish more then that
minlee85 said:
So, would you say the kernel makes a rom work on a specific phone ???
Click to expand...
Click to collapse
Android relies on Linux version 2.6 for core system services such as security, memory management, process management, network stack, and driver model. The kernel also acts as an abstraction layer between the hardware and the rest of the software stack.
Ok guys i am building a new kernel for you Note users based on the official source that samsung Dropped..i have the source and tools the problem is can someone point me on how to include the recovery as i do not own the device and would like to share some love on this device..else i will just build it without the recovery..
your replies will be much appreciated as this will be step forward for you to have a new kernel..this will be a blind build since i do not own the device i DID own it but never fiddled with it since the device was prone to bricking..
I hope you are aware of the brick bug.
http://forum.xda-developers.com/showthread.php?t=1633943
http://forum.xda-developers.com/showthread.php?t=1857556
Boy124 said:
I hope you are aware of the brick bug.
http://forum.xda-developers.com/showthread.php?t=1633943
http://forum.xda-developers.com/showthread.php?t=1857556
Click to expand...
Click to collapse
He just said that lol
Sent from my Galaxy Nexus using xda premium
Boy124 said:
I hope you are aware of the brick bug.
http://forum.xda-developers.com/showthread.php?t=1633943
http://forum.xda-developers.com/showthread.php?t=1857556
Click to expand...
Click to collapse
yes i am aware of that and it seems the newer ones are now safe from brick bug..but still its never late just to be cautious..
just finished building 1 kernel image..hope i did it right..
note: Always do a backup before borking your device..
test zimage
also i need a clean ramdisk for STOCK TW roms..as i am just using the Revived Hydracore kernel ramdisk..it might not boot as i what i am seeing it..but nonetheless just try if it boots up..
kairi_zeroblade said:
yes i am aware of that and it seems the newer ones are now safe from brick bug..but still its never late just to be cautious..
Click to expand...
Click to collapse
Sorry, but that's kind of a joke: you want to build a kernel for the Note, but you do not have one. And you do not know how to include recovery. And you want to be cautious.
You really expect that a member with a Note would risk his device testing this?
Maybe you should start to build a kernel for a device you own yourself.
ThaiDai said:
Sorry, but that's kind of a joke: you want to build a kernel for the Note, but you do not have one. And you do not know how to include recovery. And you want to be cautious.
You really expect that a member with a Note would risk his device testing this?
Maybe you should start to build a kernel for a device you own yourself.
Click to expand...
Click to collapse
i used the remaining Hydracore remnants for ramdisk and in my inspection i did found a recovery included..nevertheless it seems to be safe as i am reading his deve post before i dived in..
i own an S3 and i built my own kernel for it..based on the Update 7 sources the same goes for my S3 mini(i do not own the device but since sources are available then why not build 1)..also i am not obliging everyone to help..if it boots up then good for you as i can upload the source and for your devs to start spinning things..much more or less its a good start..
you can always ODIN in the stock boot image..if things come worse..also do not blame me since this was the problem with samsung to begin with..
edit1: ok so for those who are interested to help me you can PM me as i want to try the lower exynos platform..this is just weird as the kernel format is in zimage instead of a normal boot.img file..this is just for those who are brave and knows the way around stuff with N7000..
kairi_zeroblade said:
you can always ODIN in the stock boot image..if things come worse..also do not blame me since this was the problem with samsung to begin with..
Click to expand...
Click to collapse
If things come worse you'll make a new "Angelom Kernel". No risk for you - because you can't brick your device.
But in the end each tester has to decide if he wants to test your "blind build".
ThaiDai said:
If things come worse you'll make a new "Angelom Kernel". No risk for you - because you can't brick your device.
But in the end each tester has to decide if he wants to test your "blind build".
Click to expand...
Click to collapse
that is why its just for those who are brave enough..else you stay on stock forever..that is why samsung release these codes..for those who are interested..else just look at those codes..
Hi all,
I've heard of the SiyahKernel for the I9300 which has dual boot functionality.
Does anybody know if this works on the I9305? Or is there a dual boot kernel available which is made for the I9305 in special?
Reason why I want to have dual boot:
I'm a huge Ubuntu fan. And what I've understood from what I've read is that it's CM(10?) based. So I'd like to use that as second rom. (I know, there isn't a version for the I9305 available right now, but I'll give it a try to port it from I9300 to the I9305.)
Thanks in advance.
As far as I was aware there is no dual boot yet for our device
Sent from my GT-I9305 using xda app-developers app
If their is then its in Development .
jje
Does it take much time to make a kernel which supports dual boot ?
Does anybody know how to port a kernel from I9300 to the I9305 ? Is it hard work to do that ?
And why does the 1GB extra and LTE support make such a difference for ROMS on the device ?
Thanks in advance.
Its not so much the difference as developers actually wanting to work on the phone . Nobody pays them its their choice what to develop . jje
tloader11 said:
Does it take much time to make a kernel which supports dual boot ?
Does anybody know how to port a kernel from I9300 to the I9305 ? Is it hard work to do that ?
And why does the 1GB extra and LTE support make such a difference for ROMS on the device ?
Thanks in advance.
Click to expand...
Click to collapse
1. Thats not REALLY hard, however you have to know what to do. Looking and comparing sources is good point to start. Take a look at gokhan or googy commits about dual boot for example.. Personally, I havent been interested in it, but I might look into it, why not
2. Apart from these, we have other radio, and that causes so much trouble with ROM differences..
Hbohd said:
1. Thats not REALLY hard, however you have to know what to do. Looking and comparing sources is good point to start. Take a look at gokhan or googy commits about dual boot for example.. Personally, I havent been interested in it, but I might look into it, why not
Click to expand...
Click to collapse
Cool ! That would be awesome
Hbohd said:
2. Apart from these, we have other radio, and that causes so much trouble with ROM differences..
Click to expand...
Click to collapse
It's cool that we have radio, but.... why do we need it ? seriously... we all have a mobile network subscription these days
Couldn't we just drop that in the beta/alpha versions, and add it in later then ? ;s
tloader11 said:
Cool ! That would be awesome
It's cool that we have radio, but.... why do we need it ? seriously... we all have a mobile network subscription these days
Couldn't we just drop that in the beta/alpha versions, and add it in later then ? ;s
Click to expand...
Click to collapse
I mean, another radio, like baseband, ril etc. I wasn't talking about normal FM radio (we haven't even got one in i9305).
However, taking only these proper files (like ril + modem) from our ROMs and take them to i9300 ROMs might work, I tried some time ago doing same thing with temasek's cm10.1 and it worked.. Unfortunately I wasn't able to compile fully stable and well working kernel (based on temasek's sources) therefore I do not use it now ;p
Hbohd said:
I mean, another radio, like baseband, ril etc. I wasn't talking about normal FM radio (we haven't even got one in i9305).
However, taking only these proper files (like ril + modem) from our ROMs and take them to i9300 ROMs might work, I tried some time ago doing same thing with temasek's cm10.1 and it worked.. Unfortunately I wasn't able to compile fully stable and well working kernel (based on temasek's sources) therefore I do not use it now ;p
Click to expand...
Click to collapse
Ahh, stupid mistake >< sorry for that!
Would still be nice of you could look at the dual boot feature for our device !
[Q] Are there N7000 kernels with Video4Linux(V4L2) & USB Video Class(UVC) enabled?
I am trying to hook up an external camera (borescope) via USB OTG and these drivers need to be enabled. They apparently are not enabled in stock kernel. I am currently running XXLSZ stock ROM with PhilZ stock kernel.
Is anyone aware of a kernel with these drivers enabled?
Evidently requires the following in the defconfig or .config file:
CONFIG_VIDEO_DEV=y
CONFIG_VIDEO_V4L2_COMMON=y
CONFIG_VIDEO_MEDIA=y
CONFIG_USB_VIDEO_CLASS=y
CONFIG_V4L_USB_DRIVERS=y
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
I'm sure this is a simple change but beyond my skill level...
Thanks for any help.
v35lee said:
I am trying to hook up an external camera (borescope) via USB OTG and these drivers need to be enabled. They apparently are not enabled in stock kernel. I am currently running XXLSZ stock ROM with PhilZ stock kernel.
Is anyone aware of a kernel with these drivers enabled?
Evidently requires the following in the defconfig or .config file:
CONFIG_VIDEO_DEV=y
CONFIG_VIDEO_V4L2_COMMON=y
CONFIG_VIDEO_MEDIA=y
CONFIG_USB_VIDEO_CLASS=y
CONFIG_V4L_USB_DRIVERS=y
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
I'm sure this is a simple change but beyond my skill level...
Thanks for any help.
Click to expand...
Click to collapse
My kernel (link in Ori Dev section) has all but CONFIG_USB_VIDEO_CLASS is not set.
You can try to see if it works. Otherwise I can change this setting in the next version.
BTW, what is the benefit of external camera? N7000 already has two internal camera.
forest1971 said:
My kernel (link in Ori Dev section) has all but CONFIG_USB_VIDEO_CLASS is not set.
You can try to see if it works. Otherwise I can change this setting in the next version.
BTW, what is the benefit of external camera? N7000 already has two internal camera.
Click to expand...
Click to collapse
I actually just flashed your Kernel yesterday! Thanks for your continued work on the Note.
It does look like the CONFIG_USB_VIDEO_CLASS needs to be set, as the app I'm trying to use gives the error 'Device has no UVC driver'. I would be extremely grateful if you would enable that in your next version. I have been trying to learn how to build my own kernel but quickly getting overwhelmed...
Another change I have seen referenced is 'the permission of /dev/video0 is set 0666 in /ueventd.xxxx.rc'. Not sure what that refers to but sure you will. Here are a couple of places where this capability is outlined a little more with links to source:
https://bitbucket.org/neuralassembly/simplewebcam
http://brain.cc.kogakuin.ac.jp/research/usb-e.html
Regarding the benefit of an external camera - it is simply being able to hook up a camera that can go where the Note can't, or where you want a camera located away from the Note but still see the image on the Note. In my case, I have a cheap USB borescope/endoscope which I use to look at and take pictures/video of exhaust valves, cam, etc inside my engine. The other benefit for me is the portability of the Note - I can hook the borescope up to my laptop, but it would be more convenient to work with the much smaller Note. Others are using the external camera capability to hook up a USB webcam in their car to use as a dashcam or rear view camera recorded/displayed on their phone.
I do have this working on an old tablet (Huawei MediaPad), but really would like to get it working on the Note. Thanks for your interest!
i will make it for you to test soon
forest1971 said:
i will make it for you to test soon
Click to expand...
Click to collapse
Wow, that would be fantastic. Thanks!
Need a kernel
v35lee said:
Wow, that would be fantastic. Thanks!
Click to expand...
Click to collapse
Can you please give that kernel with support of UVC? and to what firmware it speciolazied? i use CM11 4.4.2 on N7000, couldn't find solutions to connect an external cam, so please reply me, whatever the answer is. THANKS!
leo_neo said:
Can you please give that kernel with support of UVC? and to what firmware it speciolazied? i use CM11 4.4.2 on N7000, couldn't find solutions to connect an external cam, so please reply me, whatever the answer is. THANKS!
Click to expand...
Click to collapse
It was for SAMSUNG TW JB 4.1.2 ROM, the kernel was special version forest1971's kernel noted in his signature. WOn't work with your CM11 4.4.2.
You might check with forest to see if he still has this version - I don't think it would be correct for me to forward his work without his permission.
v35lee said:
It was for SAMSUNG TW JB 4.1.2 ROM, the kernel was special version forest1971's kernel noted in his signature. WOn't work with your CM11 4.4.2.
You might check with forest to see if he still has this version - I don't think it would be correct for me to forward his work without his permission.
Click to expand...
Click to collapse
Please feel free to share that version in this thread for those who need it.
Sent from my GT-N7000 using Tapatalk 2
UPDATE: 15/12/2015
new kernel build has been released today, few new features added and tweaks made.
changelog
Code:
Added UKSM(Ultra-Kernel Samepage merging) for performance and memory management
added interactive cpu governor
Enabled Fading LED Notification Light
Removed pretty much all debugging junk from kernel as its not needed
switched to linaro 4.9.4 compile with cortex a7 optimization
new link is now an update.zip so can be flashed with twrp and has been confirmed as working, ive also disabled secure storage so wifi password should save fine
link:
https://www.dropbox.com/s/r97qyhvafs85l14/update.zip?dl=0
or if your feeling brave heres the boot img and replacement wlan.ko that needs to go in /system/lib/modules
https://www.dropbox.com/s/r6jgadnx3suedh7/boot-g800h-23.img?dl=0
https://www.dropbox.com/s/fpwpx06vz0e4dml/wlan.ko?dl=0
NOTE: for those of you who want to get some of your ram back that samsung has so kindly blocked in 5.1.1 please check out this link
http://forum.xda-developers.com/gal...b-ram-fix-updating-to-lollipop-g800h-t3247521
i am working on a fix to get rid of this restriction in the kernel but for now this is the only way to
any suggestions or ideas would be appreciated.
any donations however small would be much appreciated to help cover some of my costs and time
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=RPFP77CH25NVC
----------------original post------------------
hello all,
as most of you have probably already seen i have recently released a custom kernel for the exynos variant of s5mini, but now thanks to some major help from sasukesama in testing over a dozen builds half of which didnt even boot at first i have a working kernel for the G800H with a few tweaks and features added. i will be keeping this kernel and my exynos one maintained regulary so keep checking for updates.
current features on this kernel are:
Code:
1.6Ghz CPU Overclock
550mhz GPU Overclock
100mhz Base GPU Clock (battery saving FTW)
zzmoove CPU governor
Few different I/O governors including FIOPS and BFQ
SU supported and have disabled samsungs stupid rooting protection
few other little tweaks
flashing currently is either via odin or direct flash from device
links for kernel images
Odin tar.md5
Code:
https://www.dropbox.com/s/l51bzvgpf185vxh/boot.tar.md5?dl=0
standard boot.img to flash from device or twrp ive been informed can flash it also
Code:
https://www.dropbox.com/s/06donpl14ef1mws/boot-g800h-14.img?dl=0
kernel source is available
https://github.com/DJSteve/g800h_custom_kernel
please let me know any issues, requests or questions
and again cheers to sasukesama for risking his device testing early versions
If you still need some testers, you can count on me! Just PM me!
Jackeagle TWRP is also capable of flashing img files
I've Flashed with it some kernels and its safe to use
Tardis? WHAT? woooop wooooooop
Ahmetay said:
Tardis? WHAT? woooop wooooooop
Click to expand...
Click to collapse
theirs a reason behind the reference due to fact i started off with this kernel by sending it to the future due to where i am in world compared to where sasukesama is
How about OTG support? Also, finally a custom kernel for G800H. Good Work! :victory:
DJ_Steve said:
theirs a reason behind the reference due to fact i started off with this kernel by sending it to the future due to where i am in world compared to where sasukesama is
Click to expand...
Click to collapse
hmm... time lord tech!
Vithalvess said:
How about OTG support? Also, finally a custom kernel for G800H. Good Work! :victory:
Click to expand...
Click to collapse
i forgot to ask that, it has OTG support in stock rom but its just not enabled in the kernel (i think)
Can I test on g800 d/s?
Dont think i enaabled otg yet its next on list to do... your welcome to try on a d/s model but i cant promise it wont cause issues
Sent from my SM-G800F using Tapatalk
bill_kevin said:
Can I test on g800 d/s?
Click to expand...
Click to collapse
Mine is the ds and it works
Ps: the ds version is the same H version they're one
the name is G800H DS but for some reason the web sits separates them
maybe because they're stupid :v
G800
H and H/DS are same.
i can use DS rom (5.1.1) in HQ(Turkey) one sim qualcomm variant..
------
antutu score is 23k btw
Havent got a clue i think it should work but dont hold.me to it.. samsung and their stupid multiple devices all over
Sent from my SM-G800F using Tapatalk
Ahmetay said:
G800
H and H/DS are same.
i can use DS rom (5.1.1) in HQ(Turkey) one sim qualcomm variant..
------
antutu score is 23k btw
Click to expand...
Click to collapse
Can you try the kernel on it? See if it works as well
sasukesama said:
Can you try the kernel on it? See if it works as well
Click to expand...
Click to collapse
already using it antutu score was 18-19k and its 23k now
Ahmetay said:
already using it antutu score was 18-19k and its 23k now
Click to expand...
Click to collapse
Cool then we'll add it in the thread name
btw my antutu scores 21450 :'|
it was 18760 so its better now
One last thing can you try GTA SA?
it was laggy as hell back on the stock kernel and not playable even on the lowest graphics settings but now its playable
i just want to see if im the only one who lags for :'(
DJ_Steve said:
Dont think i enaabled otg yet its next on list to do... your welcome to try on a d/s model but i cant promise it wont cause issues
Sent from my SM-G800F using Tapatalk
Click to expand...
Click to collapse
I've read elsewhere that, opposite to Galaxy S5, our Galaxy S5 mini doesn't push juice out of the usb pins, and that's why they don't need a sealing flap protecting the connector against water contact. No power out, no hardware enabled OTG.
Just my two cents, please correct me if that's not true.
Cheers
someone can confirm this, not save wifi password before restart phone
and i have this warning (screenshot)
i have SuperSU-v2.62-20151210170034
bill_kevin said:
someone can confirm this, not save wifi password before restart phone
and i have this warning (screenshot)
i have SuperSU-v2.62-20151210170034
Click to expand...
Click to collapse
That will be knox triggering. Supersu should be able to disable that warning if you open app
Sent from my SM-G800F using Tapatalk
RGold55 said:
I've read elsewhere that, opposite to Galaxy S5, our Galaxy S5 mini doesn't push juice out of the usb pins, and that's why they don't need a sealing flap protecting the connector against water contact. No power out, no hardware enabled OTG.
Just my two cents, please correct me if that's not true.
Cheers
Click to expand...
Click to collapse
My friend have the G800F with the otg enabled kernel and its still waterproof
only when the otg connected it sends voltage
also the S5 neo doesn't have usb cover and its waterproof with otg enabled from factory so dont worry
i think the whole you must cover ports for a waterproof design is moreof a myth, aslong as you allow the device to dry out somewhat after getting wet i doubt very much it will have any effect on the usage - my OLDD moto Atrix got completely drowned and all i had to replace on it was the capacitive buttons at bottom of screen, rest of device worked perfectly after being dried out (in rice as it was not waterproof)