I've been trying to port over ICS from DHD but no success(ROM doesn't boot, stuck at HTC splash screen)
Since I'm a noob to ROM porting any help would be appreciated.
I followed a simple guide which told me to replace certain files in the boot.img and system folder along with a couple of files more.
I used the ICS rom of DHD and MIUI ICS rom for IncS.
cooljais said:
I've been trying to port over ICS from DHD but no success(ROM doesn't boot, stuck at HTC splash screen)
Since I'm a noob to ROM porting any help would be appreciated.
I followed a simple guide which told me to replace certain files in the boot.img and system folder along with a couple of files more.
I used the ICS rom of DHD and MIUI ICS rom for IncS.
Click to expand...
Click to collapse
a suggestion for you...try the cm7 rom instead of miui ics build.
thanks for your effort. i will also dig about it but after my last exam. i request everyone who could contribute....its for our phone.
keep trying bro.
If it is simple enough I could give it a try, any moderate to advanced programming I wouldnt have a clue
I have been working on this over the last couple of days and so far my port has touchscreen, audio, RIL, wifi, 2D HW acceleration, notification LED and proxy sensor working (pretty much the same as the DHD port I think). Last I tried the microphone wasn't working for calls but it should be fixed in my new build.
I will post it up in the next couple of days once it's ready to be used. I've been busy with other things so haven't had a chance, plus I don't have access to the developer section yet.
st.matt said:
I have been working on this over the last couple of days and so far my port has touchscreen, audio, RIL, wifi, 2D HW acceleration, notification LED and proxy sensor working (pretty much the same as the DHD port I think). Last I tried the microphone wasn't working for calls but it should be fixed in my new build.
I will post it up in the next couple of days once it's ready to be used. I've been busy with other things so haven't had a chance, plus I don't have access to the developer section yet.
Click to expand...
Click to collapse
good job. if you need any help just let us know. i will try to look into it today night positively.
Anyone got any guides/tutorials kinda stuff for this?
Nopes, no tuts as such... just small guides....
Any links??
Keen to see how much of your port is working so far as well
EDIT: just tried it myself using a guide in other thread. used the DHD beta 3 and vivo latest CM7 nightly and is stuck at htc splashscreen
EDIT2: didnt sign the rom before, lets try that again...
EDIT3: still stuck on splashscreen
I will post my port up later tonight. I had a chance to do a bit of work on it and it's pretty good right now but the market is broken for some reason.
Once I get that working (and hopefully bluetooth as that shouldn't be hard) then I will upload it.
st.matt said:
I will post my port up later tonight. I had a chance to do a bit of work on it and it's pretty good right now but the market is broken for some reason.
Once I get that working (and hopefully bluetooth as that shouldn't be hard) then I will upload it.
Click to expand...
Click to collapse
Sounds good, what ROMs did you use to port it?
st.matt said:
I will post my port up later tonight. I had a chance to do a bit of work on it and it's pretty good right now but the market is broken for some reason.
Once I get that working (and hopefully bluetooth as that shouldn't be hard) then I will upload it.
Click to expand...
Click to collapse
Looks like a nice birthday gift... ;D
Unfortunately I wasn't able to get market working.. but anyway here is the first Alpha.
It is based on a combination of the Desire HD build and using the kernel by TwistedUmbrella. I have a device setup to work with TwistedUmbrella's ICS tree but I don't know if it will 100% build successfully at this stage (takes forever to build on my 5 year old computer..). All credits go to the DHD guys as they have done basically everything, I've just made it work (or at least, most of it) on the vivo.
Working:
- Hardware 2D/3D Hacks
- Touchscreen
- Bluetooth
- Wifi (not tethering)
- RIL
- Data
- Sound
- Sensors
- Rotation
- Status LED
Not Working:
- Hardware video acceleration
- Tethering
- UMS (use adb instead)
- USB tethering
- Camera
- Google account (so Gmail, Market all not working)
The account error seems to be something to do with xt_qtaguid.. here is the log info:
Code:
I/qtaguid ( 3029): Failed write_ctrl(u -1) res=-1 errno=9
I/qtaguid ( 3029): Untagging socket -1 failed errno=-9
I/GLSUser ( 3029): GLS error: NetworkError
Might be a problem with the kernel, but I'm not really sure. Any help would be nice, I've spent about 5 hours on this and gotten nowhere.
Link: http://www.multiupload.com/Z4JKSC1JK2
Please don't post bugs reports just yet. This is the first alpha, it's not really a daily driver and I know that there are bugs. Post fixes instead.
Sounds awesome Matt! what are you using to break down and build the rom??
Will give it a go in the morning and post any other feedback
Nice work you got slot further than I did! I will see if I can contribute anything to your build once I have it installed.
The Desire S version is pretty good, and the hardware is almost identical to the Inc S, maybe that would make for a better base?
Sent from my HTC Incredible S using xda premium
l0st.prophet said:
Nice work you got slot further than I did! I will see if I can contribute anything to your build once I have it installed.
The Desire S version is pretty good, and the hardware is almost identical to the Inc S, maybe that would make for a better base?
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
That's probably not a bad idea. I will see if I have time tonight to try and see if I can get market working by using some of the desire s stuff.. or maybe someone else could try as well.
For anyone that gives it a go, just keep in mind that the button backlight levels are in framework-res.apk, and will need to be recompiled from source or decompiled and edited to get the levels right.
P1n3apqlExpr3ss said:
Sounds awesome Matt! what are you using to break down and build the rom??
Will give it a go in the morning and post any other feedback
Click to expand...
Click to collapse
Well so I have checked out TwistedUmbrella's ICS tree and 7x30 kernel, and have made a vivo config for both. I've then used the prebuilt DHD ICS rom and taken out the DHD stuff and put in stuff from the vivo Miui.us rom. Then I've just gone through and fixed the boot ramdisk, built the kernel and put it together for the boot image.
In future I will try building from source, but as I said it takes a very long time for me.
st.matt said:
Well so I have checked out TwistedUmbrella's ICS tree and 7x30 kernel, and have made a vivo config for both. I've then used the prebuilt DHD ICS rom and taken out the DHD stuff and put in stuff from the vivo Miui.us rom. Then I've just gone through and fixed the boot ramdisk, built the kernel and put it together for the boot image.
In future I will try building from source, but as I said it takes a very long time for me.
Click to expand...
Click to collapse
This sounds WAY over my head, all I tried was unzipping CM nightly 146 and the DHD build and changing files, rezipping and signing it. No wonder I got stuck at the HTC splashscreen...
Keep up the good work
st.matt said:
Unfortunately I wasn't able to get market working.. but anyway here is the first Alpha.
It is based on a combination of the Desire HD build and using the kernel by TwistedUmbrella. I have a device setup to work with TwistedUmbrella's ICS tree but I don't know if it will 100% build successfully at this stage (takes forever to build on my 5 year old computer..). All credits go to the DHD guys as they have done basically everything, I've just made it work (or at least, most of it) on the vivo.
Working:
- Hardware 2D/3D Hacks
- Touchscreen
- Bluetooth
- Wifi (not tethering)
- RIL
- Data
- Sound
- Sensors
- Rotation
- Status LED
Not Working:
- Hardware video acceleration
- Tethering
- UMS (use adb instead)
- USB tethering
- Camera
- Google account (so Gmail, Market all not working)
The account error seems to be something to do with xt_qtaguid.. here is the log info:
Code:
I/qtaguid ( 3029): Failed write_ctrl(u -1) res=-1 errno=9
I/qtaguid ( 3029): Untagging socket -1 failed errno=-9
I/GLSUser ( 3029): GLS error: NetworkError
Might be a problem with the kernel, but I'm not really sure. Any help would be nice, I've spent about 5 hours on this and gotten nowhere.
Link: http://dl.dropbox.com/u/52030869/vivo_ics.zip
Please don't post bugs reports just yet. This is the first alpha, it's not really a daily driver and I know that there are bugs. Post fixes instead.
Click to expand...
Click to collapse
great job bro! just need the camera and gmail account. rest everything is perfect ! i will try it today and see. thanks for your efforts
Download link not working... Too much traffic :/
Sent from my Incredible S using XDA App
Splux said:
Download link not working... Too much traffic :/
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
yes its not working. can we get other links please?
Yeah sorry I didn't realise dropbox imposed download limits. Here is another download link: http://www.multiupload.com/Z4JKSC1JK2
I think I may have fixed Google accounts though, so there might be another download in another 30 minutes or so.
Related
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 ?
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://www.multiupload.com/XT9QPPQYF1 thanks xploited for uploading
md5: 670068584eb94bf1d660c0450815ad0d
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Not sure how the dev team would react to this ..we do not want any bricked phones because of this ..there maybe some experimental dangerous code in there in those sources as of now ..not sure though
Hmm... figured since I spent quite awhile getting a build set up, it might be worth sharing. I am happy to take down if it is inappropriate.
Well I am not the best person to answer that ...but yeah thanks for your work.
Eh, I wouldn't be mad about it, but I think it needs more caution. I would just wait. As you say, it kindof screwed with a lot and wasn't very usable, so why flash it? Maybe ok for someone who wants to look at the code, but I wouldn't flash it.
Awesome news man. Thanks for being a lab rat and giving us an update.
Sent from my MB860 using xda premium
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
samcripp said:
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
Click to expand...
Click to collapse
and I guess you guys deserve a Xmas break now ...
It's nice to see that! Thanks for your hard work.
I'm looking forward to the CM9
Thank you for this.
!
Anyways, Just out of curiosity... where can you find the official Atrix Dev team's CM9?
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
I always forget what kang means.
Sent from my MB860 using XDA App
wrldsuksgo2mars said:
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://goo.gl/39NnA
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Click to expand...
Click to collapse
Thinks for your works,
Come from Chinese thinks!
i shall say this.. if this is behind where the dev team actually is...things are looking good! and btw.. i believe fruitcaker maker works. installed and is now creating;]
edit: yep. it does.
Thanks man very very good work android congratulations for share work whith comunity
Sent from my MB860 using xda premium
it looks very nice but id needs a bit more work to be a experimental daily driver.
ps: to solve the corrupt backup problem just copy the files to your computer before flashing and copy to your phone before restoring.
good luck!
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
try the one on this link
http://rootzwiki.com/topic/11854-romcm9-encounterics-x-beta-2-with-working-radio-401/
good luck!
---------- Post added at 07:52 AM ---------- Previous post was at 07:47 AM ----------
ilya11g said:
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
Click to expand...
Click to collapse
try the one on this link
http://rootzwiki.com/topic/11854-rom...ing-radio-401/
good luck!
For a preview build it looks pretty nice. Surprisingly stable for what it is. Definitely keeping an eye on this, especially since the code is out there to make DIY kangs with.
samcripp said:
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
Click to expand...
Click to collapse
Random SamCripp memory....
"We're rapping them, we're rapping them!!!"
Sorry, guess you had to be there.... aahhh memories... nevermind, sorry for the off topic post.
Thanks though for the effort of getting this ported btw.
I've started porting CyanogenMod 9 to the Galaxy Tab 7.7. Do not flash this unless you know how to backup your data and especially unless you know how to get back to stock. If you don't already know how to do this, you might want to familiarize yourself with the process now, while the developers try to stablize CM9. I don't have time to help people unbrick their devices, and will not take responsibility for any user bricking their device, you flash this at your own risk.
If you are a developer interested in helping out with the porting effort, please PM me.
Known Issues
HDMI dongle doesn't work
Some USB keyboards aren't working
I815: CDMA and LTE isn't enabled
I815: GPS doesn't work
I815: Autobrightness is broken
Download
Google apps can be found at http://goo.im/gapps
I815 (August 15, 2012): http://goo.im/devs/ohanar/i815/cyanogenmod/cm-9-20120815-NIGHTLY-i815.zip
P6800 (August 15, 2012): http://goo.im/devs/ohanar/p6800/cyanogenmod/cm-9-20120815-NIGHTLY-p6800.zip
P6810 (August 15, 2012): http://goo.im/devs/ohanar/p6810/cyanogenmod/cm-9-20120815-NIGHTLY-p6810.zip
Old
P6810 (DP1, April 4, 2012): http://goo.gl/ANRQx (md5: 2be30aaa4aadcd3065239e16f0ca5247)
P6800 (DP1, April 5, 2012): http://goo.gl/CrwCQ (md5: f333f6aca81e1fb0f08244358e492813)
Flash
Flash from ClockworkMod Recovery, make sure to wipe data/factory reset. No whining if it eats your homework.
Build Instructions
Setup a standard CyanogenMod 9 build environment (there are plenty of tutorials on the web already on how to do this). Then
Add add the following entries to your local manifest
Code:
<project path="device/samsung/XXX"
name="ohanar/android_device_samsung_XXX"
revision="ics"
remote="github" />
<project path="device/samsung/smdk4210-tab"
name="ohanar/android_device_samsung_smdk4210-tab"
revision="ics"
remote="github" />
<project path="kernel/samsung/smdk4210-tab"
name="ohanar/android_kernel_samsung_smdk4210-tab"
revision="ics"
remote="github" />
where you replace XXX with your device (i815, p6200, p6210, p6800, p6810, or t869).
Make sure that your device is running the newest build of CyanogenMod 9 or stock ICS if your device has it.
Make sure your device is plugged in and has debugging enabled.
Run the extract-files script from your particular device tree.
Run vendor/cm/get-prebuilts
Your sources are now ready, to build run
Code:
$ . build/envsetup.sh # this sets up the build environment
$ lunch cm_XXX-userdebug # this selects your device
$ mka bacon # this builds CM
Changelog
08/08/2012
Hopefully remaining wifi issues fixed (wifi hotfix shouldn't be needed anymore)
Wifi tethering enabled (no clue if it works)
08/03/2012
LPM fixed (can now charge while off)
Camera force closes fixed
7/19/2012
P68x0: Autobrightness fixed
Bluetooth fixed (thanks to lowtraxx for pointing out where the issue was)
I815: LTE Modem's massive power drain fixed
7/15/2012
Wifi! -- for real real, not for play play
P6800: SIM Toolkit Support
Hardware-Accelerated Video (Regression in 7/10/2012)
ASOP Charging mode (still not really working)
7/10/2012
smdk4210-tab kernel
I815 build
vibration (regression in Alpha 2)
3g data on P6800 (regression in Alpha 2)
Camera (both front and back)
Regression: Hardware-accelated video (this also means no previews in the Camera)
Regression: LPM
Alpha 2
smdk4210 kernel (common kernel used in the CM9 ports for the i9100, i777, n7000, p6200, p6210, p6800, and p6810)
USB gadget support
Hardware-accelerated video
Rear facing camera (only stills for now)
Better auto brightness (values still need to be tuned)
LPM (charge while off)
Probably other stuff (been a long time since last update)
Regression: Vibrator no longer works, we now get a beep instead
Alpha 1
Upgrade wifi driver to compat-wireless-3.4-rc3-1
GPS hopefully fixed (thanks to Alan Orth)
Data Usage fixed (thanks to Alan Orth + Galaxy Tab 10.1 devs)
DP3.1
Wifi fix that sometimes works
DP3
Torch App (thanks to Alan Orth)
Fixed reboot download
Wifi partially works
Other random bugs caused by building with gcc 4.6 (now using the recommended 4.4)
DP2.1
3G/GSM fix (thanks to poisike)
DP2
Audio works!
DP1.1
Partial fix for autobrightness (gets brighter, doesn't get darker)
Phone like interface is gone
P6800: added GSM libraries, and basic 3g configuration
Credits
aorth -- set up the device tree for the GT-6200 (Tab Plus 3g), has been a great collaborator
poisike -- provided fix for 3g/gsm
teamhacksung -- set up the galaxys2 device tree, which was the basis for my tree
Nice! Hope more developers will join and sync with 6800
Sent from my GT-P6800 using XDA Premium HD app
locerra said:
Hi,
I've started working on porting CM9 to my P6810, and figured I would post here in case there were any other devs interested in assisting me, or working on a P6800 version.
Currently I have gotten to a lockscreen, but that is about it, most hardware still needs to be properly configured.
The sources:
https://github.com/ohanar/android_device_samsung_p6810
https://github.com/ohanar/android_frameworks_base
Click to expand...
Click to collapse
I'm interested in working on a P6800 version. I sent you a PM.
poisike said:
I'm interested in working on a P6800 version. I sent you a PM.
Click to expand...
Click to collapse
I have started on this, as well. Am beginning with the Note port right now. Gotten about as far as you. Please PM me, and we can hopefully collaborate.
Steve
Uh this sounds great!
Count me in for testing, don't have dev abilities.
sk806 said:
I have started on this, as well.
Click to expand...
Click to collapse
Do you have a git repo somewhere? I wouldn't mind looking through what you've done so far.
hurray!
Count me in for testing, don't have dev abilities.
waiting for first booting CM9
Wow great news! I really cant contribute anything aside from ROM testing on a regular basis as long as it does not increase any flash counters
great
great!! i may help,no rommaking experience but programming skills in java, c and android. pm meif want some help.
locerra said:
Hi,
I've started working on porting CM9 to my P6810, and figured I would post here in case there were any other devs interested in assisting me, or working on a P6800 version.
Currently I have gotten to a lockscreen, but that is about it, most hardware still needs to be properly configured.
The sources:
https://github.com/ohanar/android_device_samsung_p6810
https://github.com/ohanar/android_frameworks_base
Click to expand...
Click to collapse
Oh get it soon brothers, This TouchWiz is killing me.... I hate it....
locerra said:
Do you have a git repo somewhere? I wouldn't mind looking through what you've done so far.
Click to expand...
Click to collapse
I don't. Working a bit more on it, then I'll post and send you a link to the ROM...
sk806 said:
I don't. Working a bit more on it, then I'll post and send you a link to the ROM...
Click to expand...
Click to collapse
Ok, well let me know when you have something. In the meantime, I'm seperating out my repo into two: common stuff and P6810 specific ones. I'm rebuilding to make sure that I didn't break anything, but once that is done it should be easier to share work (assuming that all the things that I put in the common repo are indeed common ).
just having a peek at your github, (I have Gt-P6200) there's a typo in ..android_device_samsung_c210-common / c210_base.mk
AUDIO_PACKAGES is misspelled I believe.
nothing huge.
i've got a builbox and can host the nightlies if you want, we already do it for the nook and touchpad (unofficial) builds.
pm me if you're interested.
Its so nice to see the 6810 getting some love. When I first got it and came to the developers forum I was surprised that all the ROMS said 6800 only. I also will gladly help with testing.
I'm also glad to see the P6810 get some attention, especially when it's CM9/ICS.
Happy to help out with testing when you guys are ready
Ill echo the above also - awesome
chrisrotolo said:
just having a peek at your github, (I have Gt-P6200) there's a typo in ..android_device_samsung_c210-common / c210_base.mk
AUDIO_PACKAGES is misspelled I believe.
nothing huge.
Click to expand...
Click to collapse
I'm curious as to how similar the tab 7+ and 7.7 really are. If they are close enough (which my guess is that they are), then that repo could serve for both (although probably not in the present state). Are you thinking of working on CM9 for your tab?
dude this is awesome! i'll take a peek when i get the time and help out if i can.
keep up the good work!
I always say that xda is the place of wonders. Waiting patiently and deeply appreciate it!
I have put this project on hold for now. I flashed latest Austrian ICS build to my device and continue using it as my Kindle reader on my travels. IF somone manages to fix the two issues with kernel, send me a message and I'll continue working with the repository. But for now I'm not thinking nor touching the subject before Easter. Thank you for participating for now
I've started porting Ubuntu-touch dev-preview to the Galaxy Tab 7.7 (3g). If you do not understand it already, you flash this at your own risk. There is now also a Ubuntu-touch specific device page here: https://wiki.ubuntu.com/Touch/Devices/p6800. I'll try to keep this thread and the Ubuntu devices page as close to each other as possible.
Big thanks to Daniel_hk for helping with boot.img Now It can be booted, but the screen is still black
Also, without working wifi and display, the preview is basically unusable... Next steps should be these:
1. Get wifi drivers working.
2. Get display drivers working.
Code:
[email protected]:/# uname -a
Linux localhost 3.0.15-CM-g1dc3074 #2 SMP PREEMPT Wed Mar 13 00:43:37 EET 2013 armv7l armv7l armv7l GNU/Linux
Repositories:
Latest release tagged with: "v0.3", not tested!
https://github.com/dun1982/android_device_samsung_p6800
https://github.com/dun1982/android_kernel_samsung_p6800
Download
cm-10.1-20130312-UNOFFICIAL-p6800.zip
Daily Ubuntu image: http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
Installation
Install CWM 6.0.2.8
Wipe data/factory reset
Wipe cache partition
Flash cm-10.1-20130312-UNOFFICIAL-p6800.zip to device
Flash quantal-preinstalled-phablet-armhf.zip to device
Reboot
Starting to use
Then it gets interesting (Black sreen for now now Run the following commands in your desktop system:
Code:
adb root
adb shell
ubuntu_chroot shell
You should have now root access inside your tabled. Continue with this wiki next
What works
Ubuntu-touch dev-preview is flashable.
It boots!
Known Issues
Kernel is based to the CyanogenMod/android_kernel_samsung_smdk4210, but it is a mess. So forked it, took code here and there (mostly from locerra's JB build).
Kernel is based 3.0.15 and no newer one available (yet).
Most of the drivers in kernel had to be turned off, because build was not succeeding...
bluetooth: Doesn't work
audio: Dock audio doesn't work.
hwcomposer: HDMI dongle doesn't work.
wifi: Doesn't work.
camera: Doesn't work.
.. and lot of kernel level bugs for sure.
Displaydrivers are not working (yet).
Release notes
Version 0.2 (13.03.2013) - Now it boots, see release notes
Version 0.1 (07.03.2013) - Intial release, nothing works
Credits
BIG THANKS to daniel_hk for solving the boot.img problem for me.
Anyone who has worked previously with the device/kernel source.
locerra (for getting CM10.1 to flashable state).
wowww!!! thank you !test now:victory::victory:
Placeholder for future.
Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
Not 6810 versión?
AUs
el_campi said:
Not 6810 versión?
AUs
Click to expand...
Click to collapse
I cannot test it for anything else. The kernel sources are from CM10.1 that was in use from locerra, so in theory it should work with i815 and with p6810 as well. But I cannot give you any guarantees...
And also before I get this build to even start with my device, I do not think that sharing image would help anyone. But if you are a developer, I would like to talk with you on issues that I might have missed or done wrong. So contact me
Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
any update?
Sent from my GT-P6800 using xda premium
Not much. The generated image is missing /data/ubuntu completely and that is the reason why the image does not boot. I got also flu and fewer, so I have had not that much time after the weekend to look on the issues on that.
I'm also waiting if I get any answers from Ubuntu touch emailing list regarding the problem and where to look for answers, but my quess is that it has something to do with the devices fstab file...
Good news everyone!
Just got a very good answer the problem I had with the /data/ubuntu-folder missing from the image. There was no image provided for the actual Ubuntu at all by the build-process...
When I get home from work, I'll try to find time to look into the build process if I can include the actual Ubuntu image to the ready made image and then release it after I get my device to boot. But it seems that I got the right nudge forward for this now :highfive:
Hmpf, still not booting. Now the /data/ubuntu logs are unmodified, which would point towards kernel or fstab-issue (ie. /data/ubuntu is never used...).
Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
Good job :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:
Sent from my GT-p6800 using xda premium
Doh... still not working... Any ideas anyone?
Ok, new version build from different repositories (thx, danile_hk for tip).
I'll test the new image this evening when I get back to home, and I have my fingers crossed that I can get the device to boot up and even display something useful. After that I can start looking for ubuntu developemnt
New version did not work, but then Daniel_hk gave me working boot.img. So now I need to find out what the heck is wrong with my repository and fix it so that I can get working boot.img from start and also the device configuration has issues. Both repositories are currently out of sync I'm afraid
dun1982 said:
New version did not work, but then Daniel_hk gave me working boot.img. So now I need to find out what the heck is wrong with my repository and fix it so that I can get working boot.img from start and also the device configuration has issues. Both repositories are currently out of sync I'm afraid
Click to expand...
Click to collapse
Also, without working wifi and display, the preview is basically unusable... Next steps should be these:
1. Get wifi drivers working.
2. Get display drivers working.
It seems that I hit the wall (again) with the mentioned big issues.
For now, I keep some sabbatical from Ubuntu Touch things (ie. I flashed ICS Austria to my device) and use it as my Kindle reader again.
If by miracle I get more info regarding how to get the Kernel working with Ubuntu Touch, then by allmeans I continue working with this project. So far it just seems that making a working image, is out of my hands currently.
At least you had a go. Thanks for your efforts, and hope you might have another crack at it later on.
I'm feeling a little bit that way right now too, and put my ICS kernel on the back burner. I think I'm trying to multitask a little too much at times....
Yep, a break is what you need, maybe some clarity will come after you've had a chance to recharge.
Sent from my GT-I9300 using xda premium
It's very nice to see you took up the big responsibility to make this superb device to be usable again! it has great specs, really. KUDOS bro!!
Any update on this development?
ZhenMing said:
Any update on this development?
Click to expand...
Click to collapse
Not much, I have had no interest to spend time with this topic because I have been very busy IRL. After I get my new house renovated fully and get my job tasks done, I wont be spending much time with this project. Feel free to use any sources provided in this thread to further advance the subject.
But this wont go forward that much, if the GT-P6800 wont get official CM10.1 update...
It works?
As we now the fingerprint in new kernel work but not in ROM because the framework and binarys is incompitable for cyanogenmod ICS. So some months ago I started to port fingerprint in my free time and finaly I stoped to GfxEngine.apk error "Incorectly signed". At this point I undersood that there need to get correct signature or hack this verification down, and yes I made it yesterday(20.08.2013) . So now I had hacked GfxEngine.apk, FingerprintSensor.apk and incomplete framework for ICS from GB. (22.09.2013) We had gained fingerprint support on lockscreen whit some bugs need cleenup and bug reports
All sources and binarys for fp here: https://github.com/firecode95/
To clear all doubt what works for now:
Fingerprint sensor navigation
Fingerprint database managment
Fingerprint lockscreen set up
Fingerprint lockscreen finaly
Known bugs:
after instaling rom first boot makes fc on authentech apk then need to wait ~15 sec and press ok, and if framework is went down need reboot phone
if fp is enabled then after turing on phone need to relock phone with power button to activate fingerprint sensor
fingerprint lock setup setings section gives fc after setup and can't change lock methode anymore
Flashing:
Went from older build, just flash new build on top of it.
Went from other rom? Make full wipe and flash this then.
Fingerprint ROM's are located there, so want to test download latest build and if catch bug report it on this therad whit reproduction steps and logcat. Flash it on clean phone (full wipe).
Want to experiment and maybe make a bugfix for something build it yourself. Initialize android build enviroment(search in net just too many guides already) use official Cyanogenmod ICS source and add the local manifest download there, sync repo and type standart android building comands
Update (22.08.2013)
The finger lock now sets up right just settings apk crashes imediately after setup, and phone goes in soft reboot loop after locking phone because lock screen isn't finished and the new logcat, local_manifest add too + updated github.
Update (22.09.2013)
Today I am proud to say that fingerprint finaly works in cm-9 it's whit some bugs and doesn't show mesages about good or bad swipe in unlock screen but it works, need to swipe finger for 3 - 5 times(if that finger is in database it will work) the source will be available tomorow on my github acount.
Update (4.10.2013)
So I tryed to port it for JB but there is incompitability issues for GfxEngine.apk so need add fix in apk source but there comes dificult part, firs need reverse it to source (.java files) but its quiet difficult, I had decompiled many classes but some classes don't exactly 6 classes in booth apk's (fingerprintsensor.apk and GfxEngine.apk), I will try use different apk's but I think that it will not help and if someone want to help the JB (cm10.1) unfinished source will be available after 1 - 2 days in my github.
In attachment is some pics of what I got
The goal is to make ICS with fingerprint support and leater got port this to JB
And please do not ask or spam whit request when this will be merged in official Olympus kernel ICS rom because this is just a sketch and I am only kernel tester for new kernel. This thread is opened to got solution and every help will be higly evaluated.
Thanks go to @BravoMotorola for providing authentech SDK.
It's a great new! But i have a doubt, why use the frameworks from GB if we have the ones for ICS in AtrICS and works good?
douglasroos said:
It's a great new! But i have a doubt, why use the frameworks from GB if we have the ones for ICS in AtrICS and works good?
Click to expand...
Click to collapse
I will give you example. If we took the Settings.apk from AtrICS (leaked rom) the settings apk will crashes in 99,9% because they are system apk and is build with moto stuff not CM and will try to find things that doesn't exist in cm or if exist is diffrent resulting crash and and this is reason why the app hacking was already done.
Wrong Signature problem...
Thx. for your firecode, I know there were sample codes for GB laying on Atrix-Dev-Team, just too lazy to port it to cm-10.1
Anyway, you are saying 'invalid signature', i might help with this
Did you grab all the proprietaries directly from the leaked img??? i.e.
#fingerprint
bin/am2server
etc/am2server.pubkey
lib/libAuthUDMDrv_1750A100.so
lib/libam2app.so
lib/libam2server.so
app/GfxEngine.apk
app/FingerprintSensor.apk
The invalid signature will RING if you have a missigned GfxEngine.apk
E & M have extracted those proprietaries and made them available in Vendor git, BUT there are RESIGNED with testkey.pk8 for new ICS & JB platform
So you have to use the ORIGINAL GfxEngine.apk from the ORIGINAL leaked ICS img signed with Moto key
Hope you can make a JB port as well, Thx. in advance
Zn7mkUKzN1r8aCIV said:
So you have to use the ORIGINAL GfxEngine.apk from the ORIGINAL leaked ICS img signed with Moto key
Click to expand...
Click to collapse
I already used original moto GfxEngine.apk but it gived same error, the itself worked just whe thye used gfxservice class they crashed, and its no more actual because signature check is reversed now, if wrong signature apk goes right if right signature apk crashes . I think this comes up because in leak rom is apk named MotoSignatureApp.apk
Great work.
I hope you don't mind: https://github.com/CyanogenMod-Atri...mmit/fe050430b040e7cef6338433c543ae2e20fffff0
epinter said:
Great work.
I hope you don't mind: https://github.com/CyanogenMod-Atri...mmit/fe050430b040e7cef6338433c543ae2e20fffff0
Click to expand...
Click to collapse
I've tested AtrICS with new kernel, Fingerprint Sensor works good.
But I am not going to ask a dumb question like:
"Why don't you try to get it from Leaked Rom." cz ofc you already know it so I assume you cannot do such thing.:laugh:
status?
Firecode, is your github code completed for ics (navigation & fingerperint)? am planning to use in cm-10.1, Thx.
Nd
Zn7mkUKzN1r8aCIV said:
Firecode, is your github code completed for ics (navigation & fingerperint)? am planning to use in cm-10.1, Thx.
Click to expand...
Click to collapse
Not jet. The navigation and database administration works but finger lock screen need lot of work the resources and code itself need to be port so they looks and works like pattern lock screen. Gingerbred is quiet different lock functions and the time that need to spent for this is next problem because I am quite busy in these days.
Zn7mkUKzN1r8aCIV said:
Firecode, is your github code completed for ics (navigation & fingerperint)? am planning to use in cm-10.1, Thx.
Click to expand...
Click to collapse
I though epinter already included this stuff in the cm-10.1 repo?
ravilov said:
I though epinter already included this stuff in the cm-10.1 repo?
Click to expand...
Click to collapse
They just included hacked apk's but not android core framework for fingerprint, in my pc is scrach for cm10.1 but there thing go in new level from just dedicated lock screens they are converted to lock widgets and source for it is took from ics so to build cm10.1 from ginger fp code first need to make ics code.
I just posted this to cm10.1's thread, but i think it fits here as well
https://www.youtube.com/watch?v=eZUSBCZZA6c
Thanks firecode95 for your hard work!
Sent from my MB860 using xda app-developers app
andresrivas said:
I just posted this to cm10.1's thread, but i think it fits here as well
https://www.youtube.com/watch?v=eZUSBCZZA6c
Thanks firecode95 for your hard work!
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
nice i installed it but my fingerprint sensor refuses to work at times... i seriously dont know why :/ it works well while charging mostly but after i unplug it no response
So the problem with not responding sensor isn't solved by using the ported libs? It was my last hope for a properly working fingerprint sensor
johnannis said:
So the problem with not responding sensor isn't solved by using the ported libs? It was my last hope for a properly working fingerprint sensor
Click to expand...
Click to collapse
Take into consideration that those are GB libs hacked to work on a OS 3 releases above, like triying to run win 98/me drivers on windows 7
johnannis said:
So the problem with not responding sensor isn't solved by using the ported libs? It was my last hope for a properly working fingerprint sensor
Click to expand...
Click to collapse
Forget jcrahul message, I think your answer is here:
firecode95 said:
Not jet. The navigation and database administration works but finger lock screen need lot of work the resources and code itself need to be port so they looks and works like pattern lock screen. Gingerbred is quiet different lock functions and the time that need to spent for this is next problem because I am quite busy in these days.
Click to expand...
Click to collapse
Fingerprint naviguation: OK
Fingerprint lockscreen: needs lot of work because "resources and code need to be ported"
I know it but leaked ics framework isn't working properly, IF the ported libs n framework don't work properly either, that may means the problem is on newer versions of Android and their hardware management
johnannis said:
So the problem with not responding sensor isn't solved by using the ported libs? It was my last hope for a properly working fingerprint sensor
Click to expand...
Click to collapse
How do you mean not responding fp sensor? The seansor works fully just need lot of work in fp source integration for lock screen. And in leak rom isn't any problems with fp. If you had problems it culd be due hardware, try change fp sensor.
P.S
I think that I litle misunderstood you and this is more for @jcrahul
I realy need development account acces for authentech or documentation with SDK's for fingerprint, it's most important for now, because just trying figure out from code how all works is hard and time compsuming process. So please anyone who has this try to give a helping finger
Hmm, so you say that this not responding issue doesn't affect your device?
In mine this issue really exists and on some others too. It's like you don't even swipe your finger. And it happens as said above, when it shows up the only way to stop it is to plug in the charger, and most of the times after next deepsleep it shows up again.
For example, one day I tried using fp and worked well from the morning till the afternoon (when I got home to charge it). But after removing the charger it showed up.
I think I had go back to GB to test it but I ll do it again.
EDIT: So I went back to GB rom. Unlikely for my ATRIX but likely for the project the issue is still here. So it must be hardware related,I ll sent it for service (its still in warranty )
Update
The ROM manifest and source updated. The testing can start now and if found a bug please repot it