Related
As per the title says, just so happen to check the Lenovo forums today after reading here they released TPT source yesterday and sure enough the K1 source was released this morning!
Direct Link
http://download.lenovo.com/lenovo/content/sm/IdeaPadTablet-K1.zip
Link to the Thread
http://forums.lenovo.com/t5/IdeaPad-Slate-Tablets/Android-Source-Code/td-p/610273/page/5
Hopefully our humble and dedicated developers can tear this apart and start on some custom ROMS, maybe even kernels?? (I have high hopes clearly!)
On a side note, might not be worth mentioning, but I did notice that the source for the K1 was roughly 72mb in size while the TPT source was in upwards of 202mb?? Same compression for both, food for thought...
Robert
Great news ....the building blocks have arrived
Sent from my HTC Evo 3D with Beats Audio X515m using XDA App
Now hoping for some love, the stock android is pretty slow and painful.....
Will be nice once the custom kernels come.. hopefully they will..
Sent from my GT-I9100 using XDA App
Thats awesome news, man!!!!!!! I didnt think lenovo would do it but wow, its a start.
Hopefully we can get some sweet roms and kernels on this bad boy (k1).
Just based on this news alone, I have ordered for one..
Sent from my HTC Vision
rezapatel said:
Just based on this news alone, I have ordered for one..
Sent from my HTC Vision
Click to expand...
Click to collapse
Bad choice, hardly any support and current android 3.2.1 on it is buggy for the two that we own, stutters a lot.
Be Prepared for this lengthy response!
twe69 said:
Bad choice, hardly any support and current android 3.2.1 on it is buggy for the two that we own, stutters a lot.
Click to expand...
Click to collapse
I agree even with the latest update, there are still bugs in the OS Lenovo loads on this tablet but this should not be a driving force with not buying one. Every tablet I've owned (K1 and the GTablet) or had the chance to tinker with (Xoom, Prime, etc...) have had their flaws, but I also feel this is also based on the user and their personal preferences with using their tablet. Not to mention, what that user would be using the device for (as a toy, or daily driver) has a huge amount to do with it.
What's important here is that they are all running on some form of an Android OS, and if you are willing to tinker and sometimes even experiment with your tablet, you will be able to get to some middle ground (depending on the device, its release date, the community following it has, and when/if the source code is released) based on what you are trying to get out of that particular device to where there are little to no issues.
http://rootzwiki.com/topic/13407-alpha-ideapad-k1-cwm-stock-rooted-rom-120109-build/
For me, I'm currently running the Alpha 3 CWM rom from rootzwiki (link above) and besides I think 1-2 FC's (ONLY happened upon uninstalling pre-loaded apps) it's ran smooth as silk! Granted, I use my K1 as mainly a 'toy' for experimenting with Android SDK, flashing ROM's and general tinkering but still...
Now, you could just drop the $400-$600 on an iPad and not have to worry about FC's and other bugs but then you're left with not only an extremely restricted device but a restricted device that you paid way more for when compared to the K1 for example. Don't get me wrong, after getting my first tablet (GTablet) I quickly realized the quality of the products Apple releases to the consumer public, and if you are a member of that 90%+ percentile of the public that just wants a device to work and doesn't plan on doing anything else to it (and possibly not being as computer savvy as that 5-10% percentile) Apple is the way to go. However atleast from my experiences with the iPad/iPhone, if you plan on doing any modifications remotely resembling base mod's that can be done on an Android device, you're either threatening your warranty or simply SOL.
In short, when I buy an Android phone/tablet I will never expect it to run flawlessly out of the box because A. I'm personally anal/picky/OCD with my hardware and B. I bought it for that initial time investment in order to have a device strictly tuned to my lifestyle and means of use. For this reason alone, an Apple product will never satisfy me (again nothing against anyone who does use Apple, just my 0.02).
I'd rather have a device that is cheaper to buy with arguably the same hardware specs or comparable and is finicky (to say the least at times), but has the potential to run whatever I can throw at it smoothly and most importantly to personalize it on levels that Apple would never allow on their products simply for fear of creating instabilities.
For the K1 however, Lenovo releasing the source is the 1st step towards achieving your own perfectly tuned and personalized device however long it might take. Afterall, one crucial characteristic of an Android user that majority of the members on this forum share is patience! It's what separates us from the rest!
Sorry for the long post, I just felt like expressing my opinion and I was in the typing mood.
Dueces99 said:
I agree even with the latest update, there are still bugs in the OS Lenovo loads on this tablet but this should not be a driving force with not buying one. Every tablet I've owned (K1 and the GTablet) or had the chance to tinker with (Xoom, Prime, etc...) have had their flaws, but I also feel this is also based on the user and their personal preferences with using their tablet. Not to mention, what that user would be using the device for (as a toy, or daily driver) has a huge amount to do with it.
What's important here is that they are all running on some form of an Android OS, and if you are willing to tinker and sometimes even experiment with your tablet, you will be able to get to some middle ground (depending on the device, its release date, the community following it has, and when/if the source code is released) based on what you are trying to get out of that particular device to where there are little to no issues.
http://rootzwiki.com/topic/13407-alpha-ideapad-k1-cwm-stock-rooted-rom-120109-build/
For me, I'm currently running the Alpha 3 CWM rom from rootzwiki (link above) and besides I think 1-2 FC's (ONLY happened upon uninstalling pre-loaded apps) it's ran smooth as silk! Granted, I use my K1 as mainly a 'toy' for experimenting with Android SDK, flashing ROM's and general tinkering but still...
Now, you could just drop the $400-$600 on an iPad and not have to worry about FC's and other bugs but then you're left with not only an extremely restricted device but a restricted device that you paid way more for when compared to the K1 for example. Don't get me wrong, after getting my first tablet (GTablet) I quickly realized the quality of the products Apple releases to the consumer public, and if you are a member of that 90%+ percentile of the public that just wants a device to work and doesn't plan on doing anything else to it (and possibly not being as computer savvy as that 5-10% percentile) Apple is the way to go. However atleast from my experiences with the iPad/iPhone, if you plan on doing any modifications remotely resembling base mod's that can be done on an Android device, you're either threatening your warranty or simply SOL.
In short, when I buy an Android phone/tablet I will never expect it to run flawlessly out of the box because A. I'm personally anal/picky/OCD with my hardware and B. I bought it for that initial time investment in order to have a device strictly tuned to my lifestyle and means of use. For this reason alone, an Apple product will never satisfy me (again nothing against anyone who does use Apple, just my 0.02).
I'd rather have a device that is cheaper to buy with arguably the same hardware specs or comparable and is finicky (to say the least at times), but has the potential to run whatever I can throw at it smoothly and most importantly to personalize it on levels that Apple would never allow on their products simply for fear of creating instabilities.
For the K1 however, Lenovo releasing the source is the 1st step towards achieving your own perfectly tuned and personalized device however long it might take. Afterall, one crucial characteristic of an Android user that majority of the members on this forum share is patience! It's what separates us from the rest!
Sorry for the long post, I just felt like expressing my opinion and I was in the typing mood.
Click to expand...
Click to collapse
great read excellent points
Sent from my Galaxy Nexus using Tapatalk
Dueces99 I shall check out that rom, will see if its possible for me since I am on the latest official version....
I did have a Blackberry Playbook with the original OS in December and that was much better for web browsing etc. Just hoping that Android 4 will have less issues on the tablet since I will be keeping the Lenovo....
Oh and I have been with Android for over 2 years since Android 1.5 and about 5 android phones..... So yeh I am patient
Will definitely pay attention to the next iteration of Windows Mobile though when I upgrade at the end of the year since I like the responsiveness of Windows Mobile 7/7.5.....
this is great news.. really think of selling mine for 300 or so.... if it still worth that ( 32 gb model) .. i might hold on to it now that the source is release and ( cross fingers) someone ports CM9 to it...
we can only wish...
lenovo said they will release ics for k1
http://forums.lenovo.com/t5/IdeaPad...m-Sandwich-for-Ideapad-K1/td-p/638437/page/17
Apologies for the radio silence on this... we have been in discussion with our product teams and shared all the interest and feedback received here.
I believe the current outlook is that a plain version (sounds like it will not include the Lenovo customizations ) of ICS will be made available for download sometime in June. This is a bit later than the original May schedule and will not be pushed as an OTA (over the air update).
I appreciate everyone's patience - I know you have been waiting a while for an update on this.
Thanks
Mark
Having been burned in the past by lack of drivers & resources for different devices, I started to wonder about the future of our Nook tablets.
I don't know anything about software and/or Android development so have no idea what is required to develop these ROMs.
Since the stock ROM runs on ICS and current development is on JB, are the drivers compatible?
Also, what about Android 4.3 (Key Lime Pie) and Android 5.0? When it is release by Google, would lack of stock ROMs be a hindrance to aftermarket development?
What exactly is needed by developers to create a (mostly) stable ROM for our Nook HD tablets & Android devices in general?
I hope someone with more knowledge than I possess can answer some of these queries.
Thanks.
IMO, my HD+ is pretty dang stable right now. I think the fact that the stock ROM is ICS-based helps a lot. Going forward, who knows? Hard to speculate, but with a solid kernel and that handles the devices capabilities, i think we should be good for a while.
I definitely appreciate the roms that SDBags and every other developer has made, but I was hoping for more options available, specifically in AOSP Roms. I love the transformer lineup because it is super useful as a cheaper high performing school laptop for note taking and has a stylus for taking notes with. But honestly, I rarely have cared for asus's stock software compared to AOSP, and AOSP definitely will give me much speedier performance, much more customization and much more recent updates overall.
Can any developers let me know why there haven't been more available AOSP Roms lately, or maybe its a problem with the tf701t hardware making it harder to Rom for? Or maybe not many people are buying this tablet? I just want an idea of what I would be in for if I buy this tablet soon.
Also, has any of the Tf700 tablet developers been asked to help develop for this tablet? (Just an Idea)
This is not a bashing on any developers who are making this Rom. Especially with SDBags. I have used his CROMI Roms on the TF300t all the time and they are AWESOME!!! I was just curious why the tablet hasn't gotten much attention in the ROMs section from hearing all sorts of good things from this tablet
royredman said:
I definitely appreciate the roms that SDBags and every other developer has made, but I was hoping for more options available, specifically in AOSP Roms. I love the transformer lineup because it is super useful as a cheaper high performing school laptop for note taking and has a stylus for taking notes with. But honestly, I rarely have cared for asus's stock software compared to AOSP, and AOSP definitely will give me much speedier performance, much more customization and much more recent updates overall.
Can any developers let me know why there haven't been more available AOSP Roms lately, or maybe its a problem with the tf701t hardware making it harder to Rom for? Or maybe not many people are buying this tablet? I just want an idea of what I would be in for if I buy this tablet soon.
Also, has any of the Tf700 tablet developers been asked to help develop for this tablet? (Just an Idea)
This is not a bashing on any developers who are making this Rom. Especially with SDBags. I have used his CROMI Roms on the TF300t all the time and they are AWESOME!!! I was just curious why the tablet hasn't gotten much attention in the ROMs section from hearing all sorts of good things from this tablet
Click to expand...
Click to collapse
Not many devs bought the device, we only have cm11 source available, I don't have time to make loads of roms from source, although I might have a surprise for you soon.
It's about time other people started learning how to build from source don't you think? How about you give it a go?
sbdags said:
Not many devs bought the device, we only have cm11 source available, I don't have time to make loads of roms from source, although I might have a surprise for you soon.
It's about time other people started learning how to build from source don't you think? How about you give it a go?
Click to expand...
Click to collapse
So you would teaching? [emoji56]
What do you want to know?
sbdags said:
Not many devs bought the device, we only have cm11 source available, I don't have time to make loads of roms from source, although I might have a surprise for you soon.
It's about time other people started learning how to build from source don't you think? How about you give it a go?
Click to expand...
Click to collapse
I totally understand where you are going at. You are a great developer and I am not asking specifically you, just mainly other developers that haven't shown their awesome work for this tablet. And, do you know anywhere good to get a tutorial how to build a rom for this device?
Is building a rom for this device much harder than building a rom for another device, like the tf300t? Does the Tegra 4 chip really hard to work with when creating the ROMS for this tablet? Is there a way I can test the rom onto an emulator build of the tf701 on the computer so then I wont risk my tablet being bricked due to my ignorance? sorry for all the questions.
How soon do you guys think a ROM will be made for Nook HD/HD+ after Android L releases? Any guesses? Cyanogen have done a great job with 4.4
That's just going to be a lot of assumptions
sandsofmyst said:
That's just going to be a lot of assumptions
Click to expand...
Click to collapse
Probably why you were the only one to reply xD Thanks man
Just don't like to see 0 replies. That said, there's one now and then that I won't reply to. However, L is of much interest to me and some of the supposed improvements will hopefully be great. Plus L on the nooks would hopefully be even better. So I share your enthusiasm.
The release time could be shorter or longer depending on the amount of porting work to be done. There's other variables too. But someone else might also before cyanogenmod which would be fun.
Thanks for the reply, I agree on L being even better on the Nook varieties. Can't wait!
I was finally starting to look into bumping stock off og my HD9 and saw this... guess I can wait 4-6 months for this to all take shape... I wouldn't want to lose my progress in PvZ2 at this point anyhow
My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.
Goggles2114 said:
My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.
Click to expand...
Click to collapse
With the nook being the nook... you could be right. The latest tech really makes android smooth, not android on the older tech.
OSs don't tend to get faster as they get fancier and the latest tablets and phones have much faster hardware (and more RAM).
Well I mean take a look at the iPhone 4S, it used to be able to run IOS 5 and now it's up to IOS 8 and it's still pretty fast. These companies need to focus as well on making the newer OS work well with older devices. I mean the HD/HD+ is only 2 years old...
Corkerman said:
the HD/HD+ is only 2 years old...
Click to expand...
Click to collapse
It might be 2 years old but the hardware was never really all that great as it wasn't a top-of-the-line tablet when it came out.
Anyway, that's why I'm hoping 5.0 does something to improve performance, but wouldn't expect miracles from it if anything at all. Android just does better on newer hardware.
_________________________
Looks like cm11 m12 improved responsiveness a noticeable amount and finally too. Still not the same amount newer hardware would cause but a welcome improvement.
Goggles2114 said:
My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.
Click to expand...
Click to collapse
I upgraded my Nexus 7 2013 to 5.0.0_r2, and it is noticeably faster than 4.4.4_r2. With kitkat, art sped up menus and navigation, but not really much else. Lollipop is all art - no dalvik option - and not only are menus and navigation faster, but it seems to speed up apps as well, mainly the Chrome browser. I've been using Lollipop for a couple of weeks now, compiled 5.0.0_r2 with 4.4.4 blobs, and I've been pretty impressed. I just built 5.0.0_r5 from source yesterday with the new 5.0 blobs they released. I haven't had time to install it, but I would imagine the performance to be the same as 5.0.0_r2.
Unfortunately, the Nook HD depends heavily on CM source, and quite frankly, it's a little above my expertise. So I'll just have to wait for verygreen, bokbokan, and leapinlar to give us a lollipop build for the Nook HD and HD+.
cahrens said:
I upgraded my Nexus 7 2013 to 5.0.0_r2, and it is noticeably faster
Click to expand...
Click to collapse
That's great to hear it's indeed faster even though it's on a Nexus! Great job and hopefully the three guys can work some magic into the HD's
Corkerman said:
I mean the HD/HD+ is only 2 years old...
Click to expand...
Click to collapse
In consumer products, that's an eternity.
I've been working with Lollipop builds for a few weeks now, so I have a fairly decent idea of what is involved.
1) sensors.c (touchscreen) requires a minor rewrite.
2) hdmi_audio.c requires a symbol to be dropped (or qcom hardware specified, either/or)
3) selinux rewrites... blehch!
4) hwc, domx ... dunno yet, there's apparently working lollipop compatible source available
5) Changes to build/core/Makefile cause most builds to hang on imgdiff, some reversions are required to get around this.
OK, even with all this, I've only had one build boot enough to get some logs. Ironically it was my very first build.
http://pastebin.com/CNBrENWD
I did end up adding libcorkscrew. Anyway every subsequent build I've done reboots even before being able to get a last_kmsg. I'm at the point now where I believe our kernel will need to be patched to handle gcc 4.8. Changing the build to use gcc 4.7 is doable, but isn't very pretty or nice (too many headers have changed).
Anyone have any other hints or suggestions?
Jon Lee said:
I've been working with Lollipop builds for a few weeks now, so I have a fairly decent idea of what is involved.
1) sensors.c (touchscreen) requires a minor rewrite.
2) hdmi_audio.c requires a symbol to be dropped (or qcom hardware specified, either/or)
3) selinux rewrites... blehch!
4) hwc, domx ... dunno yet, there's apparently working lollipop compatible source available
5) Changes to build/core/Makefile cause most builds to hang on imgdiff, some reversions are required to get around this.
OK, even with all this, I've only had one build boot enough to get some logs. Ironically it was my very first build.
http://pastebin.com/CNBrENWD
I did end up adding libcorkscrew. Anyway every subsequent build I've done reboots even before being able to get a last_kmsg. I'm at the point now where I believe our kernel will need to be patched to handle gcc 4.8. Changing the build to use gcc 4.7 is doable, but isn't very pretty or nice (too many headers have changed).
Anyone have any other hints or suggestions?
Click to expand...
Click to collapse
If it were me, I'd look here http://forum.xda-developers.com/kindle-fire/development/rom-kernel-unofficial-cm12-0-otterx-t2958155 or here http://forum.xda-developers.com/kindle-fire/development/slimpop-otterx-t2957450 for some guidance.
Hashcode is a legend on XDA and he has almost single-handedly kept the very old, TI OMAP 4430 Kindle Fire alive. As for lovejoy777, currently, he has been the most active, hard working dev for that same KF. Hashcode has CM12 working and lovejoy777 has Slimpop.
Since our device is so similar to the KF and Hashcode has contributed to the Nook in the past, looks to be a good resource??? Then again, verygreen could also pop in sometime down the road.
Mike T
It was because of installing CM on a Kindle Fire 2 for a friend that I decided to purchase a Nook (wanted an OMAP).
I checked both threads over but didn't immediately find any lollipop android_device source available.
I was right about the kernel (arm/lib/memset.S?). Only took me a week to figure it out.
I'm not quite sure yet what to make of the second set of logs, but this is where I'm at now.
http://pastebin.com/EXnJpp3L
Jon Lee said:
It was because of installing CM on a Kindle Fire 2 for a friend that I decided to purchase a Nook (wanted an OMAP).
I checked both threads over but didn't immediately find any lollipop android_device source available.
I was right about the kernel (arm/lib/memset.S?). Only took me a week to figure it out.
I'm not quite sure yet what to make of the second set of logs, but this is where I'm at now.
http://pastebin.com/EXnJpp3L
Click to expand...
Click to collapse
One of my first android devices was the 1st gen KF and Hashcode helped make an inexpensive E-reader a very viable android tablet. I would PM Hashcode and/or lovejoy777. Hashcode is usually very busy but he has always been helpful towards other devs, I know he gave some assistance to lovejoy777 with SlimPop.
As for lovejoy777, he's fairly new at development but seems to be very helpful. I think he also may have gotten some help/guidance from MwisBest who built a LP rom for the OMAP 4460 Galaxy Nexus. I mention this because I believe he knows the importance of cooperation among devs. As an aside, while reading his thread I think I read that he was in the process of "cleaning up" his github. So, he could be a good source.
Maybe also PM killersloth. He built quite a few nice roms for our Nooks last year and just recently expressed some interest in trying to get LP on our device. Maybe if you contact him, you guys can make something happen. I'm an old fashioned XDA'er that believes cooperation amongst devs and end users is essential in the community. Every little bit can help.
http://forum.xda-developers.com/showpost.php?p=57255968&postcount=14
Anyway, you seem to be a very sharp guy. I wish you luck in getting LP to the Nook. I wish I could contribute more but I'm more of a file swapper and modder of existing work than a dev. :laugh:
Mike T
Moving to Texas in three days, been hectic around here lol.
I had major issues with hwc, selinux, and our old configs. Hashcode must have plowed through it if its running on otter. I'd check his commit history for some tips.
We needed this for prebuilt boot image before
http://review.cyanogenmod.org/#/c/36813/1
I needed it a few weeks back when attempting to build. They might have brought up their own method since then.
I wish they would have called it SlimPop instead of SlimLP ??
A 5.0 build for hummingbird would be nice. Hopefully it won't be hard to modify an ovation build since all the devel appears to be on ovation.
It might sound ridiculous, but let me and my development team (my close relatives which do have their down work) begin our biggest project yet - porting Touchwiz Camera for AOSP ROMS (or at least every feature which are available on stock Touchwiz). Our goal is simple - bring glorious Touchwiz camera and it's bells and whistles to AOSP ROMs, let it be Lineage or Resurrection Remix, it doesn't matter. We began our development and we will consider using Magisk as an option of getting this to work.
Be aware, that this project might never come to life (trust me, if developers couldn't bring all of our camera features to AOSP, then it's obvious how difficult it is to accomplish this). It might even require to edit the entire AOSP for this to work.
As everyone know, Touchwiz camera is closely related to Touchwiz framework, so as a consequence it closely relies on that code written. AOSP has a completely different CameraHAL for making camera even to work. So, yeah. OnePlus One has something similar already accomplished, so our goal is exactly the same.
All of the development progress will be posted here.
And please note, that this is our hobby job, not a full-time job, so when there is free time to spare, we'll spend it doing this crazy project to work and move forward.
XDA:DevDB Information
Touchwiz Camera porting project to AOSP, Device Specific App for the Samsung Galaxy S5
Contributors
airidosas252
Version Information
Status: Testing
Current Stable Version: TBA
Current Beta Version: TBA
Created 2017-06-30
Last Updated 2017-06-30
Reserved
Reserved1
go for it! good luck
Wait for it. Good luck!
Glad to hear this. Hope you can get it figured out.
I'm so glad to know that! :victory: PATIENCE and HOPE! :good:
Best of luck to ya!
Good luck guys!
Amazing!
Good luck! Hoping you can make it
Good luck guys!!! I have been waiting for such great developers!!! If you'll do it you'll sign a mile Stone, it will be part of the developing history!
I wish you all the best
Thanks for all your great words!
On the flip side, we had many difficulties, starting from bootloop issues to camera stop working even with stock ROM. We are still doing some progress. Logcats and tons of trials and errors helped us out. Moving slowly forward.
Sorry for being off quite recently. Busy working and doing personal stuff.
Progress update:
Nougat is an utter a**. Not only it would be next to impossible to make video recording work (photo capturing is a much easier job), it would take years to make it work. We are searching for some counter measures now. Looks like horrible roadmap is coming up next to our door. We are prepared.
Reserve engineering is as prominent as my need to eat. I know it does not make much sense, but I think you get the idea. Thanks for the support you all.
airidosas252 said:
Thanks for all your great words!
On the flip side, we had many difficulties, starting from bootloop issues to camera stop working even with stock ROM. We are still doing some progress. Logcats and tons of trials and errors helped us out. Moving slowly forward.
Sorry for being off quite recently. Busy working and doing personal stuff.
Click to expand...
Click to collapse
airidosas252 said:
Progress update:
Nougat is an utter a**. Not only it would be next to impossible to make video recording work (photo capturing is a much easier job), it would take years to make it work. We are searching for some counter measures now. Looks like horrible roadmap is coming up next to our door. We are prepared.
Reserve engineering is as prominent as my need to eat. I know it does not make much sense, but I think you get the idea. Thanks for the support you all.
Click to expand...
Click to collapse
Don't give up! "Hope is the last to die"! :good:
Sent from my SM-G900F that scored 73.844 in AnTuTu with No Limits 6.1 ROM. . .
Are you reverse engineering with IDA? there was a developer working on the s6 I think it was who reverse engineered and found many factory variables that were called on during certain camera processes and managed to implement them into the camera wrapper in a "dirty" fashion that wouldn't get approved to be official. It did seem though he improved the camera a lot by using factory light sensing and focusing calls he found from the reverse engineering. Id bet our s5 uses many of those same functions and names, i'll see if I can dig that thread it. It was shared in the lineage 14.1 thread.
Wow this is a amazing info
The bad camera in resurrectionremix is the only part, why I don't use this awesome rom on my S7.
Take your time and hopefully you rock it
omgbossis21 said:
Are you reverse engineering with IDA? there was a developer working on the s6 I think it was who reverse engineered and found many factory variables that were called on during certain camera processes and managed to implement them into the camera wrapper in a "dirty" fashion that wouldn't get approved to be official. It did seem though he improved the camera a lot by using factory light sensing and focusing calls he found from the reverse engineering. Id bet our s5 uses many of those same functions and names, i'll see if I can dig that thread it. It was shared in the lineage 14.1 thread.
Click to expand...
Click to collapse
Yeah, reserve engineering is our only way out. It's not possible to achieve anything in a simple fashion. I would definitely call this project a win if we at least succeed making 1080p60 to work properly, other things like fast focusing and other things might come as well, since the dynamic range on LOS completely sucks. Pictures look dead.
BTW, if what you are saying about S6 is correct, our job might become a lot easier. I believe S6 has a different camera sensor calibration from the get-go, even if the sensor is identical (minus the OIS). If those variables are accessible to us, we might get some incredible results. Of course, with a lot of patience.
And for your own convenience, I won't ask for any donations. Why? My words speak for themselves. I don't want to rob your money. And as plus, I would lose my confidence.
Wishing u and ur team the best of luck with this project fingers crossed