Database Users

CyanogenMod 7.0 for eLocity ?

Check this out !
Anyone in relation with those guys ? How could we get out tablet to support it ?
Pretty amazing !
Link here : http://www.engadget.com/2011/04/11/cyanogenmod-7-0-is-now-final-ready-for-your-consumption/
I know Dexter is the eLocity king atm, but it must be tirering to be a one man army !

Again and again and again...
Without kernel source we unable to do custom ROMs. Only modifications over stock.
Not a development topic...

5[Strogino] said:
Again and again and again...
Without kernel source we unable to do custom ROMs. Only modifications over stock.
Not a development topic...
Click to expand...
Click to collapse
maybe I should put my old signature back on? lol

the Synergy Bluetooth implementation is nowhere close to standard implementation, so although we might get a CM6/7 on this tablet, even without 2.6.36.3 kernel maybe, we still need more coding done to support the BT implemention otherwise the port will be without Bluetooth support..
I got, as example, the FolioMod ported easily, but Bluetooth did not work, same with the Blur port.. and since our kernel has no real loopdevice or devicemapper support and modules needs to be specifically compiled with the revisions used in our kernel, the "move2sd" function is also missing here, and other nice function as optimized filesystems using loopdevice for faster database updates etc..
it will be hard! , and the drivers without any source, makes its practically impossible to do a kernel based on nvidia's git tree alone..

Moved to proper forum

Kernel available??
Mr. Clown said:
Moved to proper forum
Click to expand...
Click to collapse
See on http://www.elocitynow.com/downloads/open-source.tar
and chacksum http://www.elocitynow.com/downloads/.checksum.md5

ming_a said:
See on http://www.elocitynow.com/downloads/open-source.tar
and chacksum http://www.elocitynow.com/downloads/.checksum.md5
Click to expand...
Click to collapse
Yep. Did you find it here:
http://www.elocitynow.com/developers.shtml
Billy

Benefits of cracked Bootloader?

Hi, I was just curious to know what the benefits of a cracked boot loader is and what features we could implement or achieve that we already have.

With this we should put custom kernels on our devices, and this way we should eliminate major bugs with GingerBread and Froyo, since some of stuff are made with patches over stock libs (I´m not certain about that, but it was what I understood while reading some threads). By the way, tethering over cyanogenmod menu, is only possible if we get custom kernel, if I´m not wrong doixahn said that. To end it up, with bootloader cracked, we may hope for more stability over our devices

biscoitu said:
With this we should put custom kernels on our devices, and this way we should eliminate major bugs with GingerBread and Froyo, since some of stuff are made with patches over stock libs (I´m not certain about that, but it was what I understood while reading some threads). By the way, tethering over cyanogenmod menu, is only possible if we get custom kernel, if I´m not wrong doixahn said that. To end it up, with bootloader cracked, we may hope for more stability over our devices
Click to expand...
Click to collapse
thanks, but what do you mean by a custom kernel?

_Sparks said:
thanks, but what do you mean by a custom kernel?
Click to expand...
Click to collapse
a kernel is the linux core containing drivers for all the hardware. Basically if we crack it we can add drivers for camera for example and make it work say face detection or autofocus or whatever from any other device drivers (like X10) plus adding the lib's straight into kernel not patching in and out

ahmedz_1991 said:
a kernel is the linux core containing drivers for all the hardware. Basically if we crack it we can add drivers for camera for example and make it work say face detection or autofocus or whatever from any other device drivers (like X10) plus adding the lib's straight into kernel not patching in and out
Click to expand...
Click to collapse
Yeah,...and devs cam make kernel even it smaller if they want a very thin r0m

ahmedz_1991 said:
autofocus
Click to expand...
Click to collapse
lulz nope
10characters

Probably X8's camera is to weak to handle autofocus.

4.3 kernel sources released! grab them here

http://www.sammobile.com/2013/11/05/samsung-releases-android-4-3-kernel-source-for-galaxy-s3/

Wow man latest news isn t it?? Using Internet Explorer??

And? Could you explain a bit in how it help us?
Thanks.
Enviado desde mi GT-I9300 usando Tapatalk

