so....... yeah. I've been working on this since MoDaCo dropped the Galaxy Nexus rom dump a few days ago. so far...... the phone vibrates when I hit the power button. It showed a boot screen once, and nothing more..... I do not plan on releasing this rom, well, ever. Unless I can get it to boot fully. If/when that happens, I'll post it up if it does, it'll be full of bugs that I probably won't know how to fix, so, sorry
If anyone else wants to try porting and gets it done before me, more power to ya if not, please pray that I at least get to the lockscreen xP
More info when stuff happens
UPDATE: December 11th, 2011, thus far, it boots, but touchscreen still does not work... Will keep trying.
always wanted to do this,
RESERVED
and,
RESERVED AGAIN
thanks you are also there..
tj_style has successfully booted ics sdk on our fih-fbo & ported the touchscreen drivers..
nothing else is working other than that
here's a video-
www.youtube.com/watch?v=_13ikGCviJg
may you should ask him for help..
i think it would more easy porting sdk than the dump porting as system dump is already coded for a device with completly different hardware..
nitindeck said:
thanks you are also there..
tj_style has successfully booted ics sdk on our fih-fbo & ported the touchscreen drivers..
nothing else is working other than that
here's a video-
www.youtube.com/watch?v=_13ikGCviJg
may you should ask him for help..
i think it would more easy porting sdk than the dump porting as system dump is already coded for a device with completly different hardware..
Click to expand...
Click to collapse
true, although the sdk is missing tons of stuff... so i just thought porting this would be easier haha guess not... i mean ive gotten further than most devs, my device at least powers on i think im gonna try a different kernel. maybe tomorrow.... ill report back
great work man keep going on you will get it
Source Code OUT NOW!!
groups.google.com/group/android-building/browse_thread/thread/4f85d9242667a85f?pli=1
nitindeck said:
Source Code OUT NOW!!
groups.google.com/group/android-building/browse_thread/thread/4f85d9242667a85f?pli=1
Click to expand...
Click to collapse
i know ive been working on it since yesterday
ICS ported to HTC G1
ICS has been ported to HTC G1 the first android phone... so it is just matter of time that we could also get it in our device..
http://forum.xda-developers.com/showthread.php?p=19648827
welp, i got it to boot, and it goes to the lockscreen, but then goes into bootloop... and the touchscreen doesnt work...... ah.. lots of work ahead, but i think the hard parts over ill keep updating!!!
keep going man you will get it
ICS Update by Huawei
Huawei U8860 Honor Official ICS Beta Update Released.....I am not a programmer so this might be a DUH! post...but still came across so shared...maybe the great Devs can shed some light..
Specs:
Chipset Qualcomm MSM8255T Snapdragon
CPU 1.4 GHz Scorpion
GPU Adreno 205
News Update: http://bbs.huaweidevice.com/cn/forum/index.php?app=forum&mod=Detail&act=index&id=32441
ICS Update: http://www.huaweidevice.com/cn/technicaIndex.do?method=gotoProductSupport&productId=3826&tb=0
hope it would be fast port coz' m' totally failed
this would be MUCH easier to port, considering propriotary drivers, and the chipset is nearly exactly the same. im gonna work on this when i get home.
I WILL LET YOU KNOW MY PROGRESS TONIGHT STAY TUNED!!!
^ I am tuned to hear updates from you on ICS ............
c_anuraag said:
Huawei U8860 Honor Official ICS Beta Update Released.....I am not a programmer so this might be a DUH! post...but still came across so shared...maybe the great Devs can shed some light..
Specs:
Chipset Qualcomm MSM8255T Snapdragon
CPU 1.4 GHz Scorpion
GPU Adreno 205
News Update: http://bbs.huaweidevice.com/cn/forum/index.php?app=forum&mod=Detail&act=index&id=32441
ICS Update: http://www.huaweidevice.com/cn/technicaIndex.do?method=gotoProductSupport&productId=3826&tb=0
Click to expand...
Click to collapse
More Data Here.....
https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=shortlog;h=refs/heads/msm-3.0
egarly waiting
c_anuraag said:
More Data Here.....
https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=shortlog;h=refs/heads/msm-3.0
Click to expand...
Click to collapse
kernels... i dont know a thing about em.. xD
this is odd....
you download the .zip, inside it goes like this
.zip
u8860IceCream_B863_Kernel2.6.35
dload
UPDATE.APP
if I'm not mistaken, .app is a Mac OSX file extension.... Anyone know how to decompile or extract it on windows? cuz i'm stuck.
alx294 said:
this is odd....
you download the .zip, inside it goes like this
.zip
u8860IceCream_B863_Kernel2.6.35
dload
UPDATE.APP
if I'm not mistaken, .app is a Mac OSX file extension.... Anyone know how to decompile or extract it on windows? cuz i'm stuck.
Click to expand...
Click to collapse
Bro...i was able to use below to extract Update.App using a Perl Script that I found here:
http://android.modaco.com/topic/311344-repacking-updataapp-was-new-version-of-split-updatapl/
I installed Perl from here : http://www.perl.org/get.html#win32
the command : perl split_updata.pl update.app extracts the files recovery.img and system.img along with other files that I have no clue about. However this does throw lots of CRC errors....
I am not a Perl script expert maybe you can look further into that
Related
Hey the update.zip for nexus's one update is out
here is the link android.clients.google.com/packages/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
and here the prerooted from modaco romraid.com/paul/nexusone/update-nexusone-FRF50-signed.zip
i've started porting. help devs .
Does anyone know how to not flash the new radio cause when i remove the radio.img it always says line 70 installation abonded cause it couldn't find radio.img. any help ? don't worry figured it out
Yeah. I want froyo.
Ohh.. is that real to made 2.2 on Tattoo??
-------------------------------------
Sent via the XDA Tapatalk App
I'm waiting for 2.2 on tattoo.
Developers pls help the Tattoo user.
Thanks in advance.
I'm sorry to say it, but you'll have the same problems as with the 2.1 porting...: the drivers for the camera, sensors, FM radio, etc....
don't tell me xD and what do you believe about the new kernel ? anyway i can always try . and if i don't do it i'm loser .
rwmanos said:
don't tell me xD and what do you believe about the new kernel ? anyway i can always try . and if i don't do it i'm loser .
Click to expand...
Click to collapse
you are brave!
i hope you will be a winner
Guys, I'm confident that we can at least look at the source of 1.6 Tattoo regarding the camera and port it to the new Kernel...I won't stop researching until a decent ROM is created by all of us!
First I will download the source code of the tattoo ROM, then I will build a VM featuring Ubuntu and get all necessary dev-tools to decently start programming that son of a b****!
TheSSJ said:
Guys, I'm confident that we can at least look at the source of 1.6 Tattoo regarding the camera and port it to the new Kernel...I won't stop researching until a decent ROM is created by all of us!
First I will download the source code of the tattoo ROM, then I will build a VM featuring Ubuntu and get all necessary dev-tools to decently start programming that son of a b****!
Click to expand...
Click to collapse
yeahhhh
TheSSJ said:
Guys, I'm confident that we can at least look at the source of 1.6 Tattoo regarding the camera and port it to the new Kernel...I won't stop researching until a decent ROM is created by all of us!
First I will download the source code of the tattoo ROM, then I will build a VM featuring Ubuntu and get all necessary dev-tools to decently start programming that son of a b****!
Click to expand...
Click to collapse
I belive in you!...You can do it!
If there is source code for HTC's 1.6 camera drivers, then it should be easy to port those drivers for 2.1 or 2.2, even if the Android has changed. It's more easy than reverse engineering binary drivers, no?
We just don't have a man who can (or want) to do it.
I have a problem...I wanted to unpack the boot.img file, but unfortunately the structure of this update.zip seems to differ a lot from the normal update packages...this one seems to patch most files, which unfortunately means that there's no way to start this thing up on our Tattoo's, or am I wrong?
TheSSJ said:
I have a problem...I wanted to unpack the boot.img file, but unfortunately the structure of this update.zip seems to differ a lot from the normal update packages...this one seems to patch most files, which unfortunately means that there's no way to start this thing up on our Tattoo's, or am I wrong?
Click to expand...
Click to collapse
If you flash the original Nexus One 2.1 rom, and the nexus one recovery image, then you should be able to flash this...
Yeah, but I don't think the Nexus One recovery image will work on my phone...this smells like bricking the phone hard
use the modaco one. but i can't find a way to not flash the radio.img . i remove it from update-script but the i can't get rid off the syntax error can't figure out why.
I hope you ALL will be winner
rwmanos said:
use the modaco one. but i can't find a way to not flash the radio.img . i remove it from update-script but the i can't get rid off the syntax error can't figure out why.
Click to expand...
Click to collapse
I know this sounds stupid, but did u resign the zip file after deleting radio.img or did u just deleted the img file from the zip and update-script? I'll resign it and then check - anything else I have to pay attention to? I saw again a patchfile for the recovery image, I hope it does not brick my good Amon_RA one...
/Edit: doesn't the update-script normally need an update-binary?
TheSSJ said:
/Edit: doesn't the update-script normally need an update-binary?
Click to expand...
Click to collapse
Not if uses the recovery images built-in syntax...
kiljacken said:
Not if uses the recovery images built-in syntax...
Click to expand...
Click to collapse
thanks for the info...will try to flash the update package when my tattoo is charged..
yeah i did resign . i don't think it's a radio idea to flash it with the radio.img but you know if you just delete resign and flash it won't work cause it is going to look for the file and poof installation aborted . i think i figured out the syntax error .I'll flash when is my tattoo is charged too always out of battery
OK so we hav wifi battery, keys, apps, pretty much the basics, except the camera which i think we need to start working on, currently have have much or less evrthing wrkig to hav this running, if the camera can be worked on we can jus head on just on develping and finalizing the other developments, i think if everyone who is involved in this project, if sucessful should present our work to sony and google, and im sure they will be impressed,.../may even think about employing some of us...sooo lets gett this show on the road,,,....lights CAMERA..Action!!!
***reseRVED FOR ALL LATEST UPDATS ON THIS TOPIC****
ALSO- the link for the fastest and most stable android os, it involves ext2 and linux swap partition....reallyy awesomee...
http://www.neopeek.com/en/forum/Son...o-FRG83---Android-221-Beta-Release-05-11-2010
make sure and follow instructions
and back up data! jus in case
I think first we should solve buttons and charging problem.
sateshboi said:
***reseRVED FOR ALL LATEST UPDATS ON THIS TOPIC****
ALSO- the link for the fastest and most stable android os, it involves ext2 and linux swap partition....reallyy awesomee...
http://www.neopeek.com/en/forum/Son...o-FRG83---Android-221-Beta-Release-05-11-2010
make sure and follow instructions
and back up data! jus in case
Click to expand...
Click to collapse
I have to agree, this android is the fastest. And i've tried quite a few versions..
matejdro said:
I think first we should solve buttons and charging problem.
Click to expand...
Click to collapse
with the sp3dev version charging worked for me...
i think it's a great idea to start on the camera function
Where to START???
ya have to start work on camera
does any one know where to start..
where can we know how to program or how xperia x1 camera driver works??
blackcmos said:
with the sp3dev version charging worked for me...
i think it's a great idea to start on the camera function
Click to expand...
Click to collapse
Yes, but you must have X1 plugged in when launching android. Otherwise it won't be detected.
ok maby it is a stupid question but can anyone explain me why it is so hard to make camera work don take it like i'm underestimateing devs I only want to know what has to be done to make it work i'know that it is a lot of work but i wanna know what kind of work has to be done
P.S. i didn't want to start a new thread because the forum alreday is a bit of a mess
no
jbruneaux (HTC Touch Diamond User) was success launch camera in MSM.
http://www.youtube.com/watch?v=vhz0sPjT2UA
but, it has some problem.
we just wait msm_camera complete build by jbruneaux.
and this forum sn't need new thread.
onece again i'm asking someone smarter than me a person with somkind of knowledge to eyplain me why we can't use Gigabyte GSmart G1317 Rola's drivers for the camera or htc tatoos ones they have almost the same cpu like xperia but with opengl 2 support i'm just curious and keen to know why xD
viruscrazy(jbruneaux) uploaded kernel for Diamond,Blackstone,Raphael with Camera,anybody can mod it to xperia?
http://forum.xda-developers.com/showthread.php?t=883966
matejdro said:
Yes, but you must have X1 plugged in when launching android. Otherwise it won't be detected.
Click to expand...
Click to collapse
yes...after you launched android plugged in,you can unplugge. and plugg in anytme you want
(sorry for my english)
ok, try out the new zImage
http://www.mediafire.com/?ci7wd5qe3scenia
the changes are pushed to git. the camera preview works now. not sure if anything else is working. take care, this version will drain battery power because the video decoder is never powered off. also, the sensor settings are a bit incorrect, and the logcat is filled with errors.. will fix that after the exams
sp3dev said:
ok, try out the new zImage
http://www.mediafire.com/?ci7wd5qe3scenia
the changes are pushed to git. the camera preview works now. not sure if anything else is working. take care, this version will drain battery power because the video decoder is never powered off. also, the sensor settings are a bit incorrect, and the logcat is filled with errors.. will fix that after the exams
Click to expand...
Click to collapse
MAN I LOVEEEEEE YOU XD
Thanks a lottt xD
Big thanks sp3dev
i dont know why device restarting after loading (((what build do u use???
I'll test it, but I need to know what build does this work with. Do I simply replace the zimage on existing build, or do I have to install from the beginning? Thnx!
Simply replace zImage.. I'm afraid it won't work on any current X1 build, you need camera libraries from htc magic 2.2 upgrade.. I'll update you with all the info once camera snapshot and video are fully working
Sp3dev.....you're the men.
Sent from my cyanogenMod6.0 by Neopeek using XDA App
sp3dev said:
Simply replace zImage.. I'm afraid it won't work on any current X1 build, you need camera libraries from htc magic 2.2 upgrade.. I'll update you with all the info once camera snapshot and video are fully working
Click to expand...
Click to collapse
Where to download that Lib ?
Original APP folder from most current leak::
App Folder
Original Framework folder from most current leak::
Framework Folder
Tiny's One_V Port so far:
(Boots to the Bootanimation.)
tiny4579 said:
Here is my logcat, maybe someone can figure it out. I'm taking a break for now:
logcat.txt
My current ROM is below.
sense-ics-inc.zip
Click to expand...
Click to collapse
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTCCN_CHS_1.68.1400.2_Radio_20 .67.30.0831U_3831.15.00.28_M_release_254948_signed .exe
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
HTC_One_V_Ramdisk:
V_Ramdisk Download
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
PureMotive said:
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
Click to expand...
Click to collapse
I thought of that too. But since the DInc is a 'QSD' (1000Mhz Qualcomm Snapdragon) and the Desire HD and the Desire S are 'MSM' (Mobile Station) We can't use their ports to help us :/
Being that the DInc is a qsd8k (8650 to be exact) we'll need to keep an eye out for ports with the same processor.. Oh man I wish the old Desire could get a port of this, lol. We'd have no problem at all..
Tribulattifather said:
Saw nobody was getting this started.
I am currently working on it a bit but I defenitley need help compiling a kernel.
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTC_Europe_1.56.401.1_Radio_20.66.30.0831U_3831
(For the newbies)
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
Kernel Source:
HTC Sensation XE (HTC Europe) - ICS CRC - 3.0.16 kernel source code
Look at the 9th one in the list
I hope that we can get this working for our DInc's.
Click to expand...
Click to collapse
kernel source wont help you at all for the 3.xx kernel from other htc phones, so dont bother
i ported sense 4 to the inc 2 (admittedly a lot easier cuz its msm7x30 which most of the ports are) and will give it a shot on my og inc time permitting
see inc2 port here: http://forum.xda-developers.com/showthread.php?t=1553357
the hacked .35 kernels from your ics aosp roms *should* be good (only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
When you say
nitsuj17 said:
(only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
Click to expand...
Click to collapse
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Tribulattifather said:
When you say
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Click to expand...
Click to collapse
no, you need the zimage from one of the ics aosp inc roms and the extracted ramdisk from the htc one v
Okay. Thank you for clarifying for me.
I'm getting down to business now ^>^
PonsAsinorem said:
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
Click to expand...
Click to collapse
can u tell the link to wildstang83 porting guide thread?
orochi9999 said:
can u tell the link to wildstang83 porting guide thread?
Click to expand...
Click to collapse
★wildstang83's Guide For Basic Porting★
PonsAsinorem said:
★wildstang83's Guide For Basic Porting★
Click to expand...
Click to collapse
thank u!
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
2012oasis said:
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
Click to expand...
Click to collapse
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Tribulattifather said:
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Click to expand...
Click to collapse
can you get a logcat or pm me a ROM link? I'd like to look. No guarantees of success. Sadly the sense devs that could figure it out I think have left the incredible.
Also a working ramdisk still doesn't mean the kernel is good. The kernel may need some changes.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Tribulattifather said:
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Click to expand...
Click to collapse
I'd like to try tonight if I can. I'm hoping that an HWA enabled AOSP ICS kernel works with it.
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Ahh! Excited..
Sent from my HTC Droid Incredible using Tapatalk 2 Beta-5
Tribulattifather said:
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Click to expand...
Click to collapse
I'm actually stabbing in the dark as much as you. Never messed much with roms. I'm more of a troubleshooter rather than a rom/kernel chef. I find tweaks and adapt for my kernels. But I noticed there's no init.inc.rc in that ramdisk. Other than that my mind's dead so I'll have to look tomorrow/this weekend.
I apologize for the delay in posting the port link. You'll have to forgive my internet. But, I assure you that the download is as fast as I can get it with my own server that I use.
EDIT: Port is on the next page --->
Just to make sure that everyone is on the same page - This port is NOT a working port.
It will flash to the DInc and it will install properly but it does not boot. And it is obvious why, lol, because we are still missing the piece to the puzzle to make a working kernel.
I hope that this will give you what you need to get this project I started the thrust in the right direction.
As for my method thus far, I am using the zImage from and AOSP ICS port with Ramdisk parts from the One_V.
Post Script - Today is my third year anniversary being apart of XDA. And I can only hope many more years to come.
CHEERS ALL!
Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
--WiFi (Partially: Signal strength indicator broken. Disable avoiding poor networks in advanced menu)
--GPS
--Internal sdcard
Doesn't work:
--Camera
--3G
--Sound
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
==Boot image gzip for flashing with system image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part07.20120724.img.gz
==System image gzip for flashing with boot image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part08.20120724.img.gz
Remember to always do a backup copy of your device images before flashing new ones.
Great work mate! I assume that if we want to test this later on our tablets, we need to be rooted?
suntechnic said:
Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
Doesn't work:
--Camera
--WiFi
--3G
--GPS
--sdcard fuse mounting
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
Click to expand...
Click to collapse
Woohoo! Look forward to trying this!
This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.
Great work, thanks! I'm glad that there is work going on!
Great news! As I installed ota3 before rooting my device, I hope that there will be some way to get cwm and root working...
Sent from my GT-I9300 using xda premium
Very happy that you're working on a new ROM for our device!!!
And I really hope that someone finds a way to root OTA3 since I was also too dumb to do that before updating.
Cheers!
Wow!! Keep up the good work!!!
can't wait, great work!
Great!
I thought I will be first
According to full_indigo device ID, it is AOSP, not CM? Wow..
I think together we could at last make 3G work as other hw are relatively easy to fix(may be not true for camera as sources again changed). I familiar with Qualcomm RIL framework and can't wait to see how it works with tablet and more opensource hardware module..
I also had to repack boot image to include configuration changes (init* files).
Click to expand...
Click to collapse
lenovo haven't packed init scripts? Oo how it works then? ;/
PS: hello from Russia
obscure.detour said:
This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.
Click to expand...
Click to collapse
Lenovo released ICS open source code but they forgot to release new kernel sources. This prevents me from building bcmdhd driver instead of bcm4329. It looks like JB is oriented for NL80211 wireless interface and not WEXT.
this isnt for the K1 is it
It's for tpt only
When can we see this in a flashable version? Not to sound pushy, I know we have all see the development slow down.
Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?
What is TPT
Not to sound stupid but what is TPT? I have a K1 as well and am wondering if this will work?
TPT= ThinkPad Tablet
Lenovo released ICS open source code but they forgot to release new kernel sources
Click to expand...
Click to collapse
yes I also tried to get more info but for now no response. At last they released external folder of their custom build, which also contains alsa-audio, as I seen in cm9 device tree, it should fix audio with ease(maybe after patch as sources again changed in JB).
It looks like JB is oriented for NL80211 wireless interface and not WEXT.
Click to expand...
Click to collapse
but WEXT is there isn't it?
Anyway, congrats on working wifi.
Has anyone else got this up and running? I tried uninstalling CWM and reflashing part 7 and 8 but still no luck.
mr toasty said:
Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?
Click to expand...
Click to collapse
Some of existing software probably blocks normal startup. It is always advised to clean dalvik-cache and user data (backup first). It's up to you.
Right after Lenovo logo you should see 'Android: Optimizing applications' or something similar.
Hello there, it's time to get this rolling somewhere.
This is a Development-Thread. Please don't post if you aren't a developer.
What this IS
This is a Development thread, a platform for developers to discuss the development of CyanogenMod for the G925F. It's made so that we can get this working, fix up the problems - because there will be severe ones - and achieve a working official Rom at some point.
At the moment it's @OldDroid and me with help, but it would be awesome if interested devs would join in so that we can make this a team effort.
In short, it's a Dev-Thread in a dev section.
Right now it doesn't work and I'm not sure that it will work.
What this IS NOT
This is NOT a working Rom. Not even close. I can only link you to the kernel repo and soon to device and vendor, as they are almost completed for a first try.
And yes, there is no download link for the Rom. Because there isn't anything you could download yet.
This is also NOT intended as a Q&A thread. Please don't ask if your variant will be supported, I will respond by trolling. Firstand only priority is to get this running, then we'll talk about variants.
And ETA is an evil word with no meaning here. I work slowly, deal with it
Where are we currently?
Much further than a day ago
Thanks to @OldDroid, we've teamed up
All the links you want (minus the download link :angel
device: (soon, almost complete)
https://gitlab.com/mythos234/device_samsung_zeroltexx
vendor:
https://gitlab.com/mythos234/vendor_samsung_zerolte
kernel:
https://gitlab.com/mythos234/zerolte-kernel-CM
Once available, buggy alpha builds will be posted here
///
vendor and device will soon be pushed to my github
Reserved
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
vendor is setup
OldDroid said:
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
Click to expand...
Click to collapse
Welcome aboard then
vendor is finally setup and good to go!
https://github.com/mythos234/vendor_samsung_zerolte
It's apparently not without some minor casualties, but we got it. Huge thanks to @RaymanFX, he's helping me, since I'm not that much into CM building yet and I'm also basing this project on his CM for the N910C, which's 5433 is darn similar to our 7420, so we got a pretty good base to begin with.
add me as participant to the repos ^^
https://github.com/OldDroid
OldDroid said:
add me as participant to the repos ^^
https://github.com/OldDroid
Click to expand...
Click to collapse
Done for all the 3 of them
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
mythos234 said:
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
Click to expand...
Click to collapse
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
nasko_spasko said:
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
Click to expand...
Click to collapse
I'm currently building the Rom with completely removed Bluetooth support
First Build is compiled and ready for a test.. But I can't install the zip. This would be hillarious if it wasn't so annoying
mythos234 said:
Besides I said it can't be installed Hard to test something you can't even install
Click to expand...
Click to collapse
I think that there was a mistake in the partition sizes.. /system was declared as 4.1GB, but it's only 3.6GB. Recompiling with a new value, should be able to flash it then
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Aircondition said:
Good luck develop without documentation for exynos chipset.
Click to expand...
Click to collapse
The lack of drivers makes this a fun exercise almost Where's be the challenge if everything was easy...?
Aircondition said:
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Click to expand...
Click to collapse
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
mythos234 said:
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
Click to expand...
Click to collapse
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
lch920619x said:
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
As a base to know how to do it, obviously we can't just use drivers for a different chipset
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
mythos234 said:
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
Click to expand...
Click to collapse
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
-Mr. X- said:
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
Click to expand...
Click to collapse
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
mythos234 said:
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
Click to expand...
Click to collapse
I would personally flash an Engineering boot loader while doing this, to ensure version checking is not the issue.