Related
I am new the to the GT10.1.. Just wondering why there are no custom roms or anything for it yet?!?
Sorry if I missed the thread telling me why!
jm6001 said:
I am new the to the GT10.1.. Just wondering why there are no custom roms or anything for it yet?!?
Sorry if I missed the thread telling me why!
Click to expand...
Click to collapse
Questions or Problems are not Development
Please post in the correct forums and use the search
Moving to General
So few people have the tablet at the moment, suspect that's the hold up. It still hasn't been released to the rest of the US.
How much can you do without the source code?
There's not much you can do without the source. The xoom only got it's first rom a few days ago and it does not have all that many changes. Once we get the kernel source, we should start seeing some custom kernels(for overclocking and stuff) but that's about it.
smaskell said:
There's not much you can do without the source. The xoom only got it's first rom a few days ago and it does not have all that many changes. Once we get the kernel source, we should start seeing some custom kernels(for overclocking and stuff) but that's about it.
Click to expand...
Click to collapse
That's what I figured. I'm sure you can change around a few small things, but for the most part didn't expect what I'd consider a true "custom rom."
Will probably have to wait for Ice Cream Sandwich.
I think we can thank google for that as they have chosen not to release the AOSP for honeycomb. And who knows when samsung will release the kernel source. I would have thought they would have released it by now.
xavierdylan said:
I think we can thank google for that as they have chosen not to release the AOSP for honeycomb. And who knows when samsung will release the kernel source. I would have thought they would have released it by now.
Click to expand...
Click to collapse
I'm not exactly sure what the law is but they will have to release it eventually.. The linux kernel is under the GPL, which means that any modifications to it are, without question, also under the GPL. Therefore, they have to make their version of the kernel open source at some point. Does anyone know how long they have to do so?
Does any one know if the retail version of the galaxy tab have an unlocked boot loader and if can be rooted? cant seem to find that info ne where. if it has a locked bootloader you can forget abt custom roms till the bootloader can be unlocked
htc have released source code at htcdev.com, including i have noted, a gingerbread update for desire. would these releases make it easier for hd2 android development?
it will be an interesting next few weeks
1. Wrong forum
2. Already posted on the main news page
3. Gingerbread for desire is released last week already but not the kernel source
4. Source codes were always there on the htcdev site, nothing new
Dont post things too fast m8, i know everyone is excited about the desire gingerbread rom and how it potentially can fix the graphic glitches on the sense roms (is'nt even sure it will be fixed).
Please correct me if i'm wrong i dont think there is much to develop anymore for our HD2's as there are android builds that run as fast as stable as any generic android device.
The only big thing i can imagine that still can be developed is true 720p recording and i dont know if the source code will help getting this to work. i'm not a dev
a dead man said:
would these releases make it easier for hd2 android development?
Click to expand...
Click to collapse
No, it's not a source code of Desire kernel but "only" upgrade Desire to Ginger.
a dead man said:
htc have released source code at htcdev.com, including i have noted, a gingerbread update for desire. would these releases make it easier for hd2 android development?
it will be an interesting next few weeks
Click to expand...
Click to collapse
thisa was posted yesterday and was in the wrong forum and you have done it again today, there is already 2 other threads about this going in Q&A
needs KERNEL source not the release of GB
I know this is a dead thread, but one question that has been on my mind. If a kernel can be compiled can't the kernel be decompiled to study the source code? Just a thought.
[email protected] said:
I know this is a dead thread, but one question that has been on my mind. If a kernel can be compiled can't the kernel be decompiled to study the source code? Just a thought.
Click to expand...
Click to collapse
Decompiled software is very hard to read, follow and understand. The "decompilation" process does not result in the original source code but in assembler code, which is big, ugly and meant for machines not people.
deviant007 said:
Decompiled software is very hard to read, follow and understand. The "decompilation" process does not result in the original source code but in assembler code, which is big, ugly and meant for machines not people.
Click to expand...
Click to collapse
Okay. Thank you for the answer.
One question guys, may be in the wrong thread but excuse me. I just wondering...HTC realesed upgrade for Desire some time ago, Is it that they are not yet published the source code does not break the rules of the General Public License (GPL)?
Hi guys
We heard you! Sony kernel sources now available on GitHub
Read more here
http://developer.sonymobile.com/2014/06/27/we-heard-you-sony-kernel-sources-now-available-on-github/
If you have dev questions contact me
Enjoy!
J
sp sources are up
Hope sony hear us for some other things too.. with us sony can make the Android for us even better /o/
Very good thank you!!!
jerpelea said:
Hi guys
We heard you! Sony kernel sources now available on GitHub
Read more here
http://developer.sonymobile.com/2014/06/27/we-heard-you-sony-kernel-sources-now-available-on-github/
If you have dev questions contact me
Enjoy!
J
Click to expand...
Click to collapse
As I see the 201 kernel available for SP. Why not the 205?
air001 said:
As I see the 201 kernel available for SP. Why not the 205?
Click to expand...
Click to collapse
With the exception of the ram disk, they are identical.
https://github.com/sonyxperiadev/kernel-copyleft/tree/12.1.A.1.xxx
Btw thanks @jerpelea
Perhaps someone can finaly take a proper look to the annoying RAM issue
Opening the camera api to allow 3rd party apps to set ISO etc would be the cherry on the top...
Well, now that the kernel is up - how about a service that allows to create signed kernels so that locked BL can also benefit from custom kernels?
mick232 said:
Well, now that the kernel is up - how about a service that allows to create signed kernels so that locked BL can also benefit from custom kernels?
Click to expand...
Click to collapse
It's impossible to do without Sony private keys/signing tools leak. This is just a kernel source, it doesn't contain them. So even if you build the kernel from source, it will only work on UBL.
Also, to all: moving source to github won't solve anything, and doesn't change anything, it's now just easier to obtain the source for devs. Previously the source was released in the form of open-source tar packages on Sony site...
MrSteve555 said:
It's impossible to do without Sony private keys/signing tools leak. This is just a kernel source, it doesn't contain them. So even if you build the kernel from source, it will only work on UBL.
.
Click to expand...
Click to collapse
That is why I said "service" - Sony doesn't have to hand over the keys. They can provide a service, you upload your custom built kernel, Sony signs it, you download the signed kernel.
mick232 said:
That is why I said "service" - Sony doesn't have to hand over the keys. They can provide a service, you upload your custom built kernel, Sony signs it, you download the signed kernel.
Click to expand...
Click to collapse
Oh, so I misunderstood you. Your idea is really good, but I don't think Sony would ever think about it. So it's just a miracle...
Signing a custom kernel is endorsing it. How can they know if it's broken or something messed up.
Releasing the keys and signing package is better option with declaration or warning for no liability in case of damage
neXus PRIME said:
Signing a custom kernel is endorsing it. How can they know if it's broken or something messed up.
Releasing the keys and signing package is better option with declaration or warning for no liability in case of damage
Click to expand...
Click to collapse
They will never release the keys. However, they, themselves, can sign it if we give it to them. And we can provide them with sources so that they know everything is working fine.
shahrukhqasim said:
They will never release the keys. However, they, themselves, can sign it if we give it to them. And we can provide them with sources so that they know everything is working fine.
Click to expand...
Click to collapse
They dont have enough resources & time to release proper and quick updates. You really think with the NUMBER or devices with locked bootloaders and estimated number of submissions of custom kernels will be possible???
Think about it first. At least dozen models within 18 months time fframe, tens and hundreds of custom ROMs and kernels for each devices.
And its not like one kernel dev will only go once. Be reasonable bro.
Companies only provide services which can be automated. or require a suitable amount of debugging. Bootloader unlocking is IMEI based and database can be automated. So millions of users can use it without issues.
Much better would be they just release the keys in spirit of open source or maybe give some unlock mechanism for permanent locked BLs.
jerpelea said:
Hi guys
We heard you! Sony kernel sources now available on GitHub
Read more here
http://developer.sonymobile.com/2014/06/27/we-heard-you-sony-kernel-sources-now-available-on-github/
If you have dev questions contact me
Enjoy!
J
Click to expand...
Click to collapse
We need solution for locked blootloaders! Development is so hard on locked bootloaders. Give us signing keys or make a site to get kernels signed or anything. LBL are lagging behind UBL a great deal. We need signing facility.
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
neXus PRIME said:
They dont have enough resources & time to release proper and quick updates. You really think with the NUMBER or devices with locked bootloaders and estimated number of submissions of custom kernels will be possible???
Think about it first. At least dozen models within 18 months time fframe, tens and hundreds of custom ROMs and kernels for each devices.
And its not like one kernel dev will only go once. Be reasonable bro.
Companies only provide services which can be automated. or require a suitable amount of debugging. Bootloader unlocking is IMEI based and database can be automated. So millions of users can use it without issues.
Much better would be they just release the keys in spirit of open source or maybe give some unlock mechanism for permanent locked BLs.
Click to expand...
Click to collapse
Then lets just contact Sony what solution do they propose? They should at least respond.
http://developer.sonymobile.com/201...-aosp-for-xperia-on-github-video-open-source/
Enjoy
I wonder if camera and modem will be supported in the future.
well thats good news
I love how people Hage such amazing text interpretation skills. The device tree was added to Github. There are lots of resources there for third party devs to work on and build their own AOSP, or AOSP based ROM.
But this isn't a official release. There never was. This is meant for developers and developers only.
Sent from my SGP311 using Tapatalk
Yeah we already knew because author already posted here http://forum.xda-developers.com/showthread.php?t=2907471
Sent from my D6503 using Tapatalk
Felimenta97 said:
I love how people Hage such amazing text interpretation skills. The device tree was added to Github. There are lots of resources there for third party devs to work on and build their own AOSP, or AOSP based ROM.
But this isn't a official release. There never was. This is meant for developers and developers only.
Sent from my SGP311 using Tapatalk
Click to expand...
Click to collapse
I'd argue it's an official release - a release for developers, but it's still official.
XDA is starting to be "Vanity Fair"...
Check your informations before you decide to post sensationalistic title like this one...
funky0308 said:
XDA is starting to be "Vanity Fair"...
Check your informations before you decide to post sensationalistic title like this one...
Click to expand...
Click to collapse
I see this too much... Aka agreement on ur post
And secondary point,
Not a rom, its neither a aosp rom
Yes official but its purely there for CM11, AOSP and any deviant developers to correct problems with their builds or correcr sonys problems
Its a greed thing sony is doing, it will benefit sony as well as xda devs
So... I wont be able to have AOSP rom with locked bootloader on my Xperia?
Cigaras said:
So... I wont be able to have AOSP rom with locked bootloader on my Xperia?
Click to expand...
Click to collapse
Unlocked bootloaders ONLY. If you still had a locked bootloader and ran AOSP, then your warranty wouldn't be void, thus creating problems for Sony, with non Devs users returning phones and help queries etc...
waynekirby said:
If you still had a locked bootloader and ran AOSP, then your warranty wouldn't be void
Click to expand...
Click to collapse
But if AOSP is provided by Sony themselves, why would they threat it as warranty voiding?
Lets take for example Xiaomi, for Mi3 and Mi4 gsmarena.com said that You could choose either MIUI or AOSP, and You get OTA updates for both (I am not sure if that is official, I do not own a Xiaomi device). Would be great if Sony would do something similar, Google Play Edition would also work for me, as long as I get to keep all the Bravia Engine and X-Reality goodness
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
funky0308 said:
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
Click to expand...
Click to collapse
I highly doubt this. If it's true, you should be able to show that, though...
funky0308 said:
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
Click to expand...
Click to collapse
There is a difference between google play editions and kernel source. If the source is precompiled, its as good as stock. Uncompiled source can be edited to cause serious hardware damage resulting in the void of warranty clause.
Xiaomi is yet to release kernel source for Mi3 and Mi4.
adyscorpius said:
There is a difference between google play editions and kernel source. If the source is precompiled, its as good as stock. Uncompiled source can be edited to cause serious hardware damage resulting in the void of warranty clause.
Xiaomi is yet to release kernel source for Mi3 and Mi4.
Click to expand...
Click to collapse
I don't understand your point here...
I know there are differences, that's why Sony works on this, officially.
We have CM and AOSP ROMs for Z1/Z2 but Sony now hired guy from here to help them in building AOSP that'll work on LB and is released by Sony.
That way, they still can control and approve what will go to device abd what won't...
Maybe I'm wrong but what's the point of releasing AOSP without kernel support from bootloader?
We already have that..
My guess would be - they want us to use AOSP but they don't want us to unlock bootloader and mess with DRM keys.
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Envious_Data said:
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Click to expand...
Click to collapse
Exactly...that's the whole point.
Finally, someone who understand what I'm trying to say and what's the whole purpose of that project
funky0308 said:
Exactly...that's the whole point.
Finally, someone who understand what I'm trying to say and what's the whole purpose of that project
Click to expand...
Click to collapse
Would be nice if instead of your warrenry being voided, its changed
So free repairs for sony fauls so long as its not caused by you rom
Envious_Data said:
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Click to expand...
Click to collapse
AOSP compiled ROM from sony ?
i tought we'd only get the source code and nothing more on AOSP ?
Haldi4803 said:
AOSP compiled ROM from sony ?
i tought we'd only get the source code and nothing more on AOSP ?
Click to expand...
Click to collapse
We only are getting source it seems but to have this for locked bootloaders sony must compile and sign a rom and kernel
Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2...nhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2...FhQTHJIa2xVems
reserved
Artemka2008 said:
Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2ALf4H-2aBrZnhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2ALf4H-2aBrZFhQTHJIa2xVems
Click to expand...
Click to collapse
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).
drakonizer said:
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).
Click to expand...
Click to collapse
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)
Artemka2008 said:
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)
Click to expand...
Click to collapse
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.
drakonizer said:
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.
Click to expand...
Click to collapse
ok, I will delete this thread.
Artemka2008 said:
ok, I will delete this thread.
Click to expand...
Click to collapse
You don't have to delete the thread. It can be used for discussions. You can upload your kernel whenever you feel its appropriate to release your source code.
On a more helpful note: I can't say much without seeing the source code, but if you have ported the kernel drivers as well from shield, you can try using the blobs from Shield itself. You'll probably need to use blobs that match the version of the kernel you are trying to port.
so does that mean that there is a chance for cm12+?
Jahhhhhhh said:
so does that mean that there is a chance for cm12+?
Click to expand...
Click to collapse
Without camera and sound now. I tried to run Android 5.1.1 with our kernel. But I can't find working graphical blobs. I need help with it.
This is my last logcat https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U
This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?
Palm Trees said:
This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?
Click to expand...
Click to collapse
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.
Artemka2008 said:
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.
Click to expand...
Click to collapse
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.
drakonizer said:
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.
Click to expand...
Click to collapse
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.
Palm Trees said:
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.
Click to expand...
Click to collapse
Not the point. The shield developers will not be able to help us. Things will become very easy if this shield kernel port works. We will probably be able to use the newer blobs meant for the Shield, which makes development very easy, if this becomes bootable/stable. I really hope the OP manages to get it working. We either need newer blobs from Xiaomi or we need to write wrappers to use the current kitkat blobs (not easy, since Nvidia documentation is nowhere near as detailed as say, Qualcomm) or we need to get this port working well, which would enable us to use most of the blobs from the Shield (provided Xiaomi hasn't gone out of their way to screw with their blobs). The first two ways are practically impossible, which leads me to rest all my hope on this port. Unfortunately without the source code, we will just have to be silent spectators, waiting for some news.
Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks
rocky869 said:
Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks
Click to expand...
Click to collapse
I asked LuckyMeAgain to publish on the official website, so it's the same thing. I am ArtemkaVZM on 4pda and arttt on en.miui.com MiuiSmokeRom dev team.
Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia
Harrynowl said:
Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia
Click to expand...
Click to collapse
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U
Artemka2008 said:
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U
Click to expand...
Click to collapse
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?
drakonizer said:
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?
Click to expand...
Click to collapse
All the necessary blobs were taken from Shield. More no such files, which could be replaced.