It means we can finally have custom kernels woooooo
Sent from my GT-I9300 using XDA Premium 4 mobile app

Well, I downloaded the source kernel and I need a clear way how to compile it smoothly. I wonder whether I can flash the kernel via Odin or CWM to a rooted stock I9300XXUGMJ9 firmware or not. Will it work? Any walkthroughs?

ahmedmelm said:
Well, I downloaded the source kernel and I need a clear way how to compile it smoothly. I wonder whether I can flash the kernel via Odin or CWM to a rooted stock I9300XXUGMJ9 firmware or not. Will it work? Any walkthroughs?
Click to expand...
Click to collapse
http://source.android.com/source/building.html
Read everything on left hand side
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

rootSU said:
http://source.android.com/source/building.html
Read everything on left hand side
Click to expand...
Click to collapse
That's way cool. But any matter to accelerate the process? Would really compiling this kernel and pushing it to existing ROM work?

What do you think source code is exactly? What is it you think you want?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

I know this is not a Q&A thread but could I ask? Does this release of source kernel code mean, that Samsung finally released the source code for the dreaded mali GPU driver and the FM radio blobs that we so need to make CM roms fully functional and smooth?

granets said:
I know this is not a Q&A thread but could I ask? Does this release of source kernel code mean, that Samsung finally released the source code for the dreaded mali GPU driver and the FM radio blobs that we so need to make CM roms fully functional and smooth?
Click to expand...
Click to collapse
No. Read following for explanation.
dhiru1602 said:
Blobs are userspace components which correspond to the HAL (Hardware Abstraction Layer). It is this layer which is responsible for communication between the kernel and the operating system. GPU kernel driver is opensource, but the GPU HAL is closed source. This is the case with all the devices, but on our device, much more components of the HAL are closed source like FIMC, FIMG, HWJPEG, TVOUT. Samsung doesn't release the source code for this components because it doesn't necessarily have to. Without the source code, we are forced to use the compiled binary which may or may not work properly. Since we are left without options, we often mess around with the Android framework, making dirty hacks to get them to work. We will not be able to futureproof our device with newer versions of Android unless we have the source code since making edits on compiled binaries is not possible and hence we have to wait for official releases so that we could get newer binaries (blobs). Here is the list of all the blobs that we use on our device. Having proprietary code is not uncommon, but Samsung doesn't release the source code for essential parts of the OS like Graphics subsystem, OMX and DSP, which makes things more complex provided there is no documentation for the SOC, nor they are wiling to help developers.
Click to expand...
Click to collapse

dhirend_6d said:
No. Read following for explanation.
Click to expand...
Click to collapse
Thanks for the explanation. So basicaly those kernel sources don't mean much. And I was so excited

granets said:
Thanks for the explanation. So basicaly those kernel sources don't mean much. And I was so excited
Click to expand...
Click to collapse
They mean as much as every other kernel source release. We still dont have everything we need to make AOSP work properly, but we can now get custom kernels for 4.3 touchwiz roms.

rootSU said:
They mean as much as every other kernel source release. We still dont have everything we need to make AOSP work properly, but we can now get custom kernels for 4.3 touchwiz roms.
Click to expand...
Click to collapse
These include the latest mali r3p2. So we have now userspace binaries + kernel source drivers. It makes this possible, which is awesome. It's coming for all exynos4 devices.

[HELP] Porting G2's L to G1 [KERNEL]

Yo peeps,
Code:
[COLOR="Red"]For people who say I will wait for official update STAY OUT![/COLOR]
So i was trying to port the G2's Lollipop update to G1. Many of you may think itz quite useless, well i just decided to try because i am a big dev here to compile AOSP or CM12 roms without a proper device tree. So while we wait for Official Update or until CM/AOSP becomes stable i thought maybe i could try porting. So i managed to get the system and boot.img made a zip and now the problem seems with the kernel. I get a fall through to fastboot mode when i use their kernel and when i use ours it gets stuck on bootlogo. Both the kernels are of 3.4.42 and i am not good at kernels like the way i am at kang so if someone could help me with the kernel part maybe we can get L earlier.
This thread is for only people who can encourage and try helping! Others please excuse.
I unpacked both the boot.img made a zip of it and uploaded so that it would be easier for people to help. I dont mind testing it numerous times. Willing to listen and try anything and everything that can make it boot. So here are the kernels.
Hope to find help!
 @VictoriousShooter
 @rr46000
 @S0bes
 @yajnab​

