Related
Hi guys,
I stopped a while to build rom for tatoo but I continued to follow the thread.
For fun I have compiled the latest stable kernel ... if anyone cares to test it I'll put the link here.
I take this opportunity to insert a link to my kernel sources generated using HTC.
I think it's correct to use this kernel for the development of libraries on the camera and radio, as it turns out to be the only kernel you know works.
Compiling the latest kernel I have seen many great features ... but totally missing some drivers, such as those in radio ...
I do not understand this anxiety developers to have a custom kernel and the most updated ... But I think it is appropriate to start building a secure kernel. When the camera and the radio works then you can create as many kernels you want ... but not before.
This is my thought ... meanwhile I'll use this post to whoever wants to download the kernel and HTC for those who want to test my kernel 2.6.35.4.
Kernel_2.6.29_HTC
contain for shure all drivers for FMRadio,camera,bt ecc and all htc patches (if presents). this kernel il generated from HTC kernel source downloaded from htc site.
Features added: ext3 and ext4 partitions support
Kernel_2.6.35.4_v1NOT WORKING
Is a testing kernel. it is generated compiling the last stable source released on kernel.org
Kernel_2.6.35.4_v2
- FMRadio diriver inculded
- voltage and current regulator support
- Led drivers
- ext3 ext4
nice job, my friend.
francians said:
nice job, my friend.
Click to expand...
Click to collapse
is not nice... it haven't the radio drivers and i don't know if it work well...
i have only spent some time today because i have nothing to do..
it isn't a serious kernel for me...
ikxdf said:
Hi guys,
... But I think it is appropriate to start building a secure kernel. When the camera and the radio works then you can create as many kernels you want ... but not before.
Click to expand...
Click to collapse
Although I´m no dev, this is actually very sensible. I´d rather had a slightly outdated but FULLY functional kernel, than the most up-to-date but crippled one...
No source or config files or tweeks you made?
Good day ikxdf!
Seg
segway_ said:
No source or config files or tweeks you made?
Good day ikxdf!
Seg
Click to expand...
Click to collapse
i will upload the source and the config soon
The attached kernel Kernel_2.6.35.4_v1_[ikxdf].zip does not even boot.
No adb no something on /proc/last_kmsg after boot to recovery!!
Nice try ikxdf.
Seg.
segway_ said:
The attached kernel Kernel_2.6.35.4_v1_[ikxdf].zip does not even boot.
No adb no something on /proc/last_kmsg after boot to recovery!!
Nice try ikxdf.
Seg.
Click to expand...
Click to collapse
This is because he based it on the stock Linux kernel, and not the android branch... I don't even know if it's compiled for ARM or x86, but I'll check that soon...
Sent from my HTC Hero using XDA App
EDIT: I have checked for the kernel architecture and it is compiled for ARM. I also took the liberty of extracting the config from it, and saw that it seriously need lots of attention. I have attached a copy of the config below... BTW: good luck with getting this to work
segway_ said:
The attached kernel Kernel_2.6.35.4_v1_[ikxdf].zip does not even boot.
No adb no something on /proc/last_kmsg after boot to recovery!!
Nice try ikxdf.
Seg.
Click to expand...
Click to collapse
please sega-way evitate your sarcasm and read well before writing:
ikxdf said:
is not nice... it haven't the radio drivers and i don't know if it work well...
Click to expand...
Click to collapse
ikxdf said:
For fun I have compiled the latest stable kernel ... if anyone cares to test it I'll put the link here.
Click to expand...
Click to collapse
if u don't know i haven't a tatto for testing.
if anyone want test and send me the error i will try to fix if i find the time.
for me the only correct kernel is the 2.6.29 compiled from the htc source. All other kernel is only a game.
For the next time...learn to read all post before writing.
Thanks
kiljacken said:
This is because he based it on the stock Linux kernel, and not the android branch... I don't even know if it's compiled for ARM or x86, but I'll check that soon...
Sent from my HTC Hero using XDA App
EDIT: I have checked for the kernel architecture and it is compiled for ARM. I also took the liberty of extracting the config from it, and saw that it seriously need lots of attention. I have attached a copy of the config below... BTW: good luck with getting this to work
Click to expand...
Click to collapse
thanks Kill. I can't take a look now but next week i will try to recompile it. Please i need a .config of a original 1.6 ROM...can u upload it here?
ikxdf said:
thanks Kill. I can't take a look now but next week i will try to recompile it. Please i need a .config of a original 1.6 ROM...can u upload it here?
Click to expand...
Click to collapse
from the tattoo.. it was gz now is zip
ikxdf said:
please sega-way evitate your sarcasm and read well before writing
Thanks
Click to expand...
Click to collapse
Its just a feedback...
Sorry if you take it as something else....
Seg
i'm trying to made this kernel booting and have add some features:
- FMRadio diriver inculded
- voltage and current regulator support
- Led drivers
if anyone want test it i will upload it today
uploaded in first posts
I've been away from the Tattoo scene since we got root on this little device.
I'm currently interested in getting psfreedom to run on Tattoo but it seems that the stock HTC kernel is crippled (missing usb stuff). If your kernel is at least bootable, this would be a nice place to start
mainfram3 said:
I've been away from the Tattoo scene since we got root on this little device.
I'm currently interested in getting psfreedom to run on Tattoo but it seems that the stock HTC kernel is crippled (missing usb stuff). If your kernel is at least bootable, this would be a nice place to start
Click to expand...
Click to collapse
if u are talking about 2.6.35.4 version you have to try if it can boot because i haven't a tattoo for test it.
I have sell my tattoo after 2 week but all great users of this thread have always made a great testing job for me and for my rom.
If anyone want test if this kernel is booting or not i will contine to develope it.
If it doesn't boot and adb will start i need a logcat.
if u are talking of the original htc kernel 2.6.29 version it is already working on my rom (Pancake) .
i will release sonn the wlan.ko module for 2.1 and for 2.2 roms for the 2 versions of kernel.
Hi, ikxdf!
I'm willing to try your kernel. I am quite an experienced linux user of desktop and server but I'm quite new regarding ROM flashing. But still, from what I gather I have to flash your kernel archive in the boot sector, right?
I have AmonRA's recovery installed and tested. And I'm eager to try cooked stuff as I've just gotten my Tattoo out of service today after 3 weeks!!! I was so dissapointed in having my old Nokia again.
I apologize for my bad English I am Italian and use google translate
I need a guide on how to compile Android from source
(the ParanoidAndroid for accuracy)
which linux distro to use?
which packages to install?
which commands to use?
I have a lot of time free
and a core i5 cpu
I think that to compile Android from source
but I need a guide
then I ask you developers, you can post a guide
----------------------------------------------------------------------------------------
write from my pc using win8 e programming a websites
bomdia said:
I apologize for my bad English I am Italian and use google translate
I need a guide on how to compile Android from source
(the ParanoidAndroid for accuracy)
which linux distro to use?
which packages to install?
which commands to use?
I have a lot of time free
and a core i5 cpu
I think that to compile Android from source
but I need a guide
then I ask you developers, you can post a guide
----------------------------------------------------------------------------------------
write from my pc using win8 e programming a websites
Click to expand...
Click to collapse
Well, you need a lot of work to get a working build, as i currently compile CM9 for SXL.
Recommended distros: Ubuntu 12.04 Precise / Linux Mint 13 Maya with Cinnamon interface to have the best linux experience << The best linux distro i ever used
Packages: Well, you need to check the Paranoid site to download the repo for ICS or JB variant of source-code.
Commands: Lots of commands, there are tutorials online. Example >> here
After this, you will need the device tree for SXL, i have one that is deprecated (not updated for some time), it does not work the variant uploaded here, but i will upload it.
You will need the vendor files, i also have the files but as the build of CM9 don't work, i haven't upload them anywhere untill i can get an at least experimental build that boots
Link for android device tree for sxl by me here
There is a lot of work and there aren't any specific guides on how to do this, you need to join communities and be a pain on the ass for them untill you learn how to do this.
I hope this helps anyways
Lexmazter said:
Well, you need a lot of work to get a working build, as i currently compile CM9 for SXL.
Recommended distros: Ubuntu 12.04 Precise / Linux Mint 13 Maya with Cinnamon interface to have the best linux experience << The best linux distro i ever used
Packages: Well, you need to check the Paranoid site to download the repo for ICS or JB variant of source-code.
Commands: Lots of commands, there are tutorials online. Example >> here
After this, you will need the device tree for SXL, i have one that is deprecated (not updated for some time), it does not work the variant uploaded here, but i will upload it.
You will need the vendor files, i also have the files but as the build of CM9 don't work, i haven't upload them anywhere untill i can get an at least experimental build that boots
Link for android device tree for sxl by me here
There is a lot of work and there aren't any specific guides on how to do this, you need to join communities and be a pain on the ass for them untill you learn how to do this.
I hope this helps anyways
Click to expand...
Click to collapse
thanks a lot I think I start tomorrow I'm a little tired
Hi just so you know you won't be able to compile Paranoid Android for ICS from source as it was never released.
If you can get JB to work then you will not only be a hero but also be able to use Paranoid Android source
I have a problem I can not download the sources of the paranoid in any way
help (or build the sources normal Android?)
Did you follow a guide how to set up the environment in linux? Or Mac.. the way you can download sources is git clone and then the git link. There are many guides on doing that part. Also when I download source it times out in a 4 mb/s connection and I need to use a better connecyion
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
anders3408 said:
Did you follow a guide how to set up the environment in linux? Or Mac.. the way you can download sources is git clone and then the git link. There are many guides on doing that part. Also when I download source it times out in a 4 mb/s connection and I need to use a better connecyion
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Click to expand...
Click to collapse
aa ok but the guide I was reading did not say that it was necessary to clone each of the sources piece by piece, but he said to use a single link.
I have linux mint 14 with cinnamon (from the 13 consigliatami lextmazter I do not work)
both in Italy and in spite of my connection is approximately 16 mb / s (88% above the national average)
Post link to guide.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
bomdia said:
aa ok but the guide I was reading did not say that it was necessary to clone each of the sources piece by piece, but he said to use a single link.
I have linux mint 14 with cinnamon (from the 13 consigliatami lextmazter I do not work)
both in Italy and in spite of my connection is approximately 16 mb / s (88% above the national average)
Click to expand...
Click to collapse
I do not recommend Linux Mint 14 as it is new edition, based on new Ubuntu version 12.10 if i remember good, don't know for sure, that's why, on Ubuntu 12.04 building is supported, even though on some guides it is said that on 12.04 it is experimental, well, it was, now it should be stable.
Also, if you want to port things like Paranoid or PAC you should start with AOSP or CM9 or AOKP, to put it short, versions that have guides and source codes on their sites. In my opinion CM is the best thing to start with, that's why i started CM9, after that you can easily port every 4.0.4 AOSP based ROM.
The same thing applies to JB, if you can port or build AOSP or CM10, you can port every JB AOSP based ROM very easily following only a few basic steps, that's how things work in this hood
Off-topic: I was a little distracted from building/testing/devving because of the school affairs, but today i will resume my work on CM9, if things work well, i will have a bootable build this very evening.
same as lexmazter, sound correct. the hard part is build CM9 rom, rest is pretty easy.
Lexmazter, i am about to try take a ramdisk from cm9 primou and make changes in every lines and see if i can get it to work with runnymede. if it does we will have a working aosp bootimg. i have compiled a zimage from source and it works with wifi and bt and so on in sense rom, also zimage works with cm9 with wifi.
lexmazter, can you please take a bencmark test with antutu 3.0.1, the new one, and post screenshot of the score and wich rom you are in ? they have made the test much diffrend so score is diffrend in 3.0.1 than older , so i have nothing to compare it to
anders3408 said:
same as lexmazter, sound correct. the hard part is build CM9 rom, rest is pretty easy.
Lexmazter, i am about to try take a ramdisk from cm9 primou and make changes in every lines and see if i can get it to work with runnymede. if it does we will have a working aosp bootimg. i have compiled a zimage from source and it works with wifi and bt and so on in sense rom, also zimage works with cm9 with wifi.
lexmazter, can you please take a bencmark test with antutu 3.0.1, the new one, and post screenshot of the score and wich rom you are in ? they have made the test much diffrend so score is diffrend in 3.0.1 than older , so i have nothing to compare it to
Click to expand...
Click to collapse
5941 no OC with LTX Kernel v0.7 and Sense 3.0 by fshami, also, i think i found the right ramdisk for now for CM9, it solved the dalvik-permissions, now i still need to boot the build, still trying to figure what is wrong here and why it hangs after Android is upgrading... >> Starting applications.
I can work more on my device now as i have a cheap second phone to use if for calls and sms.
so then I decided, when I start buildare the source of AOSP Android 4.2 jellybean I think it's easier for me to start.
I had to use because the new mint old man crashed always
bomdia said:
so then I decided, when I start buildare the source of AOSP Android 4.2 jellybean I think it's easier for me to start.
I had to use because the new mint old man crashed always
Click to expand...
Click to collapse
As a recommandation, i would recommend building AOSP 4.0.4, it is easier to start and has more chances of working, after that, you have the experience and the headstart to work on 4.1 and only after that on 4.2.
Just start with baby-steps, it is easier and increases the chances of success.
Lexmazter said:
As a recommandation, i would recommend building AOSP 4.0.4, it is easier to start and has more chances of working, after that, you have the experience and the headstart to work on 4.1 and only after that on 4.2.
Just start with baby-steps, it is easier and increases the chances of success.
Click to expand...
Click to collapse
ahh ok then I try to go with 4.1 if I can not then step 4.0.4
bomdia said:
ahh ok then I try to go with 4.1 if I can not then step 4.0.4
Click to expand...
Click to collapse
Well, i recommend this because i'm still building 4.0.4 and i haven't successfully booted a build, so that's why i say this, because if you get the 4.0.4, in short terms, all you need to change for 4.1 is the graphics driver, but for 4.2 i don't know for sure, too new for me and i'm still trying to get 4.0.4 to air
then my kernel is not so bad 5838 with sense 4.1 v. 1.5.1 and still missing some improvments
which ramdisk are you using, zimage from stock rom should get it to boot, but the ramdisk as you know need to be changed to cm9. when you compile from source it should also make a ramdisk that will fits the rom, i think it is best to check what the diffrence in the new ramdisk and the old one with VM errors and then fix them, perhaps it will boot then ? one specific compiled by you ? post a logcat in your cm9, had also some bootloop in my cm9 port but got it booting.
anders3408 said:
then my kernel is not so bad 5838 with sense 4.1 v. 1.5.1 and still missing some improvments
which ramdisk are you using, zimage from stock rom should get it to boot, but the ramdisk as you know need to be changed to cm9. when you compile from source it should also make a ramdisk that will fits the rom, i think it is best to check what the diffrence in the new ramdisk and the old one with VM errors and then fix them, perhaps it will boot then ? one specific compiled by you ? post a logcat in your cm9, had also some bootloop in my cm9 port but got it booting.
Click to expand...
Click to collapse
just enter the irc channel, will talk more there, no need to spam the forum with this.
The boothanging is because of the audio, the ramdisk is good, i use the LTX v0.7 zImage and ramdisk from stock edited to fit the build.
Also, the ramdisk is not made with the build, maybe if you compile the kernel with the rom, and for this you need to put the kernel online and othe things, and because of proxy, i can't and won't do that. For more details, like i said, find me on the irc.
link here
you say that jelly beans to need a new kernel? because sifting through the Internet I found this: https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources there are also drivers for jelly bean of adreno 2xx
bomdia said:
you say that jelly beans to need a new kernel? because sifting through the Internet I found this: https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources there are also drivers for jelly bean of adreno 2xx
Click to expand...
Click to collapse
yeah, those are the drivers
But they do not require a new kernel
Lexmazter said:
yeah, those are the drivers
But they do not require a new kernel
Click to expand...
Click to collapse
but I need or I do not need?
Welcome to the official thread for the Lollipop roms for our Optimus 2x
As to start, this thread is exclusively for the developers who are interessted/working on on the Lollipop ports for our Optimus 2x
We had alredy some build like the OmniRom , CM12 and even ParanoidAndroid.
This thread is exclusively for discussions for the developers and for the testers to test the new made roms so I will update the links as the roms get made. So I am only posting here the links of the latest version, to get the versions from the past you wil need to browse throught this thread
Update 05/6/2016
Gucky did it again! New build for CyanogenMod 12.1 is up, and now with fixed camera! When I get the full list of working features and bugs, I will upload it here. Thank you Gucky for your massive help and contribution to this community. This device is very old after all, and you still find the time to tinker on it. No words really. Respect!
CM12.1 : https://sourceforge.net/projects/lg...cm-12.1-20160531-UNOFFICIAL-p990.zip/download
WARNING the Rom is still not stable, but we are close!
ParanoidAndroid: https://s.basketbuild.com/devs/Puri/p990/AOSPA(lollipop)
Take in mind that all these roms are unstable besides the CM12 rom,but it still has some major bugs which we as a group will fix.
As in all of this, stay tuned for updates
Good job my friend
Thank you very much. I'm downloading right now. It would be useful, if you could upload your (Lokal) Manifest, too. So we are able to re- build the rom with the necessary changes.
Looking forward!
Credits goes to you!
um
gucky01 said:
Thank you very much. I'm downloading right now. It would be useful, if you could upload your (Lokal) Manifest, too. So we are able to re- build the rom with the necessary changes.
Looking forward!
Credits goes to you!
Click to expand...
Click to collapse
um.......*noob mode activated.....BOOP * what you mean with manifest? lol
Could you please share your sources.
TheMysteryouse said:
Hello everyone.As you might know me from some threads where i comment some stuff.Anyways, since Lollipop was announced i was obssesed with it and my wish was that i would be the first one to make the version availble for our device.
Well i kinda did it....KINDA of course but we need some help if we wanna make it work.I call ALL of the developers for our device to work together to make it work.We are so close to get it fully booting.I made it boot to the animation and now where the help comes in use.We need some developers who can enable ADB on our device in the bootanimation.TO be honest i dont really know anything about sources and that stuff but i know some things.With the help of @tonyp and @timduru which I am the most thankfull of that gave me hope to make this.So here we go!
WARNING!!!
ONLY FOR DEVELOPERS
No one should download and flash this rom because you will get stuck in the bootanimation and will need to install previouse rom again and install everything over...blah blah blah.
Also the link to the rom is here ----> https://www.dropbox.com/s/fwhg08ux7qhtgsh/5.0 test.zip?dl=0
So if someone gets it working, please pm me in the progress. Cheers
Click to expand...
Click to collapse
TheMysteryouse said:
um.......*noob mode activated.....BOOP * what you mean with manifest? lol
Click to expand...
Click to collapse
a little help.
http://wiki.cyanogenmod.org/w/Doc:_Using_manifests
Oh
Hugo-PT said:
a little help.
http://wiki.cyanogenmod.org/w/Doc:_Using_manifests
Click to expand...
Click to collapse
Well to be honest, i dont really know how to share the menifest because i didn't use much the source. I was porting the Cm11 tonyp's rom and the rom from timduru, so i dont really know how to share the manifest lol
TheMysteryouse said:
Well to be honest, i dont really know how to share the menifest because i didn't use much the source. I was porting the Cm11 tonyp's rom and the rom from timduru, so i dont really know how to share the manifest lol
Click to expand...
Click to collapse
Did you change some files in the zips or did you build a new rom in the way Raum described, my friend?
http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305
nope
gucky01 said:
Did you change some files in the zips or did you build a new rom in the way Raum described, my friend?
http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305
Click to expand...
Click to collapse
nope, didn't touch anything other than the updater script i think and the build prop because i wanted fully stock experience
I can be your tester my phone got a battery problem so im having fun with flashing roms
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
DJNoXD said:
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
Click to expand...
Click to collapse
Well, it might be that he used KatKiss from timduru for the TF101 which has a Tegra 2, but still our phone uses the Tegra 2 AP20H, while the TF101 uses Tegra 2 T20. Small difference in the chipset, but still a difference. Easiest would be to port from the Galaxy R or Captivate Glide, but they too struggle with Lollipop over in their forum. Anyway, TheMysteryouse used timduru's AOSP rom, so maybe it would be easier building the whole thing from the demo CM12 sources available.
nonono
DJNoXD said:
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
Click to expand...
Click to collapse
Nope, this rom has NOTHING to do with the tegra 3 rom.I used the rom for TF101 tablet which is tegra 2 but had a cmall chipset difference.So yeah I am still trying to do some things like searching the framework sources from tony to see if he has a code in the build.prop which directly enables ADB from the boot, but cant really find it.Anyways try your best and so the others.Cheers
Hi guys, after some testings I could get booting to finish. There are some errors left. But I will work further this evening and upload the rom afterwards. Think this will remain a test build for some time, till Tony or DJ can fix the errors.
Stay tuned!
Any video or screenshot? xD
Sorry for nob request, but working well or not, its great to our comunity
p.s. if need tester in future, you, TheMysteryouse or DJNoXD.
Im ready for
...WoW!...That´s Good News...Thank You for All of You, Guy´s...
gucky01 said:
Hi guys, after some testings I could get booting to finish. There are some errors left. But I will work further this evening and upload the rom afterwards. Think this will remain a test build for some time, till Tony or DJ can fix the errors.
Stay tuned!
Click to expand...
Click to collapse
Awesome news buddy! Lollipop on first power dual core android device! Switch to 1+ One as a primary phone for some reason but I will continue to follow and supporto you!
That is great!!! ))))))))
Ok. I have to go one step back. The rom is not ready for the testers and I'm too tired to test more. For those, who want to repeat my steps or want to finish...
I replaced the files in Mystery's rom with my own Kitkat ones. The first half, than the second. Now I could get it to finish the booting process. This steps I went on and on. So I could reduce the problem to the framework-files in "system". If you replace all of them, it boots up with some error messages.
I think we have to reduce the 40 files inside more and more to find the reason for the bootloop.
All the best to you,my friends!
Damm this is great a device from 2010 receives android L. 4years later. If I can borrow the old optimus 2x from my father then I could also look into the problems if it's not booting yet then. Till then continue your work.
Fix camera?
https://forum.xda-developers.com/chef-central/android/guide-porting-64bit-mtk-roms-mt6735-t3563807
I think that wont work, because our kernel or rom base is on 32bits o something like that, but i'm not sure, @vampirefo can confirm this if he want to
I believe these files listed are already ported into the build.
I had my doubts that this would make any change for our device, but i put the files into a patch install and tried it.
still No camera ..! sorry .
unless the files also needed to have permissions applied.
New rom compatible with Blu R1HD?
https://forum.xda-developers.com/android/development/nougat-unofficial-t3567653
menphis said:
New rom compatible with Blu R1HD?
https://forum.xda-developers.com/android/development/nougat-unofficial-t3567653
Click to expand...
Click to collapse
Not directly, would need to be "ported" and tweaked. That post says its for same processor and is tagged as "Coolpad 3"
Be careful testing with it. It comes from a general thread not any device specific thread so who know what to really is.
mrmazak said:
Not directly, would need to be "ported" and tweaked. That post says its for same processor and is tagged as "Coolpad 3"
Be careful testing with it. It comes from a general thread not any device specific thread so who know what to really is.
Click to expand...
Click to collapse
Thanks friend.
Can the library work for R1HD camera in nougat?
menphis said:
Thanks friend.
Can the library work for R1HD camera in nougat?
Click to expand...
Click to collapse
Do not know. It would have to be tested.
If there was a way to know what camera module the r1-hd has and then compare it to the one for cool-pad 3 lite has.
Other than being able to do that it is left to trial and error.
Is already there and is not working I think is something with the boot img I mean the kernel part
Id really like to see the camera working. I dont mind my R1s camera not working really because i dont use it, But if it were working the Rom would receive unofficial build status instead of the "beta" and "discontinued" its been getting.
I have Nougat on my R1 solely thanks to Mrmazak
10033859 said:
Id really like to see the camera working. I dont mind my R1s camera not working really because i dont use it, But if it were working the Rom would receive unofficial build status instead of the "beta" and "discontinued" its been getting.
I have Nougat on my R1 solely thanks to Mrmazak
Click to expand...
Click to collapse
Well, unless you switch phones or Blu releases an update camera won't be fixed.
To be honest camera isn't very good in any built rom for Blu devices, I have several roms I built for Blu Life Max, camera works but it isn't very good, pink haze on back camera, front camera is ok, still not as good as stock rom, or ported stock rom from another device.
Sent from my NXA8QC116 using Tapatalk
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
menphis said:
Fix camera?
https://forum.xda-developers.com/chef-central/android/guide-porting-64bit-mtk-roms-mt6735-t3563807
Click to expand...
Click to collapse
64bit won't work on 32bit, nor will 32bit work on 64bit, no way around that.
A 32bit kernel can only use 32bit binaries, 64bit kernel can only use 64bit binaries.
Sent from my NXA8QC116 using Tapatalk
vampirefo said:
Well, unless you switch phones or Blu releases an update camera won't be fixed.
To be honest camera isn't very good in any built rom for Blu devices, I have several roms I built for Blu Life Max, camera works but it isn't very good, pink haze on back camera, front camera is ok, still not as good as stock rom, or ported stock rom from another device.
Click to expand...
Click to collapse
Yeah you got a point. The camera was never very good on Cyanogen or Lineage. Or even for that matter on the BLU rom itself... When i need the camera i just use my other S6 Active.
vampirefo said:
A 32bit kernel can only use 32bit binaries, 64bit kernel can only use 64bit binaries.
Click to expand...
Click to collapse
The compat layer (see CONFIG_COMPAT) in the kernel allows for 32 or 64-bit userland with 64-bit kernel and is supported by Android. The tinno 64-bit config has this enabled.
mumbel said:
The compat layer (see CONFIG_COMPAT) in the kernel allows for 32 or 64-bit userland with 64-bit kernel and is supported by Android. The tinno 64-bit config has this enabled.
Click to expand...
Click to collapse
that means nothing, no matter.
good luck compiling a 64bit kernel out of 32bit source.
perhaps R1HD Plus, kernel source might be of some use to you all, the phone is advertised as 64bit, I think it's really going to be 32bit, but won't know til someone gets one.
vampirefo said:
that means nothing, no matter.
good luck compiling a 64bit kernel out of 32bit source.
Click to expand...
Click to collapse
You didn't know you could run 32-bit binaries in a 64-bit kernel, and now you're saying you can't compile 64-bit kernels out of 32-bit source, whatever you think you mean by that. The point of me mentioning the tinno config is there is a 32-bit config and 64-bit config for the same soc and surprise, it uses the same source. There is minor difference in the config choosing arch/arm and arch/arm64, but it still compiles and the source is there to do it.
mumbel said:
You didn't know you could run 32-bit binaries in a 64-bit kernel, and now you're saying you can't compile 64-bit kernels out of 32-bit source, whatever you think you mean by that. The point of me mentioning the tinno config is there is a 32-bit config and 64-bit config for the same soc and surprise, it uses the same source. There is minor difference in the config choosing arch/arm and arch/arm64, but it still compiles and the source is there to do it.
Click to expand...
Click to collapse
I can't help you learn the difference, you will get there on your own.
A 64bit kernel can't run 32bit binaries, nor can a 32bit kernel run 64bit binaries.
You are confusing Linux kernel with Android kernel.
Android kernel 64bit uses a 64bit toolchain Android kernel 32bit uses a 32 bit toolchain neither kernel could possibly run any binaries compiled with the other toolchain.
But, instead of me trying to teach you the difference, go ahead and fix the camera with the 64bit binaries, no better teacher than hands on, get your hands dirty.
Sent from my LIFE X8 using Tapatalk
did anybody seen this thead https://forum.xda-developers.com/k3-note/orig-development/rom-custom-nougat-roms-k-3-note-t3513466
liviu_anc said:
did anybody seen this thead https://forum.xda-developers.com/k3-note/orig-development/rom-custom-nougat-roms-k-3-note-t3513466
Click to expand...
Click to collapse
What's written there is 100% correct, that's why camera will never ever work, unless Blu releases an update.
That's the main reason I got rid of the phone, other phones don't have the same limitations that R1HD has.
My Life Max doesn't have the problem, hopefully the new R1HD plus doesn't either.
Sent from my Life_Max using Tapatalk
vampirefo said:
What's written there is 100% correct, that's why camera will never ever work, unless Blu releases an update.
That's the main reason I got rid of the phone, other phones don't have the same limitations that R1HD has.
My Life Max doesn't have the problem, hopefully the new R1HD plus doesn't either.
Click to expand...
Click to collapse
I hope to the new r1 hd it doesn't have this kind of problems is having a different processor anyway I read something like the new r1 hd plus has a 64 bit processor
liviu_anc said:
I hope to the new r1 hd it doesn't have this kind of problems is having a different processor anyway I read something like the new r1 hd plus has a 64 bit processor
Click to expand...
Click to collapse
I think that was just another lie Blu told, I am betting it's 32 bit.
If 32 bit and camera doesn't use junk libaries like R1HD, the phone can run many custom roms.
Most likely run same roms my Life Max can.
Should know soon enough a lot of people ordered the phone.
Whether is 64 bit or 32 bit.
Sent from my Life_Max using Tapatalk
vampirefo said:
I think that was just another lie Blu told, I am betting it's 32 bit.
If 32 bit and camera doesn't use junk libaries like R1HD, the phone can run many custom roms.
Most likely run same roms my Life Max can.
Should know soon enough a lot of people ordered the phone.
Whether is 64 bit or 32 bit.
Click to expand...
Click to collapse
When I will get to us I will order straight that phone who knows probably is having a 64 I didn't seen one in real life so I don't know yet just let's hope is a 64
like they say here https://www.mediatek.com/products/smartphones/mt6737
hi all
for those impatient and dare to try, plus able to handle problems ON YOUR OWN as i cannot offer any help at this point:
anyone interested to test an updated version of BeastMode Kernel R154 by @freeza with the latest samsung firmware N960FXXU8FUD1?
please be noted that:
- this might be EXTREMELY DANGEROUS or could BRICK YOUR PHONE in a few seconds, and I am not responsible for bricked devices or any damages which may arise. so, you have been WARNED
- I have NOT TESTED on my n960f yet (just updated to TH4 from pie but not rooted yet for some reasons). SO THINK TWICE!!
- chances the phone may not boot up properly (boot loop or hang) due to the toolchains used to compile the kernel. I have encoutered this before with only one of the four or five gcc i had which booted up the phone successfully
ideal situation to minimize uncertainties:
- already on ud1
- data/cache partition is ext4 formatted (ideally NOT f2fs as supported by bm kernel)
- capable of diagnostic/identify the problems by examining the logcat/last_kmsg and the like would defintely a plus
to be continued...
Hello, Is this gonna work on newer BL version? FUE5 version, also @CyderXDA would wanna try it, but he's on newer BL. We also have Exynos9810 Telegram Chat, there's N9/S9/S9+ users in there that maybe could test for you and stuff if you're interested
JC1126 said:
Hello, Is this gonna work on newer BL version? FUE5 version, also @CyderXDA would wanna try it, but he's on newer BL. We also have Exynos9810 Telegram Chat, there's N9/S9/S9+ users in there that maybe could test for you and stuff if you're interested
Click to expand...
Click to collapse
hi
samsung has just posted a newer firmware N960FXXS8FUE5, probably hours ago, i am going to update it first. will let you guys know
thanks for your interests
ykkfive said:
hi
samsung has just posted a newer firmware N960FXXS8FUE5, probably hours ago, i am going to update it first. will let you guys know
thanks for your interests
Click to expand...
Click to collapse
Alright Goodluck!
JC1126 said:
Alright Goodluck!
Click to expand...
Click to collapse
update 20160616
updated to samsung ue5 sources
i have built 2 different versions, one with gcc 4.9 and the other with gcc 12. there will be only one version in the future (either gcc4 or 12). the reason i built 2 versions this time is in case one of the gcc used doesnt boot probably there's another one to try
differences between @freeza 's R154:
- kernel sources updated (N960F) without any fix or new feature
- not pre-rooted/pre-patched by magisk since the magisk version may differs from what u r using
- NOTE: other devices preiously supported are not recommeded yet, although you may try, i cant make any promise it will work since i didnt look at other devices sources
thinking if i should release it for testing now or wait until i have time to test it myself coz i don want to brick anyone's phone, including mine of coz
ykkfive said:
update 20160616
updated to samsung ue5 sources
i have built 2 different versions, one with gcc 4.9 and the other with gcc 12. there will be only one version in the future (either gcc4 or 12). the reason i built 2 versions this time is in case one of the gcc used doesnt boot probably there's another one to try
differences between @freeza 's R154:
- kernel sources updated without any fix or new feature
- not pre-rooted/pre-patched by magisk since the magisk version may differs from what u r using
- f2fs supported as R154 (cache/data)
thinking if i should release it for testing now or wait until i have time to test it myself coz i don want to brick anyone's phone, including mine of coz
Click to expand...
Click to collapse
Holy that's insane, you added f2fs that's exciting, wonder if it supports AOSP because most of n9 users use aosp, some use noblerom
JC1126 said:
Holy that's insane, you added f2fs that's exciting, wonder if it supports AOSP because most of n9 users use aosp, some use noblerom
Click to expand...
Click to collapse
i didnt add anything new, but i found in his fstab, f2fs is ready. i didnt examine the kernel sources yet. this it true for aosp etc also
so in case f2fs/aosp etc was supported in his R154, it should be, i believe...
sorry, but NO f2fs there in his kernel!!
ykkfive said:
i didnt add anything new, but i found in his fstab, f2fs is ready. i didnt examine the kernel sources yet. this it true for aosp etc also
so in case f2fs/aosp etc was supported in his R154, it should be, i believe...
Click to expand...
Click to collapse
that's cool, can't wait to try it out in lineage a11 lol
JC1126 said:
that's cool, can't wait to try it out in lineage a11 lol
Click to expand...
Click to collapse
i just checked the output, there's no f2fs unfortunately but i can add it later after test
ykkfive said:
i just checked the output, there's no f2fs unfortunately
Click to expand...
Click to collapse
that's still fine tbh, not much difference on ext4, good thing is it works on aosp, idk if it'll boot on oneui3.1 because it needs a permissive kernel to boot so yeah
JC1126 said:
that's still fine tbh, not much difference on ext4, good thing is it works on aosp, idk if it'll boot on oneui3.1 because it needs a permissive kernel to boot so yeah
Click to expand...
Click to collapse
tbf i have not built one with both sammy and aosp supported kernel, and i even don't know his kernel supports aosp
for the one ui 3.1 thing, u mean the ported one? i believe he's made it to run on existing kernel so it should be fine. of coz it needs to be tested first
ykkfive said:
tbf i have not built one with both sammy and aosp supported kernel, and i even don't know his kernel supports aosp
for the one ui 3.1 thing, u mean the ported one? i believe he's made it to run on existing kernel so it should be fine. of coz it needs to be tested first
Click to expand...
Click to collapse
Ohh alright then
update 20210618
the ue5 kernel works properly so far, tested on stock rom only due to unable to get a ue5 custom rom atm
will be released soon
thanks a lot
released, closed