For 4 weeks ive been looking at KK and playing with source... 4.4 images Build (ota zip fails)
4.4 images are building im coming here for developers help on getting this rom working
i will continually post here my sources (this is an awesome forum) and my progress as i go on.. been at this for over 4 weeks developing my first rom...
this post will get more colorful and easier to read over time:
Below is a quote from my google+ post on Xoom Community (join it.. its a great place)
STATUS UPDATE:
Xoom Wifi - LIFESTREAM ROM by LOGMD
Build 17 - Failed BUT we have:
-boot.img
-system.img
-kernel (supposedly)
I have managed to extract the system.img into a flashable Zip... but i KNOW the permissions are F*%#ked
I installed boot.img manually using fastboot but its left me in bootloops (not actually getting to the boot animation, looping on the moto logo)
i flashed the 4.2.2 EOS4 BigPart image because its compatible with the new partition layout and it doesnt bootloop... but it also doesnt get to bootanimation either...
BUT it did respond to ADB devices and came up as unauthorized device so obviously when i ADB SHELL it says device unauthorized...
I THINK that i need to build the boot.img with the BigPart patch but im not sure even if the kernel is just not working properly. if ive built it properly or whatever...
IF ANYONE knows any xoom developers or you are a xoom developer and know how to build kernels on a version of android thats not supported officially or if you think you could help me out then im all ears
Click to expand...
Click to collapse
BIG THANKS to the BigPart & 4.3/4.4 dev thread (will add links later) would have been stuck at one of the many roadblocks if it wasnt for these people!
we are getting closer to getting a rom working i can feel it! lets make it happen! loving how live the threads are in this forum for the xoom!
PROGRESS
I will update here the overall progress towards a working rom WHEN i get time as work can get very busy. I will not be selfish and steal peoples ideas if they are the ones who invented it then i will give credit where it is due, and it is possible that this rom could never be built or someone beats me to it. I may end up collaborating with someone with more experience on thier rom but ill do my best to get an edition of my own working.. IF all fails for now with 4.4 i will spend time on a 4.2 rom/kernel
DISCLAIMER
I (LOGMD) am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software. In saying that Enjoy a respectful development environment, expect no ETA's and help me where necessary
REPARTITION
SYSTEM.IMG
BOOT.IMG (kernel, ramdisk etc)
THREADS OF LIFE (words stolen from Shadows Fall Album)
This is where you and I should use as a starting point for homework using the communities are a great way to learn the newest up to date developments! I do not read fiction books but I sure as hell read technology!
GOOGLE+
+LOGMD | +XDADevelopers | +XoomOwners
XDA-Forums
BLOG
OTHER (follow me)
Twitter | Facebook
I wish you luck. As your skill and luck is our luck.
Sent from my Xoom using XDA Premium HD app
subbed! anticipating great things!
way to be!! Super excited. Need guinea pigs? I'll help
sbeaber4 said:
way to be!! Super excited. Need guinea pigs? I'll help
Click to expand...
Click to collapse
ill start uploading some system img zips soon. see if i can take anything more out of android that is not essential to makeing it work i.e. NO BROWSER NO PLAY STORE everything gone, i was told by another developer they have managed to get the rom small enough for fastboot (~251MB) so ill try the same so it will be easier to flash!
I stupidly did not reserve posts so heres one more
boot.img
For the kernel, why don't ask to ElementalX ?
If we have a system.img but it's to large to flash through fastboot,
thinking out loud but could we get it connected via adb in recovery and do the dd if=/location/of/system/img of=/dev/block/mmcblkpXXX
would that work?
---------- Post added at 11:52 AM ---------- Previous post was at 11:48 AM ----------
Another thought on trying to get the img into a flashable zip, not sure if you've heard of dsixda kitchen! http://forum.xda-developers.com/showthread.php?t=633246
I've used it before in regard to the Xperia T and it's compatible with many devices and can turn system imgs into zips I believe
If using bigPart Kernel than you can not use fastboot as fastboot does not know the new partition layout.
Incredible news!!
Love to see KitKat on Motorola Xoom!
Sent from my Xoom using Tapatalk 4
Have you tried using Motorola's mfastboot.exe? I've had to use that instead of the regular fastboot to flash large system images to my Moto X, I'm curious if it would work for the repartitioned Xoom. Apparently it breaks the image down into two parts to get around size limitations with the regular fastboot.
I uploaded it here if you'd like to test it out
TWRP
So we partitioned the Tab with 1000 Mo for system, i'm not sure it's necessary, i read it's possible to reduce the size of the ROM under 256 Mo
I have a old Samsung Galaxy Ace and for this old tool on Jenkins the 4.4 cooper is compiled but not flashable because no recovery adapted to flash it.
I visit a lot of site like Mclaw studio and see for each ROM kitkat it's a special TWRP dedicate specialy to kitkat ROM.
So do you thing we need another TWRP or the TWRP big part is ok?
pots22 said:
So we partitioned the Tab with 1000 Mo for system, i'm not sure it's necessary, i read it's possible to reduce the size of the ROM under 256 Mo
I have a old Samsung Galaxy Ace and for this old tool on Jenkins the 4.4 cooper is compiled but not flashable because no recovery adapted to flash it.
I visit a lot of site like Mclaw studio and see for each ROM kitkat it's a special TWRP dedicate specialy to kitkat ROM.
So do you thing we need another TWRP or the TWRP big part is ok?
Click to expand...
Click to collapse
I managed to shrink to 209 MB which flashes =] it may not have anything but core android but thats all we care about right now i dont care about FC... next is kernel follow this link will be more active about kernel updates. im gonna post some nvidia drivers i just found
Elemental-X seems to have updated to beta with support for big partition.
4.4
hawkstorm said:
Elemental-X seems to have updated to beta with support for big partition.
Click to expand...
Click to collapse
Exactly, http://www.androidfilehost.com/?fid=23252070760974877
Now we have a bigpart partitioning, a bigpart Kernel
So what needed for start a 4.4 kitkat test build?
pots22 said:
Exactly, http://www.androidfilehost.com/?fid=23252070760974877
Now we have a bigpart partitioning, a bigpart Kernel
So what needed for start a 4.4 kitkat test build?
Click to expand...
Click to collapse
Technically we didn't even need the big part
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Cameron581 said:
Technically we didn't even need the big part
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Well, the dev said that he needed to remove a few things to get it to flash. Maybe now he can reinsert whatever he removed and check whether it can flash.
hawkstorm said:
Well, the dev said that he needed to remove a few things to get it to flash. Maybe now he can reinsert whatever he removed and check whether it can flash.
Click to expand...
Click to collapse
That makes no sense he removed apps and was on a parted kernel
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Experimental X was just updated to support Bigpart. It is not the update that Logmd is looking for to support KK 4.4. The new kernel needs a lot more upgrading involving drivers for the Tegra Chip.
They are probably trying to see if they can get KK 4.4 working without bigpart first. And if successful it can blossom from there with ROM developers taking advantage of BigPart to create more custimized ROMS.
4.4
Cyanogenmod launch from yesterday and today a lot of ROM CM11 4.4.2
http://download.cyanogenmod.org/
All ROM don't exceed 200 Mo, so i'm really not sure about the necessity of Bigpart.
Related
Hey guys,
Alroger has included a patched framework into one of his builds, offering support for PDroid. Based on their work, the modified JAR files seem to do the work nicely. Therefore, you can find the patched and unpatched versions of the files in CWM flashable format attached to this post.
Please report back if it works for you, as it will be valuable feedback to the team porting PDroid to ICS.
For more info on PDroid, go here:http://forum.xda-developers.com/showthread.php?t=1357056
For more info on the port of PDroid to ICS, go here: http://forum.xda-developers.com/showthread.php?t=1554960
Notes & Observations
- Only compatible with official CM9 (Android 4.0.3 and 4.0.4).
- Only compatible with Recovery 3.0.x or later (should not be a problem with recent/modern ROMs/builds).
- This build is only compatible with SGT7 device variants and the CM9 builds released for these devices.
However, if you indeed get into trouble, try clearing cache, dalvik cache and flashing your original ROM on top of this package. No data wipe should be required!
Download & Install:
Download OP post attachment of your choice (based on CM9 0421 nightly)
Flash P1-PDroid-CM9-0421-CWM.ON.v2.zip to apply patch
Flash P1-PDroid-CM9-0421-CWM.OFF.v2.zip to remove patch
Save zips onto your Tab
Reboot in Recovery mode
Install zip from SD Card
Reboot tab & wait for Android to upgrade
Install PDroid app from market (market link)
Enjoy
Disclaimer
I will not offer support to anyone in case these ZIPs cause any harm or damage in any way. You are responsible of your own actions including flashing anything to your device!
Thanks and Credits
Thanks, in no particular order to these guys:
svyat for the initial work
pastime1971 for the ICS port
alroger for building the patched framework files compatible with CM9 and giving me his blessing to pack the patched framework files
Let me know of any issues or success stories in the thread.
Peace,
C.
I don't need to flash this patch as I already use alroger's build of CM9 ROM with PDroid (2012-04-24), but I just wanted to say thank you, as this is excellent news for next time when I don't use a ROM that already includes PDroid patches!
http://cafe-ti.blog.br/1524~sgt7-p1000-android-ics-cm9-mtd.html
Is this device specific?
It runs on all SGT7 variants running official CM9 build.
It won't work for other ROMs or other devices than SGT7.
PS: if it runs on something else, it is only by chance!
Peace,
C.
Ok...thanks anyway.
From the OP it read like it was good for any cm9.
Hope nobody flashes it on the wrong device.
Luckily I was smart enough to ask first.
I thought it is common sense since this is SGT7 forum?
Sent from my GT-P1000 using XDA
priyana said:
I thought it is common sense since this is SGT7 forum?
Sent from my GT-P1000 using XDA
Click to expand...
Click to collapse
Just followed a link that he posted from a different thread....
And the xda app doesn't say what device thread you're in if you follow a link.
will this work on a sph-p100 running update-cm-9-20120425-NIGHTLY-p1c-signed
LivnDream said:
will this work on a sph-p100 running update-cm-9-20120425-NIGHTLY-p1c-signed
Click to expand...
Click to collapse
Yes, @cheatman's post is exactly for the official cm9 nightly p1 and p1c (Galaxy Tab 7 GSM and CDMA).
And he offers the removal of the patch also, in case you have any problems.
thanks will give it a go
Hi Cheatman,
Will this work on AOKP ICS?
Or will it need a different one? Can you build one?
Thanks!!
First thing: updated OP post to avoid confusion.
Secondly @priyana: It will probably break AOKP builds as the framework is heavily modified compared to CM9. You could try to flash it and report back, but be ready to flash AOKP again on top of it if it bugs out.
If you have issues, you will not need to restock or wipe data. You can just flash AOKP again on top of it and it should return to normal after a reboot.
Peace,
C.
Thanks Cheatman.
Just to feed back here.
I just tried applying it on my aokp build #31 but can't boot into the OS.
Flashed the from again on top of it and I am back to aokp like you said.
Sent from my GT-P1000 using XDA
Same for me with AOKP. After installing the ON package it boots up to the part of updating, the next start it doesn't boot up anymore and is stuck on the bootlogo and makes a short vibration in repeated intervalls.
Installed the OFF package, updated on first boot, doesn't work anymore on next boot just like the ON package.
Too bad for me as I'm going to use the train now and could've used the tab.
Thanks anyway and I'm still interested in this and would hope to see a fix.
You can still use the tab by flashing aokp again.
All data intact in my case.
Sent from my GT-P1000 using XDA
I know that and did that already because OP wrote that in the first post:
"However, if you indeed get into trouble, try clearing cache, dalvik cache and flashing your original ROM on top of this package."
Works as usual but no pdroid.
OK.
Read you wrongly because you said too bad, you "could have used the tab"
I thought you meant now it is unusable/broken, hence the reminder.
Sent from my GT-P1000 using XDA
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.2.2 (JB), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
WIKI
Click to expand...
Click to collapse
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/D710_Info
INSTALLATION
Click to expand...
Click to collapse
First time installing CyanogenMod 10.1 to your Epic 4G Touch, or coming from another ROM:
- Copy GApps and CM 10.1 zip's to your internal SD Card
- Make sure you're NOT RUNNING A KERNEL WITH THE MMC-SUPERBRICK-BUG
- Make sure you're running a proper working ClockworkMod-Recovery
- Make sure you're not running a JB modem
- Boot into recovery
- Flash CM 10.1 zip from internal SD Card
- Flash GApps zip from internal SD Card
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of CyanogenMod 10.1:
- Copy CM 10.1 zip to your internal SD Card
- Boot into recovery
- Flash CM10.1 zip from internal SD Card
- Reboot
Upgrading from CyanogenMod 9:
- Copy 4.2.2 GApps and CM 10.1 zip's to your SD Card
- Boot into recovery
- Flash CM 10.1 zip from SD Card
- Flash GApps zip from SD Card
- Reboot
DOWNLOAD
Click to expand...
Click to collapse
CM 10.1 official nightly builds:
http://www.get.cm/?device=d710
Google Apps:
http://goo.im/gapps
CHANGELOG
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/q/status:merged+branch:cm-10.1,n,z
http://changelog.bbqdroid.org/#/d710/next
DONATIONS
Click to expand...
Click to collapse
If you want to donate a few bucks for the work:
Thanks to all donators!
First! Thanks Dastin, you are the man! Now go relax with your amazing girlfriend lol.
Sent from my SPH-D710 using xda premium
Nicely done bro!
Sent from my SPH-D710 using xda app-developers app
Wait.... WHAT!
Mind.. Blown.
Sent from my SPH-D710 using Tapatalk 4
It looks like the change log is pointing to the wrong branch, shouldn't it be http://review.cyanogenmod.org/#/q/status:merged+branch:cm-10.1,n,z ??
Sent from my SPH-D710 using xda premium
Well i stayed up to install it. So far so good. I was holding out on an older WFTN build one before many people started having wifi and data issues.
GPS 3G, 4G, WIfi all working well so far. Won't really know for a day or two. Can't be sure of anything but my initial impressions are good.
Whoa!! Thank you! Great Job man!
official! better late than never, amazing work dastin
Sent from my HTCONE using Tapatalk 2
=]
Congrats buddy, Good job. But i don't get why i cant find it under devices on the cya site?
Edit: Did any drastic changes or anything really change from unofficial? JB modems do work with 4g ONLY no 3g support
http://dl.xda-developers.com/attach.../9/0/6/7/5/Screenshot_2013-08-15-10-34-02.jpg
thanks for getting our phone recognized....Finally!!! Great job bro!
Great Work. I have been waiting for this day!
Side Note as I see it was asked, there is no data while on JB Modem. We know this to be true because, Dastin hasnt mentioned it as a fix in WFTN Build as of yet. Also, just to confirm. I flashed a JB modem and come to a result with no data.
=]
Thanks, i didn't see it in op to not use a modem and i thought that was the requirement for it to become a CM official rom.
elzero26 said:
Great Work. I have been waiting for this day!
Side Note as I see it was asked, there is no data while on JB Modem. We know this to be true because, Dastin hasnt mentioned it as a fix in WFTN Build as of yet. Also, just to confirm. I flashed a JB modem and come to a result with no data.
Click to expand...
Click to collapse
woooo
JB modems do work. proof is in the pudddin (4g only)
http://dl.xda-developers.com/attach.../9/0/6/7/5/Screenshot_2013-08-15-10-34-02.jpg
So just for the record, how will WFTN differ from these nightly releases now since we have official support?
Pretty sure WFTN will be dead as hes going to continue to work on this rom and tweak it to make it perfect. With it being official i assume hell be getting alot more assistance from the cya community which will be great! other more exp people will have to elaborate more than me
darklavalizard said:
So just for the record, how will WFTN differ from these nightly releases now since we have official support?
Click to expand...
Click to collapse
darklavalizard said:
So just for the record, how will WFTN differ from these nightly releases now since we have official support?
Click to expand...
Click to collapse
Had exactly the same question.
Really nice work btw. Will likely be moving away from this device soon but will certainly keep running your builds on it as it'll make a good play/backup device.
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
papertown11 said:
Pretty sure WFTN will be dead as hes going to continue to work on this rom and tweak it to make it perfect. With it being official i assume hell be getting alot more assistance from the cya community which will be great! other more exp people will have to elaborate more than me
Click to expand...
Click to collapse
My understanding was that official cm builds needed to remain pretty "pure" while wftn would give the flexibility to add whatever tweaks dastin wants. I've asked the same question and may be making all of this up. So I'll let dastin tell us for sure.
All up to dastin for sure. I don't know why he'd wanna start adding tweaks and halos and stuff when he was going for pure and clean before but if he wants to start dabbling with wftn like that he can but as he always says he doesn't have much time so i figured he'd pretty much drop it and move on to full support of this i may be wrong but hell be the only one to answer it.
gg_99 said:
Had exactly the same question.
Really nice work btw. Will likely be moving away from this device soon but will certainly keep running your builds on it as it'll make a good play/backup device.
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
My understanding was that official cm builds needed to remain pretty "pure" while wftn would give the flexibility to add whatever tweaks dastin wants. I've asked the same question and may be making all of this up. So I'll let dastin tell us for sure.
Click to expand...
Click to collapse
OK flashed the Nightly and keyboard force closes the whole time. Can't type anything including my Google account. MD5 sum matches though. Well, it's 1:30 in the morning here so I'll just continue tomorrow. Just a heads up.
Sent from my Nexus 7 using Tapatalk 2
=]
I've actually set up fresh 3 times and it works perfect for me . Do your standard wipe factory/ wipe dev cash then reload gapps and you should be fine. Load a gb modem too you should be gtg
sol_671 said:
OK flashed the Nightly and keyboard force closes the whole time. Can't type anything including my Google account. MD5 sum matches though. Well, it's 1:30 in the morning here so I'll just continue tomorrow. Just a heads up.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
This is the support thread for CM10.2 on the T-mobile Samsung Galaxy S II. It is still a major work in progress, so please make sure you have a backup that you can restore if you run into problems.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view http://changelog.bbqdroid.org for a full list of changes.
IRC SUPPORT:
Join us in #teamchopsticks or #cyanogenmod on the Freenode IRC network.
DO NOT ASK FOR SUPPORT IF YOU FLASH A DIFFERENT KERNEL!
The kernel packaged with CM10.2 is very tightly coupled with the ROM code. If you install a kernel different from the one in this ROM, please do not ask for any support.
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Please see our blog at http://www.teamchopsticks.org for installation, download links and release notes.
Install instructions:
Installation, Download, and Release Notes: http://www.teamchopsticks.org/p/cm102-release-notes.html
Contributing/Building: http://www.teamchopsticks.org/p/contributing.html
FAQ/Troubleshooting: http://www.teamchopsticks.org/p/faq.html
NOTE! You MUST use the recovery provided at the install link otherwise you will boot loop!
NOTE! You MUST wipe /cache, /data, and /system!! Also, make sure you install a 4.3-compatible gapps package. See our blog for more information.
The CyanogenMod team and TeamChopsticks would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Womp womp! Good job Nancy.
Thanks Guys!!
---------- Post added at 10:01 PM ---------- Previous post was at 09:51 PM ----------
I see the 20130729 gapps are posted, aren't the 20130813 the 4.3 set ?
so... is cwm permanent or will we be able to flash with twrp in the near future?
cause i personally cant stand cwm, got soo used to twrp and going to be hard to go back, i had some bad experiences with it
mycars12 said:
so... is cwm permanent or will we be able to flash with twrp in the near future?
cause i personally cant stand cwm, got soo used to twrp and going to be hard to go back, i had some bad experiences with it
Click to expand...
Click to collapse
Well, that's it for now - we technically don't maintain the recoveries, so you'll have to talk to the folks that support them directly. This particular one is the stock CM recovery that we added external_sd support to and it is build with the proper SELinux capability to prevent the reboot of doom seen with the CM10.1 based recoveries.
Ohhh yeah, just saw this drop on g+. Downloading now, thanks for the hard work. Will report back once up and running
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
so flash it using the provided recovery then... Switch back to twrp. UNDERSTOOD SIR
JesusWazBlack said:
so flash it using the provided recovery then... Switch back to twrp. UNDERSTOOD SIR
Click to expand...
Click to collapse
If you do that, you are on your own. The 10.1 recoveries do not know how to deal with the SELinux capable file system properly. You can run into some major snags that way.
This recovery, although it's very basic, works just fine for flashing zips and taking backups. Plus, it is the only one right now for the Hercules and Skyrocket that correctly works with the new filesystem for 4.3
car vs driver said:
If you do that, you are on your own. The 10.1 recoveries do not know how to deal with the SELinux capable file system properly. You can run into some major snags that way.
This recovery, although it's very basic, works just fine for flashing zips and taking backups. Plus, it is the only one right now for the Hercules and Skyrocket that correctly works with the new filesystem for 4.3
Click to expand...
Click to collapse
Oh alright. Guess no twrp then Lol. Thanks for the work! Appreciate it
No sweat man, I"m sure it's only a matter of time before the appropriate changes are made to TWRP and CWMR Touch. Our device is a bit of an oddball in how the storage volumes are setup, so this issue was really unique to us with 4.3
Woohoo! Thanks devs! This phone will remain me for a long time to come so this gives me a smile
Once again, thanks and I will flash and report back :good:
-------------------------------------------------------------------------------------------
Ahh CWM, the good old days xD
Recovery was fun to use lol
ROM works beautifully on my end, no issues so far. Smooth and fast.
Good work!
Hmm, does DSP Manager work properly for anyone?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 4
Joining the party..
Sent from my SAMSUNG-SGH-T989 using Tapatalk 4
so far so good, just missing the options to disable touch keys from lighting up. Going back to 4.2.2 until mainline nightlies show up.Also lack of TWRP is upsetting.
Thanks for the work you've been doing for us!! Can't wait for a dayly driver!
The only bug I've been able to spot so far is that there is still a reboot issue when accessing the external SD card from a gallery app. I can use quickpic just fine, but once I hit the SD card folder, the phone locks up and inevitably reboots.
Other than that, this is a very good alpha build of Android 4.3! Great work TeamChopsticks!
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
The recovery link isn't working.... anyone have a mirror that isn't d-h.st?
Edit: Finally downloaded...
Edit: anyone know if advanced settings are making a come back any time soon?
Man, I feel so late joining the 4.3 party.
Anyway, just flashing the CWM for CM10.2 now. Its not TWRP but as long as I can still revert back to my nandroid backup made with TWRP in case things go wonky, I'll be fine.
So far, CM10.2 alpha builds for Hercules runs great: feels a bit smoother than 4.2 and faster.
4.3
Thanks so much for the hard work devs this is great!!!
There is a NFC wakelock issue with the latest 10.2 rom, as shown by BetterBatteryStats.
NfcService:mEeWakeLock - 87.7%
I cannot turn off NFC either.
As a proof of concept I compiled Kit Kat for our Acer Inconia. It needs a new build of CWM in order to flash. I have not been able to boot up CWM that I compiled so anyone here that has built recovery on here before try to build latest CWM and/or TWRP then we can try out this KitKat build to see if it boots or not. It may need some kernel patches. It's using pio_maski's jb-mr2 trees that I modified for 4.4 for a100 (note: I haven't uploaded yet and won't unless it boots).
Download: http://d-h.st/aKr
What you can do to help:
1. Compile the latest TWRP or CWM and post if it boots. Only do this if you've done it before; I'm not going to teach because it is out of my knowledge why CWM won't boot. If you come across any errors and don't know how to fix PM me or post here I'll help you fix it.
2. NOTHING can be done until we have a working (latest) recovery.
Sources:
Device: https://github.com/awid777/android_device_acer_a100 (cm10.2 branch)
Note for the sources: This isn't the source I used to compile the initial build. However, they are almost identical. The credits for the sources for the ROM go to @pio-masaki for his device and commons trees and prebuilt kernel. I would post the sources I used but I never uploaded them because I ended up deleting them early on as I prefer to use a single device tree. All my commits will now be posted to the listed source.
awidawad said:
As a proof of concept I compiled Kit Kat for our Acer Inconia. It needs a new build of CWM in order to flash. I have not been able to boot up CWM that I compiled so anyone here that has built recovery on here before try to build latest CWM and/or TWRP then we can try out this KitKat build to see if it boots or not. It may need some kernel patches. It's using pio_maski's jb-mr2 trees that I modified for 4.4 for a100 (note: I haven't uploaded yet and won't unless it boots).
Download: Pending upload.
What you can do to help:
1. Compile the latest TWRP or CWM and post if it boots. Only do this if you've done it before; I'm not going to teach because it is out of my knowledge why CWM won't boot. If you come across any errors and don't know how to fix PM me or post here I'll help you fix it.
2. NOTHING can be done until we have a working (latest) recovery.
Click to expand...
Click to collapse
I am not a "DEV", however I have a good amount of talent with photoshop and have some self taught coding experience with linux and html5. I also am willing to learn/eager to learn. I know you mentioned you don't want to teach. Just know if you point me in the direction I am willing to do the work on my end to get the knowledge and apply it. I have been playing with this tablet and working on a hybrid kitkat look alike using 4.1.2 as my base. I tried using 4.3 and applying 4.4 goodies to it. Didn't work that well. The 4.3 Jellytime was a bit quirky at times and didn't seem stable as a daily driver. I have put together a couple new boot animations to compliment kitkat already. I have also modified Arora installer with a very good kitkat theme. I have used it several times to verify it works correctly. I can provide that if wanted. I am waiting for a stable build and willing to help where I can. I plan on installing this tablet into my dash in the very near future. Once that is done, unfortunately I will only be able to help with themes and basic items that don't require the tablet all the time. I have contemplated having the ability to remove the tablet whenever I leave the car so I guess we will see when I get there. Apologize for the long post.
po8pimp said:
I am not a "DEV", however I have a good amount of talent with photoshop and have some self taught coding experience with linux and html5. I also am willing to learn/eager to learn. I know you mentioned you don't want to teach. Just know if you point me in the direction I am willing to do the work on my end to get the knowledge and apply it. I have been playing with this tablet and working on a hybrid kitkat look alike using 4.1.2 as my base. I tried using 4.3 and applying 4.4 goodies to it. Didn't work that well. The 4.3 Jellytime was a bit quirky at times and didn't seem stable as a daily driver. I have put together a couple new boot animations to compliment kitkat already. I have also modified Arora installer with a very good kitkat theme. I have used it several times to verify it works correctly. I can provide that if wanted. I am waiting for a stable build and willing to help where I can. I plan on installing this tablet into my dash in the very near future. Once that is done, unfortunately I will only be able to help with themes and basic items that don't require the tablet all the time. I have contemplated having the ability to remove the tablet whenever I leave the car so I guess we will see when I get there. Apologize for the long post.
Click to expand...
Click to collapse
This is not a port, thus doesn't need modification. It is compiled (built) from source and the work that needs to be done is in the source code so it can be compiled properly and work without modification
http://wiki.cyanogenmod.org/w/Development
awidawad said:
As a proof of concept I compiled Kit Kat for our Acer Inconia. It needs a new build of CWM in order to flash. I have not been able to boot up CWM that I compiled so anyone here that has built recovery on here before try to build latest CWM and/or TWRP then we can try out this KitKat build to see if it boots or not. It may need some kernel patches. It's using pio_maski's jb-mr2 trees that I modified for 4.4 for a100 (note: I haven't uploaded yet and won't unless it boots).
Download: [url]http://d-h.st/aKr[/url]
What you can do to help:
1. Compile the latest TWRP or CWM and post if it boots. Only do this if you've done it before; I'm not going to teach because it is out of my knowledge why CWM won't boot. If you come across any errors and don't know how to fix PM me or post here I'll help you fix it.
2. NOTHING can be done until we have a working (latest) recovery.
Click to expand...
Click to collapse
Thanks for the link and quick response, will take a look through some of that stuff and see if there is anything I can do to help. Also I noticed while I was typing the first one you put up a download... Did you get it to boot. I downloaded and tried using TWRP and was unsuccessful. I tried a couple times to make sure it copied over from the computer correctly. Still the same result.
4.4 updates different. Latest cwn will flash it. Maybe there's an easy way to do this
Sent from my SPH-L710 using XDA Premium 4 mobile app
Ok so I am stuck right now. I spent a couple hours building an environment and started compiling from source. I am stuck at this point:
$ source build/envsetup.sh
$ breakfast a700
Where a700 is, should be a100. I get errors when doing this because CyanogenMod does not have the device in it's file system. Whoever has successfully done this, please advise. I am over half way with this and would like to complete the build. I have about 20gbs of data sitting on my cpu waiting to compile this so the sooner we can find the solution the better. Thanks in advance.
Need help solving this to move further... There might be a work around, however I have never done this and I am stuck.
Wait till tonight. I'll post my code.
Sent from my One SV using Tapatalk
awidawad said:
Wait till tonight. I'll post my code.
Sent from my One SV using Tapatalk
Click to expand...
Click to collapse
Sounds good. I spent a good part of 3 hours compiling a master build of Kitkat which was complete prior to me leaving for work this morning, however my daughter kicked the power strip under the desk and shut everything down. I will try and find a little time tonight to recompile.
Am I missing something?
Sent from my SPH-L710 using XDA Premium 4 mobile app
TWRP Version?
Is this TWRP new enough for your needs if not what is the newest version you are aware of
a100 TWRP 2.6.1.0 windows installer: as far as I can tell the Twrp image is based of linuxsociety's/GodMachine's work I know for sure the installer is his
http://d-h.st/Rfm
I have flashed this and all seems to work well
I also took the 2.6.1.0 from the above linked installer and put it into a flashable.zip that originaly contained GM's 2.2.2.1 TWRP
I updated the script to show the proper version as well attatched below
AngryManMLS Is responsible for both 2.6.1.0 and 2.6.3.0, "if I am not mistaken"?
His windows/Linux installers can be found here: http://www.androidfilehost.com/?a=show&w=files&flid=9577
and Here:http://forum.xda-developers.com/showpost.php?p=47555451&postcount=109 For 2.6.3.0
I also invited AngryManMLS to build the TWRP needed for this project So We'll have to wait and see if he can help "Break US OFF A PEICE OF SOME KIT-KAT---- Iconia???!!!!!!"
I just want to correct something. The only thing I have done was updating the Windows and Linux installers for TWRP. I have no responsibility with the compiling of TWRP itself. At this point we're waiting for the TWRP folks themselves to fix whatever issues that lie with Kit Kat 4.4. I don't know what to say beyond that. Sorry.
AngryManMLS said:
I just want to correct something. The only thing I have done was updating the Windows and Linux installers for TWRP. I have no responsibility with the compiling of TWRP itself. At this point we're waiting for the TWRP folks themselves to fix whatever issues that lie with Kit Kat 4.4. I don't know what to say beyond that. Sorry.
Click to expand...
Click to collapse
My Bad I shouldn't have assumed do you know who is doing the compiling?
I'm going to go ahead and compile TWRP. I've educated myself on the a100 (I've never done programming on this device or any other Tegra based device... Used to Qualcomm and HTC) hopefully it will work. Current TWRP branch on GitHub is twrp2.7 and has all KitKat changes in it. I'll have a build tomorrow morning. Tonight I have to finish my essays and other homework. I'll let you all know if recovery boots or not. If it does boot, I'll go ahead and attempt installing and booting KitKat
hello! I wonder if owners will share files as well as the vendor, I've wanted to compile pacman for this tablet but can not find the source code! Thanks in advance!
josegalre said:
hello! I wonder if owners will share files as well as the vendor, I've wanted to compile pacman for this tablet but can not find the source code! Thanks in advance!
Click to expand...
Click to collapse
Once I have time, which won't be until later tonight. You could use www.github.com/pio-masaki too. Use the jb-mr2 branch for 4.3
http://forum.xda-developers.com/showpost.php?p=41990263&postcount=1
awidawad said:
Once I have time, which won't be until later tonight. You could use www.github.com/pio-masaki too. Use the jb-mr2 branch for 4.3
Click to expand...
Click to collapse
hardslog said:
http://forum.xda-developers.com/showpost.php?p=41990263&postcount=1
Click to expand...
Click to collapse
thank you! I have to have fun these days!
Well I compiled latest TWRP it didn't work it has same errors. I'll take this up with Dees_Troy. Because when I place the same trees and TWRP into the cm-11 source it won't compile, whereas it compiles fine in cm-10 source. When I manually fix compilation errors it compiles but when flashed it doesn't boot. Same story with CWM
Sent from my One SV using Tapatalk
awidawad said:
Well I compiled latest TWRP it didn't work it has same errors. I'll take this up with Dees_Troy. Because when I place the same trees and TWRP into the cm-11 source it won't compile, whereas it compiles fine in cm-10 source. When I manually fix compilation errors it compiles but when flashed it doesn't boot. Same story with CWM
Sent from my One SV using Tapatalk
Click to expand...
Click to collapse
Try compiling cwm then.
Sent from my SPH-L710 using XDA Premium 4 mobile app
NOTE
This is an UNOFFICIAL build of CyanogenMod 10 for the galaxy fame S6810P it should also work for the S6810 but i don´t know for sure since i don´t own this device and don´t want to brick your device so.
If you know that s6810p roms works with s6810 say it in the thread here and i wil edit the asserts later on the sourcecode.
This is only for testers who know how to report an logcat so we find out the problems why it won´t boot and can fix those problems.
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, or dead SD cards,
* nuclear war, pinguin invasions or that you are getting fired because the alarm app failed.
* before flashing it! YOU are choosing to make these modifications, and if
* If you point your finger at me for messing up your device, I will laugh at you. Hard
*/
First Time Installing an custom rom if you have an custom recovery proceed to step download zip and continue.
Install an good custom recovery:http://forum.xda-developers.com/showthread.php?t=2656949
Download the zip
WIPE DATA/FACTORY RESET
Format/System
flash the rom zip from recovery
Flash the kernel from recovery
Reboot
Connect your phone to your pc and use adb to logcat and report it here.
Download Site: TEST VERSION 1.0
https://drive.google.com/file/d/0B1u3mnq0nstfSkdnUVp1YkhPZVU/
Kernel
https://drive.google.com/file/d/0B1u3mnq0nstfVGNsVnFNSDVIVnc/edit?usp=sharing
FAQ/KNOWN ISSUES
Click to expand...
Click to collapse
Wifi doesnt work
Audio doesnt work
Bluetooth works but internal sd isnt mounted good so you cant receive files.
nfc i dont know.
simcard doesnt work
camera doesnt work related to internal sd not being mounted well or wrong permissions
sdcard mounting doesnt work
EVERYTHING RELATED TO RIL
Don´t blame me that it doesnt work fully since there is no official or unofficial sourcecode on github except mine now.
And i don´t own that device.
Credits:
adytzu33 for the cm10 sourcecode
Corsicanu for providing the sourcecode and helping to finalize cm10.
Cyanogenmod for providing their own system
Corsicanu,faizauthar12 and Toshiro71 for being Betatesters.
XDA:DevDB Information
Cyanogenmod 10, ROM for the Samsung Galaxy Fame
Contributors
wulsic
ROM OS Version: 4.1.x Jelly Bean
Based On: Cyanogenmod
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2014-05-30
Created 2014-05-19
Last Updated 2014-05-31
Reserved for Later use
I'd like to test but i dont know how to get logcat. if u give instruction here.i'll try
Thank You
Hi, thanks but the link doesn`t work
Sent from my Meeb[]x-1 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1726238 Here's a way, I don't know if it is outdated. I gonna try to post a logcat after a download the rom.
@wulsic you forgot about gapps - http://goo.im/gapps/gapps-jb-20121011-signed.zip
To provide logcat - install the rom and gapps, make a full wipe, reboot and connect the phone to usb cable and open a cmd where you will type 'adb logcat'. Copy the output-there will be a loop-and paste it here.
You will need sdk installed and configured and proper drivers.. Note that the phone might not boot-will remain on Samsung Galaxy Fame logo. I will test it in an hour or two maybe..
Sent from my Nameless phone
Ohyeah i totally forget i will check it after school i cant do anything now cause i need to go to school.
Hakets sorry but i cant make an mirror now. Next Time i will upload to mega and mediafire or google drive. Or inform me if you guys know a beter website.
If you guys post an logcat attach it in your post instead of quoting it @corsicanu thankyou for making an detailed post i was tired so i couldt finish it.
I will make after school another mirror, make the platform-tools and drivers in one package so people dont need to download the whole sdk. If we Get the phone booted up then i will also post in the op my light gapps i think the fame will also be smoother then with unneccesary bloatware.
Verstuurd vanaf mijn Nexus 4 met Tapatalk
I use google drive without any problems..
Mirrored the zip... You will find also gapps-jb-20121011 for 4.1.x. Cheers!
Removed the link
Update 1: Edited the zip because i received status 7 and reuploaded. Status 7 is because the recovery is built with s6810 kernel and the zip tries to get assert for s6810p. @wulsic you may need to remove manually on every build from updater-script so it won`t request asserts.
Update 2: Something is wrong with init.rc.. @adytzu33 fixed this once but idk how. It`s related to the mountpoints and permissions.
Code:
[email protected] ~/Desktop $ adb devices
List of devices attached
94363000479004F6 device
[email protected] ~/Desktop $ adb logcat
- exec '/system/bin/sh' failed: No such file or directory (2) -
I am wait until beta version or final version
Sent from my GT-S6810 using XDA Premium 4 mobile app
aserted failed: getprop........................................
installation aborted ( status 7)
i guess i'll also wait for next release
Question
I am download from corsicanu link
After instalation
It still bootloop
And I try to use stock boot.img,and it's same
Can corsicanu or wulsic fix this
I am use S6810
Sent from my GT-S6810 using XDA Premium 4 mobile app
corsicanu said:
I use google drive without any problems..
Mirrored the zip... You will find also gapps-jb-20121011 for 4.1.x. Cheers!
https://drive.google.com/folderview?id=0B-zMfsAgHdrxUjFDellHaXJrNlk#list
Update 1: Edited the zip because i received status 7 and reuploaded. Status 7 is because the recovery is built with s6810 kernel and the zip tries to get assert for s6810p. @wulsic you may need to remove manually on every build from updater-script so it won`t request asserts.
Update 2: Something is wrong with init.rc.. @adytzu33 fixed this once but idk how. It`s related to the mountpoints and permissions.
Code:
[email protected] ~/Desktop $ adb devices
List of devices attached
94363000479004F6device
[email protected] ~/Desktop $ adb logcat
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
Corsicanu i will remove the line
TARGET_OTA_ASSERT_DEVICE := nevisp,s6810p,GT-S6810P from the boardconfig.mk i will look into init.RC after school. But i just need to know or the ROM is compatible with Every device so i can mention it.
Verstuurd vanaf mijn Nexus 4 met Tapatalk
toshiro71 said:
aserted failed: getprop........................................
installation aborted ( status 7)
i guess i'll also wait for next release
Click to expand...
Click to collapse
Try to download from corsicanu,he fixed it
Sent from my GT-S6810 using XDA Premium 4 mobile app
Need to point out some things:
@wulsic you need to remove manually from updater script every time as the compiler still inserts an assert.. Was tested with @adytzu33 and came up to same conclusion. The other solution would be to make another cwm for all devices based on s6810p kernel.
And the rom will be compatible with all version of single sim Fame as they work with custom stock. Only problems that may appear could be 'no sim' errors like on stock rom for different zone.
@faizauthar12 there is no point to download again as we are sure something is wrong there.
For all here, these builds are debug builds. The only purpose of these builds is to patch existing bugs and make it work. If you are not sure of what you`re doing, the best will be to stay away. It may not boot, may brick your phone or you may lose your data. You are the only one responsable for any damage that you do to your phone.
corsicanu said:
Need to point out some things:
@wulsic you need to remove manually from updater script every time as the compiler still inserts an assert.. Was tested with @adytzu33 and came up to same conclusion. The other solution would be to make another cwm for all devices based on s6810p kernel.
And the rom will be compatible with all version of single sim Fame as they work with custom stock. Only problems that may appear could be 'no sim' errors like on stock rom for different zone.
@faizauthar12 there is no point to download again as we are sure something is wrong there.
For all here, these builds are debug builds. The only purpose of these builds is to patch existing bugs and make it work. If you are not sure of what you`re doing, the best will be to stay away. It may not boot, may brick your phone or you may lose your data. You are the only one responsable for any damage that you do to your phone.
Click to expand...
Click to collapse
Sorry for my mistake
Sent from my S6810 using XDA Mobile app
I just wanna say, I'm glad that finally someone built CM for galaxy fame
Thanks for all your works guys..
I'm ready to be your tester
But, just out of curiosity..
why don't you guys compile CM11 instead?
I mean, someone has making effort to do it, but also stuck in somewhere..
maybe you guys could team up or something
here's the link:
http://forum.cyanogenmod.com/topic/91390-compiling-cm11-to-the-galaxy-fame/
and
http://forum.xda-developers.com/showthread.php?t=2713973
regards,,
cheers
and keep famous
midoen said:
I just wanna say, I'm glad that finally someone built CM for galaxy fame
Thanks for all your works guys..
I'm ready to be your tester
But, just out of curiosity..
why don't you guys compile CM11 instead?
I mean, someone has making effort to do it, but also stuck in somewhere..
maybe you guys could team up or something
here's the link:
http://forum.cyanogenmod.com/topic/91390-compiling-cm11-to-the-galaxy-fame/
and
http://forum.xda-developers.com/showthread.php?t=2713973
regards,,
cheers
and keep famous
Click to expand...
Click to collapse
because, as i said, other version of android different than stock (4.1.2) needs porting of drivers.. and when you end up with errors you don't really know wich is the problem - incomplete device tree or incompatible drivers.. will try to reach him and see if we can team up.. cheers!
Sent from my Nameless phone
Stuck in bootsplash, please tell me how to solving this ?
Ikhsan_novindri said:
Stuck in bootsplash, please tell me how to solving this ?
Click to expand...
Click to collapse
Wait man,it's under maintaince cause all device stuck on boot
Sent from my GT-S6810 using XDA Premium 4 mobile app
Ikhsan_novindri said:
Stuck in bootsplash, please tell me how to solving this ?
Click to expand...
Click to collapse
Flash stock rom via odin or restore a previous backup if you have.
I will say it one more time. This isn`t a working cyanogenmod, it doesn`t boot, and the only purpose of releasing it is for debug. If you don`t know what this is about stay away from this thread. Also please read the whole thread before flashing. Was that much 2 pages?
We will keep it low until a working version. If there is anyone who would like to help us with tests and debugging PM me or @wulsic and maybe we`ll cooperate. Thanks!
Also http://github.com/wulsic & http://github.com/corsicanu for those who want to help on this project.