I think it is impossible without kernel source... This way you can play with Ramdisk only. Moto g2 has little bit different hw..

only difference is screen size and camera, the processor, graphics chip, ram, battery and sensors are the same. so it is possible to port g2 update to g1.

AgentChaos said:
only difference is screen size and camera, the processor, graphics chip, ram, battery and sensors are the same. so it is possible to port g2 update to g1.
Click to expand...
Click to collapse
The ROM itself-yes
Kernel-no.

I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...

S0bes said:
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
Click to expand...
Click to collapse
I have flashed ZTE warp cm10 on ZTE v9a with kernel built by myself and it was also working... But with warp kernel there was no chance to boot v9 device up.
I think with flashing g2 lollipop over g1 shouldn't brake your phone permanently, unless you are not flashing modern etc. (just flashing system and kernel). But I cannot promise nothing will be broken

Try using a CWM flashable version of the G2 rom along with the CM12 kernel? You might be able to get some kind of result from it?

Justice™ said:
Try using a CWM flashable version of the G2 rom along with the CM12 kernel? You might be able to get some kind of result from it?
Click to expand...
Click to collapse
cm kernels wouldnt work on stock roms bro.. tried it.
fabus said:
I have flashed ZTE warp cm10 on ZTE v9a with kernel built by myself and it was also working... But with warp kernel there was no chance to boot v9 device up.
I think with flashing g2 lollipop over g1 shouldn't brake your phone permanently, unless you are not flashing modern etc. (just flashing system and kernel). But I cannot promise nothing will be broken
Click to expand...
Click to collapse
S0bes said:
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
Click to expand...
Click to collapse
@S0bes i thought you may know something so kinda tagged u bro btw i tried flashing g2's stock firmware image it doesnt brick or anything but since they have a different kernel it still goes to fall through to fastboot mode even on g2's stock roms. the main difference is that 5.0 uses ART and ours DALVIK and hence i believe that what the issue.

yeshwanthvshenoy said:
i tried flashing g2's stock firmware image it doesnt brick or anything but since they have a different kernel it still goes to fall through to fastboot mode even on g2's stock roms. the main difference is that 5.0 uses ART and ours DALVIK and hence i believe that what the issue.
Click to expand...
Click to collapse
I do not believe so. Neither Android 4.4.4 Moto G LTE nor, Moto G (2014) Kernels (or ROMs) boot on Moto G (2013.)

@yeshwanthvshenoy I know you stated you are a big dev, but since you are, you already know kernels can't be ported from an image. You need the source code. Unless you have a magical way of changing code without needing to decompile.
Still... if you are having fin making zips, go ahead, don't let my words discourage you. But... this is a dead end.

Agreed with @fermasia
if porting kernel without source was such an easy task by this time we had so many kernels
Only way is directly flash 2nd gen kernels to try our luck if some things work
All the best [emoji4]

reversegear said:
Agreed with @fermasia
if porting kernel without source was such an easy task by this time we had so many kernels
Only way is directly flash 2nd gen kernels to try our luck if some things work
All the best [emoji4]
Click to expand...
Click to collapse
I dont think there will be any luck since G 2014 has a different MSM board and that has to do with the result you will get. So if you manually flash XT1064 firmware on an XT1032 just expect a beautiful soft brick in the best of the cases... Just wait for official OTA, there are just days left for it!!! Next week we will se some news.

for this you need a new kernel for G1, which we dont have. (and even if we had it then we had the ROM too)
you will have to use the old kernel with the new ROM. which will obviously create tons of error.
have you tried CM12 kernel with the ROM?

For the kernel, try following and check if there is some progress.
Decompile both the kernels with dsixdia kitchen. You will get ramdisk and Zimage for each kernel. Try following combination.
4.4.4 Zimage (G1) + 5.0 Ramdisk (G2) + Modules (G1)
If no, try using init.rc of G1 and give another try.

I'm not planning on helping you do this, but the g2 and g1 use the same kernel. You only have to enable certain things in the defconfigs...

Somcom3X said:
I'm not planning on helping you do this, but the g2 and g1 use the same kernel. You only have to enable certain things in the defconfigs...
Click to expand...
Click to collapse
They are using the kernel source, but even kernel source for g2 hasn't been released so far...

fabus said:
They are using the kernel source, but even kernel source for g2 hasn't been released so far...
Click to expand...
Click to collapse
You don't really need it, decompile the boot.img and replace the zimage inside with a compiled one.
I don't recommend doing this. Porting in this case is pointless.
By the way, kernel source was released a while ago.

Good luck on the kernel. Though I highly suspect that Motorola will give us Lollipop on the Moto G before anyone is able to come up with a working port.

Somcom3X said:
You don't really need it, decompile the boot.img and replace the zimage inside with a compiled one.
I don't recommend doing this. Porting in this case is pointless.
By the way, kernel source was released a while ago.
Click to expand...
Click to collapse
thanks for the info and help all of u are extending i know maybe this may not work out but itz just a try. and @Somcom3X can u please a little more of the above statements u said about changing defconfigs and few other stuff. Should i use G2's zimage and G1's ramdisk or any file that u think would make it boot? Can u specify the file name if so.

Get the basic source of the G1. Match the changes made to G2 for the L. Best to getthe old G1 kernel source and modify the things needed for the L. Test and Go.
Unless its creating changes in filesystem its good to play with.
---------- Post added at 03:13 PM ---------- Previous post was at 03:13 PM ----------
yeshwanthvshenoy said:
thanks for the info and help all of u are extending i know maybe this may not work out but itz just a try. and @Somcom3X can u please a little more of the above statements u said about changing defconfigs and few other stuff. Should i use G2's zimage and G1's ramdisk or any file that u think would make it boot? Can u specify the file name if so.
Click to expand...
Click to collapse
G2 device board name differs. It will be just foolish and waste of time

[Question] Is it possible to install this rom from another device with the same specs

I was searching a bit about snapdragon 430 and the devices that use it.
And i came across a device with the same specs as redmi 3s(land)
So, i was wondering,
Could we use it?
Its stable and built on AOSP
Device link=http://m.gsmarena.com/bq_aquaris_u_plus-8378.php
Rom links=https://www.bq.com/en/support/aquaris-u-plus/support-sheet

No. You'll have to ask the developers to 'PORT' the ROM to run on the intended device.

zans1023 said:
No. You'll have to ask the developers to 'PORT' the ROM to run on the intended device.
Click to expand...
Click to collapse
Well, i suppose it wont be hard to to that since the hardware is exactly the same

Jure_aleksic said:
Well, i suppose it wont be hard to to that since the hardware is exactly the same
Click to expand...
Click to collapse
Hardware is same
The kernel is not.
Some stuff like fingerprint sensor wouldn't work.

Jure_aleksic said:
I was searching a bit about snapdragon 430 and the devices that use it.
And i came across a device with the same specs as redmi 3s(land)
So, i was wondering,
Could we use it?
Its stable and built on AOSP
Device link=http://m.gsmarena.com/bq_aquaris_u_plus-8378.php
Rom links=https://www.bq.com/en/support/aquaris-u-plus/support-sheet
Click to expand...
Click to collapse
Those are stock ROM links, probably not much interesting in these ROM's anyway

The kernels are different, CPU frequencies also different.

Yappuccino said:
The kernels are different, CPU frequencies also different.
Click to expand...
Click to collapse
Frequencies are the same

Jure_aleksic said:
Frequencies are the same
Click to expand...
Click to collapse
Kernel still isn't the same.
You can try replacing the vendor directory, and the /system/etc/firmware directory, and you will still get many features don't work.