Here is a colloction of all the available Jellybean custom roms for GalaxyTab 7.7.
17/1/2014
Add the new JB build: BeanStalk link.
7/10/2013
After studying the source of fstrim, I manage to get it work on our CM kernels. Thanks to UpInTheAir's tips! :good:
The update kernels are good for all the ROMs I posted. LagFix/Fstrim is working now. Cheers!
History
22/7/2013
The Samsung blobs are really outdated. It's getting harder and harder to port our tab to new codes. Need you guys to show more patrience to test and report on the new builds.
Flash this patch View attachment p6800-TelephonyPatch.zip will fix the Telephony and kernel issue of p6800 in 16/7 cm10.1. Not work for PAC. Good luck!
20/7/2013
A bug in the new CM source cause i815 not boot. The fixed version 20130720 is uploading now. Salute to Lt.col.johncross and other i815 owners for helping me test. Cheers!
16/7/2013
A tiny bug (a missing flag) in the device tree cause the new SystemUI crash! My repo was corrupted after repeatly reverting the commits. It took me a whole week to recover! I really need to complete my uploads to github!
In this new build, I switch to the 4412 kernel source (3.0.64) with new sensor blobs. Native NTFS support is finally there. For those who want to change their external sd to NTFS, please noted that recoveries can't read NTFS. Testing and rebuilding now. Will upload in an hours. Cheers!
24/6/2013
It's been a while for cm10.1 update. The new cm10.1 is uploading now. Cheers!
9/6/2013
It was a busy week. The most important thing in early June is the momerial of the "Democracy movement of June 4" in 1989. The whole world was beneficial from it but not the origin China... :crying:
I upgrade the power management and a few kernel drivers of the CM kernel. Which fixed the charging loop issue but the tab will reboot to system after charging for a few mintues. Don't know if it is normal yet?. Gpu max. freq. is 400Mhz and update to the new blobs now. I also merge the two wifi driver to give a more stable driver. The firmware of wifi chip is updated to version 4. Hoping the kernel is done and I can move on...:fingers-crossed:
3/6/2013
It's really great that Espen96 has setup a host at his server for me! :good:
http://3djanos.com/daniel_hk/index.php?dir=rom/pa3
It is a pure download page without any ad. and delay. Also works great for downloading in the tab.
1/6/2013:
After two weeks of sweaty work on the wifi driver, I finally manager to finish TWO workable drivers. One base on Atheros latest driver on 3.9 kernel. The other one derived from the stock JB source. All the wifi and power management related drivers are modified. Both drivers work quite well in power consumption and connectivity. I use the Atheros driver as standard and will release the other drivers in a seperate kernel shortly.
CM has change a lot in the pass two weeks. Sadly, pie seems not working yet, or I don't know how... Box has limits in download so decided to remove it from pre-release. I'm open to any suggestion on new hosts. The new builds are uploading now. Cheers!
17/5/2013:
The latest cm10.1 is uploading to pre-release now. Base on the test kernel, full multi cast and vif supports are added. I have test it with Torrent download for a few hours. Hoping the wifi p2p wakelock (sleep drain) issue is fixed.
16/5/2013:
Sadly, the new wifi driver from p6800 JB source is not working on 4.2.x. Tab will reset after system start. However, I found another bug in our wifi driver's wakelock. Since cm10, the kerenl has not handle mulitple vif (which p2p always use). It just quit at the wow_suspend when detected more than one vif. In cm10, the driver will behave like sod on wifi. In cm10.1, infinite wow_suspend requests are issue which heat up and drain battery. I rewrite the whole wow_suspend and wow_resume in cfg80211. BT dowload will not cause the tab hang at sleep now. Hoping the issue is fixed. The test kernel for p6800 is uploading to pre-release. This kernel also work for PA3.50. Please test and report.
13/5/2013:
I'm adding one more release area goo.im. All the previous roms are uploading to goo.im now. OTA with GooManager will be supported shortly. Since goo.im may not be available in some region. I will continue to keep other locations.
7/5/2013:
The new build is uploading to pre-release now. Found a bug in power management of wifi driver. The wakelock duration was set to a very short period. When at sleep, the tab may not have enough time to handle the incoming wifi packets before wakelock time out. Thus infinite number of wakelock is generated. If the packet can be handled eventually, battery is drained. If not, hanging may occurs. Hoping the drain issue is gone now.
29/4/2013:
I have connect my tab to adb logcat for a day. The issue just don't come out! I change the network driver and some of the hardware settings. Don't know if the drain is fixed or not... Need you guys to do a real time test...
Testing kernels with some updates are uploading to pre-release. Support both CM10.1 and PA3.
- Touch screen params. revert to stock values.
- Compass direction fixed
- NTFS_RW enabled
- IP multicast is enabled
- lpm support, hoping to fix autoboot when charger/usb connected in PA3
- improve preview quality of streaming video in rear camera.
20/4/2013:
The Bluetooth headset is fixed!:highfive: That was the last piece of puzzle for bluetooth! It was a tiny bug in the opensource tinyalsa driver cause that. Making a clean build now. Will upload to pre-release after a brief test in a few hours. Latest CWM 6.0.3.1 too. (md5 generation in backup cause reboot, pending to next release)
12/4/2013:
The new heart need another bypass to remove the clot. I rebuild all the three model with the new supercharge kernel. By default, no O/C & U/V are applied. The GPU is boost to 300Mhz. A safe and smooth value. Hoping the laggings are gone. Uploading to pre-release to replace the 8/4 version.
Revise the tested U/V values in FAQ to adapt the new GPU freq.
10/4/2013:
Add the tested U/V values in FAQ.
7/4/2013:
Take a break to build the PA for GT-Plus. Learn more about the device tree & kernel now! Come back with a little bit refreshing. I finally figure out how to overclock the kernel.:highfive: With some degree of undervoltage, add a little bit performance without sacrifying power consumption. Thanks for the Ezykernel from Ezynow. A very good reference for O/C & U/V. With Pimp my rom, I finally got an Antutu value over 10K. :highfive:
Before starting upload, I found quite a few updates from CM. Rebuild again and will upload to pre-release in a few hours.
3/4/2013:
The first phone working p6800 build is uploading to pre-release now. Phone is working fine now! :highfive:
The new tinyalsa in 4.2 is not quite comatible with my Bluetooth. The headset's input pin is not initialize. Need to find a way to fix it. I have enabled the output pin but no way to test it. Anyone has bluetooth speakers, please report.
2/4/2013:
Kernel changes only cover p6800. Rebuilds p6810 & i815 and will upload ASAP.
1/4/2013:
Burying myself into the kernel source for the whole week end, I finally fixed the tinyalsa support in the kernel. :highfive: It was just a tiny change that cause the whole audio input fail! Nearly all apks using audio input, voice search, recorder,etc. are working now. Sadly, the phone.apk issue is not caused by that! For p6810 & i815, I could say all major issues are gone now, please enjoy. For p6800, I have to carry on...
Almost everything is tested. This time no need to put in pre-release.
26/3/2013:
Please forget about the 20130325bt build. I found the last piece of pizzle and fixed the buletooth headset service. Rebuilding all 3 models now. Will upload to pre-release ASAP. :highfive:
The last major issue is Phone.apk which requires another major operation. Please be patient...
25/3/2013:
Working on bluetooth for a whole week. Got stuck! I can scan, pairing and trasfer files but I can't bind it to the Headset service. Upload to the pre-release area to see if anyone has any idea... Sorry, p6800 only for the time being. Don't have enough time to build other models. My antique PC need 3 hrs to complete a build! Really need to upgrade it...
Please report the outcome of other bluetooth devices...
Phone.apk not fix yet. Please don't border to test it. Seems the audio driver for input not working. Searching for manual from ALSA & YAMAHA now...
Someone report transfer limits in Box. Add one more location for pre-release.
22/3/2013:
CWM 6.0.3.0 & CM10.1 10/3/2013 builds released to make room for the coming pre-release.
Further progress in bluetooth, file transfer is OK now. Audio input most likely cause phone FC. Phone apk need serious change or rewritten to work on our Tab...
11/3/2013:
10/3/2013 builds are uploading to pre-release areas..Box may take longer to upload.
There is no significant change in CWM 6.0.2.9 so pending for newer release.
8/3/2013:
My tab is fixed! Yeah!
Ater dumping the first few MB from my tab via the JTAG port. I know what cause my problem now...
It was the dd command I issued earlier to flash the recovery. I must had enter the wrong partition in of=.. I write the data to mmcblk0 instead of mmcblk0p6! I recover those data from my friend's tab. I lost all the data inside but I'm grateful to have it back. This is really the price I have to pay...
This command is extremely dangerous! I should have put it in a script to avoid typing errors. I did it in the terminal apps which is even more dangerous since the software keyboard easily cause typing error... I must had touch the Enter key when I type the letter p. I have done lots of times so I didn't bother to check the terminal window (my second mistake). This is a very good lesson to me... Thanks for those concern and for those teasing (I deserve it!). Really grateful to have you guys around! :good:
5/3/2013:
Working on the kernel for the whole weekend. Hoping to identify the problem of bluetooth and Telephony. Stuck in the latest kernel source! It fail to boot and required a lot of changes. With my friend's tab in hand, I finally managered to correct all the errors and build it out but waste the whole weekend! The lastest cm10.1 builds with the new kernel and other updates from CM is uploaded to the pre-release area. Please test and report.
17/2/2013:
No changes can be made before getting my Tab back... But still want to make myself useful. This is the CM10.1 4.2.2r1 build. Thanks gazjglusk for testing the build for me...
PS. I was told that the software keyboard is hidden by default as pa3.0b1
10/2/2013::crying:My Tab fail to boot this morning, I think my bootloader is corrupted. Not even the Samsung logo and battery icon while charging. I have to send it to the dealer for repairing...Hoping won't put an end to my works
My works:
CyanogenMod 10.2 (4.3.1r1):
http://forum.xda-developers.com/showthread.php?t=2501402
TWRP & CWM Recoveries
http://forum.xda-developers.com/showthread.php?t=2352967
PAC-Man Rom v23.0.0(4.2.2.r1.2):
http://forum.xda-developers.com/showthread.php?t=2330651
ParanoidAndroid 3.68(4.2.2.r1.2):
http://forum.xda-developers.com/showthread.php?t=2139747
CyanogenMod 10.1 (4.2.2r1.2):
● change log:
Code:
[COLOR=Blue]16/7/2013[/COLOR]
- latest source from Official n7000 16/7/2016 build
- 4412 kernel source with s wifi driver
- new ligtht sensor driver with new blobs. lower margin and one more step
- new power driver to fix charging loop at power off
- native NTFS support
[COLOR=Blue]24/6/2013[/COLOR]
- latest source from Official n7000 23/6/2013 build
- Settings update
- kernel-s with some minor bug fixes.
[COLOR=Blue]1/6/2013[/COLOR]
- latest source from Official n7000 30/5/2013 build
- completely new wifi driver and wakelock routines
- wifi data transfer in deepsleep
- better 5G wifi support
- fix a bug in gpu avs voltage table
[COLOR=Blue]17/5/2013[/COLOR]
- latest source from Official n7000 16/5/2013 build
- new wakelock routines for kernel wifi driver
- better support for 5G wifi
- better support for multicast
- lower the wifi power at deepsleep
[COLOR=Blue]7/5/2013[/COLOR]
- latest source from Official n7000 4/5/2013 build
- bug fix in kernel wifi driver
- Touch screen params. revert to stock values.
- Compass direction fixed
- NTFS_RW enabled
- IP multicast is enabled
- improve preview quality of streaming video in rear camera.
- move bluez patches from system core to device tree
[COLOR=Blue]20/4/2013[/COLOR]
- latest source from Official n7000 16/4/2013 build
- bluetooth headset audio fixed
- some debug stuff removed and clean up of kernel see if they cause drain
[COLOR=Blue]12/4/2013[/COLOR]
- kernel fixed release
[COLOR=Blue]7/4/2013 pre-release[/COLOR]
- latest CM10.1 source from Official n7000 7/4/2013 build
- O/C & U/V kernel upto 1.6G (1.8 not stable).
- new io scheduler & pagasusq gov.
- cup entries enabled in performance settings (3rd party setCUP not required)
[COLOR=Blue]3/4/2013[/COLOR]
- latest CM10.1 source from Official n7000 2/4/2013 build
- quite a lot updates from CM's source.
- fix the phone in p6800
[COLOR=Blue]1/4/2013[/COLOR]
- latest CM10.1 source from Official n7000 30/3/2013 build
- new Mali driver in kernel
- fix tinyalsa audio support in kernel
- change on-demand cupfreq.
[COLOR=Blue]25/3/2013 pre-release[/COLOR]
- latest CM10.1 source from Official n7000 21/3/2013 build
- Changes in bluetooth stack
- new SuperUser settings
- New green 3D chaging animation
[COLOR=Blue]10/3/2013[/COLOR]
- latest CM10.1 source from Official n7000 10/3/2013 build
- New su and Superuser.apk
- include Fuse and obb public mount points
- fix Brightness control in Quick Settings
- changes in kernel, try to reduce power consumption.
[COLOR=Blue]3/3/2013[/COLOR]
- latest source from CM's Offical n7000 2/3/2013 build
- lots of changes in kernel
- enabled the performance settings under developer options
[COLOR=Blue]17/2/2013[/COLOR]
- latest source from CM's Offical n7000 16/2/2013 build
- CM10.1 is now 4.2.2r1
[COLOR=Blue]8/2/2013[/COLOR]
- latest source from CM's Offical n7000 build
- lower minium valuse for Brightness, increase autoBrightness steps
- fixes on Contacts.apk and Settings.apk from pa2.55
● know issues:
- all CM10.1 issues
- VoiceDialer not working on bluetooth headset yet.
ParanoidAndroid 2.55cm (4.1.2):
Code:
[COLOR="DarkRed"] ● [B][I] change log:[/I][/B][/COLOR]
[COLOR=Blue] 14/1/2013[/COLOR]
- CM nightly build updates
- increase autoBrightness steps
- fix button misalignment in portrait view
[COLOR="DarkRed"] ● [I][B] know issues:[/B][/I]
- wifi sleep of death. mostly when signal is poor
- built-in wifi tethering doesn't work, may use paTether.apk
[/COLOR]
Downloads
Code:
[COLOR=Green][B][SIZE="4"]
Goo.im:[/SIZE][/B][/COLOR][url]http://goo.im/devs/daniel_hk/rom[/url]
[COLOR="Green"][B][SIZE="4"]Miror:[/SIZE][/B][/COLOR][url]http://www.kuaipan.cn/file/id_39173572073096195.htm#kp|39173572073096197|0[/url]
[COLOR=Green][B][SIZE="4"]Kernels:[/SIZE][/B][/COLOR][url]http://goo.im/devs/daniel_hk/rom/kernel/GT-7.7[/url]
[SIZE=4][COLOR=Green][B]CM10.1 Downloads:[/B][/COLOR][/SIZE]
● [COLOR=Red]24/6/2013:[/COLOR]
p6800: [url]http://d-h.st/7aV[/url]
p6810: [url]http://d-h.st/w19[/url]
i815: [url]http://d-h.st/kQt[/url]
● [COLOR=Blue]1/6/2013:[/COLOR]
p6800: [url]http://d-h.st/yZe[/url]
p6810: [url]http://d-h.st/24D[/url]
i815: [url]http://d-h.st/xR5[/url]
● [COLOR=Blue]17/5/2013:[/COLOR]
p6800: [url]http://d-h.st/hJF[/url]
p6810: [url]http://d-h.st/Ey1[/url]
i815: [url]http://d-h.st/MV8[/url]
● [COLOR=Blue]7/5/2013:[/COLOR]
p6800: [url]http://d-h.st/W6z[/url]
p6810: [url]http://d-h.st/9hQ[/url]
i815: [url]http://d-h.st/NOt[/url]
● [COLOR=Blue]20/4/2013:[/COLOR]
p6800: [url]http://d-h.st/njb[/url]
p6810: [url]http://d-h.st/jDS[/url]
i815: [url]http://d-h.st/w7r[/url]
● [COLOR=Blue]12/4/2013:[/COLOR]
p6800: [URL]http://d-h.st/AsV[/URL]
p6810: [URL]http://d-h.st/VpX[/URL]
i815: [URL]http://d-h.st/GpI[/URL]
● [COLOR=Blue]3/4/2013:[/COLOR]
p6800: [URL]http://d-h.st/mJZ[/URL]
● [COLOR=Blue]1/4/2013:[/COLOR]
p6800: [URL]http://d-h.st/iFX[/URL]
p6810: [URL]http://d-h.st/ywd[/URL]
i815: [URL]http://d-h.st/PH8[/URL]
● [COLOR=Blue]10/3/2013:[/COLOR]
p6800: [URL]http://d-h.st/siT[/URL]
p6810: [URL]http://d-h.st/oa0[/URL]
i815: [URL]http://d-h.st/DYt[/URL]
● [COLOR=Blue]3/3/2013:[/COLOR]
p6800: [URL]https://mega.co.nz/#!ZJxRjBCI!QFP7Jz_hVwxn7xNHTE2vGmBdUIVV8_epA9m6C1iDHMo[/URL]
p6810: [URL]https://mega.co.nz/#!9UZH0ASZ!G85RzUABwhIELdxxcU6iKX8NsHENdQXNdJWw-3mUCPQ[/URL]
i815: [URL]https://mega.co.nz/#!9Jh2HJaa!UNG4gVvkZ7h-CbLO3x37vCW0jrUVEywJJG3YY_dKq94[/URL]
● [COLOR=Blue]17/2/2013:[/COLOR]
p6800: [URL]http://d-h.st/1Kn[/URL]
p6810: [URL]http://d-h.st/4RA[/URL]
i815: [URL]http://d-h.st/cQZ[/URL]
● [COLOR=Blue]7/2/2013[/COLOR]
p6800: [URL]http://d-h.st/Zdt[/URL]
p6810: [URL]http://d-h.st/rfJ[/URL]
i815: [URL]http://d-h.st/QYi[/URL]
[COLOR=Green] [SIZE=4][B]PA2.55cm Downloads[/B][/SIZE][/COLOR]
● [COLOR=Red] 14/1/2013:[/COLOR]
p6800: [URL]http://d-h.st/nFa[/URL]
p6800AROMA: [URL]http://d-h.st/BfR[/URL]
p6810: [URL]http://d-h.st/2XX[/URL]
p6810AROMA: [URL]http://d-h.st/omh[/URL]
i815: [URL]http://d-h.st/M0Z[/URL]
● [COLOR=Blue] 27/12/2012:[/COLOR]
p6800: [URL]http://d-h.st/mrT[/URL]
p6800AROMA: [URL]http://d-h.st/Wxa[/URL]
p6810: [URL]http://d-h.st/oh3[/URL]
● [COLOR=Blue] 7/12/2012:[/COLOR]
p6800: [URL]http://d-h.st/hMG[/URL]
p6800AROMA: [URL]http://d-h.st/CLQ[/URL]
p6810: [URL]http://d-h.st/oen[/URL]
[COLOR=Green] [SIZE=4][B] Support files:[/B][/SIZE][/COLOR]
● PA_Trebuchet.zip: [URL]http://d-h.st/oQX[/URL]
[I]- to activate PA settings for 14/1 non-AROMA version[/I]
● paTether.apk: [URL]http://d-h.st/6ph[/URL]
[I]- to provide basic wifi tethering support for pa2.55[/I]
[I]**AROMA version (gapps included), current versions in [COLOR=Red]RED[/COLOR][/I]
Pre-release ROMs:
**The latest builds for testing. Some may not boot.. Please report after testing
site1:http://pan.baidu.com/share/link?shareid=296833&uk=1512265283#dir/path=/JB ROM
site2:https://mega.co.nz/#F!xRYlwZbY!LZM83QAU4OM8cz7jW0jG5Q
Gapps:
● 20121011 for (4.1.2) pa2.55,cm10: http://d-h.st/06e
● 20130812 for (4.2.2) pa3.x,cm10.1: http://goo.im/gapps//gapps-jb-20130812-signed.zip
● pa_gapps: http://goo.im/devs/paranoidandroid/roms/gapps
Other developers:
BeanStalk
Thanks vaka2
BeanStalk: http://forum.xda-developers.com/showthread.php?t=2599392
CyanogenMod
Thanks locerra & alanorth
CM10.1:http://forum.xda-developers.com/showthread.php?t=2053415
CM10: http://forum.xda-developers.com/showthread.php?t=1816859
ParanoidAndroid
Thanks Androguide.fr
PA2.53: http://forum.xda-developers.com/showthread.php?t=1838391
Source:
kernel & device trees
gitub: https://github.com/danielhk/
Credits:
The Cyanogenmod Team who keep many devices alive!
The ParanoidAndroid Team
locerra & ohanar for his great work on 7.7 devices trees
Androguide.fr for his work on PA for our device
All those who help and donate
Donations:
FAQ
Q: Where is the developer options settings
A: the "developer options" is hidden in 4.2.1 (cm10.1, pa3.0)
to show it in settings:
in:
settings > about
hit the "build number" 7 times (hints will be shown after the 3rd time)
Click to expand...
Click to collapse
Q: How to avoid the emmc brick bug when flashing
A: if coming from stock ics. Here is one of the easier way:
flash the rom (and gapps) in recovery. don't do any factory rest and wiping!
**AROMA version: disable wipe caches option!
reset to recovery again.
do factory reset or wipe data
reset and enjoy!
Click to expand...
Click to collapse
Q: What are the safe U/V values?
A: The margin of voltage tolerance is vary.
I recommend using Pimp my rom (Androguide.fr:good
at Pimp my CPU under the TOOLS:
select VOLTAGE CONTROL
The tested values are from ezykernl :good:. Value lower than that not garantee working.
Freq stock tested safe
1600MHz no value 1300mV 1325mV
1400MHz 1300mV 1275mV 1300mV
1200MHz 1225mV 1200mV 1225mV
1000MHz 1125mV 1100mV 1125mV
800MHz 1050mV 1000mV 1025mV
500MHz 950mV 925mV 925mV
200MHz 950mV 900mV 925mV
Click to expand...
Click to collapse
Greetings, great welcome for the new topic!
Re: [ROM][p6800/p6810/i815] Jellybean Custom ROMs (9/2/2013))
Thanks a lot.
Sent from my GT-P6800 using XDA Premium HD app
Thx a lot!! A Gift for the Year of Snake!!!!
Thx a lot for the great work!!
I have a question about the USB OTG! I tried the OTG cable with usb stick which is working quite well, But once I try the cable with the card reader, the device off after a few second respond.
I did try to use the same cable with the same card reader to the Tab 10.1 with CM 10.1, that is working.
Does it because of the Voltage of 7.7 is lower than 10.1? is there anyway to increase that?
Thanks a lot for your great work!
ATking said:
Thx a lot for the great work!!
I have a question about the USB OTG! I tried the OTG cable with usb stick which is working quite well, But once I try the cable with the card reader, the device off after a few second respond.
I did try to use the same cable with the same card reader to the Tab 10.1 with CM 10.1, that is working.
Does it because of the Voltage of 7.7 is lower than 10.1? is there anyway to increase that?
Thanks a lot for your great work!
Click to expand...
Click to collapse
I think so, there may not be enough current to drive your card reader...
Re: [ROM][p6800/p6810/i815] Jellybean Custom ROMs (9/2/2013))
New CM10.1 builds?!?!?!!!
Sent from my SCH-I535 using xda premium
Re: [ROM][p6800/p6810/i815] Jellybean Custom ROMs (9/2/2013))
So long with no updates for this tablet and now 2 paranoind and 1 cm 10.1 updates which to flash???
Thank you for the updates !!!
Sent from my GT-P6800 using xda app-developers app
hi
I would like to know the wifi\3g\bt working on the PA2.55cm ?
---------- Post added at 01:00 PM ---------- Previous post was at 12:56 PM ----------
and
I would like to know how to flash the PA2.55cm? Odin or?
carlo67 said:
hi
I would like to know the wifi\3g\bt working on the PA2.55cm ?
---------- Post added at 01:00 PM ---------- Previous post was at 12:56 PM ----------
and
I would like to know how to flash the PA2.55cm? Odin or?
Click to expand...
Click to collapse
It's a zip, you have to flash it in recovery.
If you are now in stock ICS, beware of the eMMC bug for bricking. You must replace the kernel before doing a factory reset or wipe.
Goodluck !
daniel_hk said:
It's a zip, you have to flash it in recovery.
If you are now in stock ICS, beware of the eMMC bug for bricking. You must replace the kernel before doing a factory reset or wipe.
Goodluck !
Click to expand...
Click to collapse
ok
I have cm9 on the tablet now. Will I doing a factory reset or wipe.?
daniel_hk said:
It's a zip, you have to flash it in recovery.
If you are now in stock ICS, beware of the eMMC bug for bricking. You must replace the kernel before doing a factory reset or wipe.
Goodluck !
Click to expand...
Click to collapse
Sorry to see that your tab went wrong!I hope it will comes to life soon.
What is this eMMC bug exactly? I never change any kernel when I change from stock ICS to PA.Just root and put the new CW and flash up PA.
carlo67 said:
ok
I have cm9 on the tablet now. Will I doing a factory reset or wipe.?
Click to expand...
Click to collapse
cm9 is ok. you can do a factory reset.
Goodluck !
sbalu said:
Sorry to see that your tab went wrong!I hope it will comes to life soon.
What is this eMMC bug exactly? I never change any kernel when I change from stock ICS to PA.Just root and put the new CW and flash up PA.
Click to expand...
Click to collapse
There are many posts on this subject.
In short:
Some of the Samsung devices (including or 7.7) have bad memory chips inside. The sock ICS kernel include a flag something like EMMC_CAP_ERASE, bad chips will lock or burnt during format (wipe). Androguide and I were also the victims of this bug. I was lucky. The dealer replace the motherboard for me within warranty period.
This time the warranty period was expired...
daniel_hk said:
cm9 is ok. you can do a factory reset.
Goodluck !
Click to expand...
Click to collapse
ok what about google apps ? will I need them?
---------- Post added at 06:29 PM ---------- Previous post was at 06:26 PM ----------
daniel_hk said:
There are many posts on this subject.
In short:
Some of the Samsung devices (including or 7.7) have bad memory chips inside. The sock ICS kernel include a flag something like EMMC_CAP_ERASE, bad chips will lock or burnt during format (wipe). Androguide and I were also the victims of this bug. I was lucky. The dealer replace the motherboard for me within warranty period.
This time the warranty period was expired...
Click to expand...
Click to collapse
am I will be safe come from cm9 ?
---------- Post added at 06:41 PM ---------- Previous post was at 06:29 PM ----------
I have a question
which rom is better for p6800 [PA2.55 or PA3] ?
daniel_hk said:
There are many posts on this subject.
In short:
Some of the Samsung devices (including or 7.7) have bad memory chips inside. The sock ICS kernel include a flag something like EMMC_CAP_ERASE, bad chips will lock or burnt during format (wipe). Androguide and I were also the victims of this bug. I was lucky. The dealer replace the motherboard for me within warranty period.
This time the warranty period was expired...
Click to expand...
Click to collapse
Than is this the right method to avoid brick: "IF COMING FROM STOCK : Do NOT wipe anything, Flash the this rom directly, reboot recovery, then wipe data (factory reset), cache and dalvik, and then Re-Flash this Rom again.This will get you safe from brick."?First time when I flashed to PA I done so, but after that I forgot about it.Fortunately there was no problem so far.Only sometimes (fortunately rarely)PA unknown way go to bootloop when restart it and than only way to get rid of it, to start from stock rom for me.When in bootloop it does not do factory reset even.Thats why I have to flash back to ICS stock to do a factory reset and after that I can do it from the beginning.And what about kernel changes you mentioned?
I wish to avoid motherboard replacement this time for your tab!I curious about it, report please!
carlo67 said:
ok what about google apps ? will I need them?
---------- Post added at 06:29 PM ---------- Previous post was at 06:26 PM ----------
am I will be safe come from cm9 ?
---------- Post added at 06:41 PM ---------- Previous post was at 06:29 PM ----------
I have a question
which rom is better for p6800 [PA2.55 or PA3] ?
Click to expand...
Click to collapse
Yes, you also need gapps to have those basic apps like Play.
The kernel of cm9 has no brick issue. Other custom ICS kernels like EzyICS & Dedrak's are also OK. With them, you can factory reset and flash rom/gapps directly
The easier way is download the AROMA version which has gapps included. You don't have to download it separately.
Goodluck !
sbalu said:
Than is this the right method to avoid brick: "IF COMING FROM STOCK : Do NOT wipe anything, Flash the this rom directly, reboot recovery, then wipe data (factory reset), cache and dalvik, and then Re-Flash this Rom again.This will get you safe from brick."?First time when I flashed to PA I done so, but after that I forgot about it.Fortunately there was no problem so far.Only sometimes (fortunately rarely)PA unknown way go to bootloop when restart it and than only way to get rid of it, to start from stock rom for me.When in bootloop it does not do factory reset even.Thats why I have to flash back to ICS stock to do a factory reset and after that I can do it from the beginning.And what about kernel changes you mentioned?
I wish to avoid motherboard replacement this time for your tab!I curious about it, report please!
Click to expand...
Click to collapse
The first step is to replace the faulty stock ICS kernel.
If you are not in stock ICS or you have already installed a custom kernel, you don't have to flash twice.
I don't know which stock ICS is good or bad. Just don't want to risk.
Factory reset usually wipe /data & /cache
PA or CM rom will write to /system & /boot
stock rom will write to /modem & other partitions too.
standard stock rom is in .tar.md5 format. and each partition is an image which will replace the whole partitions.
if you are in boot loop and can't be fixed by factory reset. There may be something wrong with other partiition(s). By installing stock rom will probably reset it.
As I mentioned before, pa & cm (and most of other custom roms) only touch /system & /boot. When to do factory reset, wiping caches doesn't matter. You may also redo it after rom boot and no need to re-flash rom/gapps.
Although this is not a good pratice, I sometime don't do factory reset when flash new rom. If something goes wrong, I can redo it. When I go from CM10.1 to PA2.99, I didn't do a factory reset. Found out that everything is preserved.
If you don't know what you are doing, play by the book is always the secure way.
A backup in recovery is a MUST if you flash alot.
daniel_hk said:
Yes, you also need gapps to have those basic apps like Play.
The kernel of cm9 has no brick issue. Other custom ICS kernels like EzyICS & Dedrak's are also OK. With them, you can factory reset and flash rom/gapps directly
The easier way is download the AROMA version which has gapps included. You don't have to download it separately.
Goodluck !
Click to expand...
Click to collapse
thanks , so the p6800AROMA: http://d-h.st/BfR is correct one?
daniel_hk said:
The first step is to replace the faulty stock ICS kernel.
If you are not in stock ICS or you have already installed a custom kernel, you don't have to flash twice.
I don't know which stock ICS is good or bad. Just don't want to risk.
Factory reset usually wipe /data & /cache
PA or CM rom will write to /system & /boot
stock rom will write to /modem & other partitions too.
standard stock rom is in .tar.md5 format. and each partition is an image which will replace the whole partitions.
if you are in boot loop and can't be fixed with factory reset. There may be something wrong with other partiition(s). By installing stock rom will probably reset it.
As I mentioned before, pa & cm (and most of other custom roms) only touch /system & /boot. When to do factory reset, wiping caches doesn't matter. You may also redo it after rom boot and no need to re-flash rom/gapps.
Although this is not a good pratice, I sometime don't do factory reset when flash new rom. If something goes wrong, I can redo it. When I go from CM10.1 to PA2.99, I didn't do a factory reset. Found out that everything is preserved.
If you don't know what you are doing, play by the book is always the secure way.
A backup in recovery is a MUST if you flash alot.
Click to expand...
Click to collapse
Where can we find birck safe ICS kernel?My stock ICS is P6810XXLPM_P6810OXXLP1_AUT.zip, that I use to flash.Its from samfirmware.com.May be its kernel is safe, because there was no problem with it, so far.I am an average user, thats why I try to keep what it is in written.Whether what cause bootloops in PA roms?I made TWRP backup, other method was not sucessfully as we discussed it before.I just hope it will work for restore when I need it.
It is worrisome that even such an expert like you can make brick.Sure accidents everytime happen.Do you know already what was led to brick for your tab?
Related
Since I had no permission to post a new thread, so Ive just posted a reply at the following link
from http://forum.xda-developers.com/showpost.php?p=23783120&postcount=1338
wkpark said:
This is forward ported tegra kernel 3.0.8 based on the Nvidia's ODM/NVRM tegra kernel 2.6.32.9
http://github.com/wkpark/tegra-linux-3.0.y
about ~700 commits are cherry-picked from the tegra kernel 2.6.32
almost all commits/commit logs are preserved. some commits are not needed anymore and some commits hard to merge.
anyway this is the result of my effort.
0. prepare android-common repo. it contain's minimal changes for android. the latest mach-tegra tree is removed.
1. about 4~6 hours needed to cherry-pick quick and dirty manually. I can figure out where are the hard parts.
2. fix to make it compile
* add slab.h / remove smp_lock.h / fix .unlocked_ioctl / fix DECLARE_MUTEX etc.
3. apply SU660 patch sets. fix for kernel 3.0.x
4. first try to boot => fail~ :>
5. figure out where are the trouble making points
* timer / irq / gpio / platsmp codes are changed in the kernel 3.0 => dig the log and fix it up
6. at last I can make boot su660 up! (about ~15 days needed to fix to boot up. total 300~400 times retry to boot)
----
the uploaded git repo is rebased interactively (remove some useless history, merge some hunks etc)
and I separate it into three branches
1. tegra-orig-3.0.8 = original android-common + tegra 2.6.32 patch series
- can be used the base of all other nvrm/odm based tegra kernel.
2. su660-lg-usb = tegra-orig-3.0.8 + su660 patches + lg-usb for official firmwares
3. su660-ics = tegra-orig-3.0.8 + su660 patch + ICS touchscreen patch, camera patch by rmcc
currently it works nicely with the SU660
Click to expand...
Click to collapse
and I've made a forward ported P990/P999 kernel based on the lge-kernel-star managed by arcee
(Please see http://forum.xda-developers.com/showpost.php?p=23831782&postcount=1351)
and finally
this is a bootable image for P990(under testing) and P999(not tested at all)
(See also http://forum.xda-developers.com/showpost.php?p=23834645&postcount=1353)
(all for CM9/ICS)
http://code.google.com/p/openstar2x/downloads
this is just first step toward the kernel 3.0
happy hacking~!
P.S.1: I also have forward ported working (but less stable) kernel 2.6.35 (about ~7 days needed to boot up)
this encourage me to forward port kernel 3.0. and this is the result
P.S.2: I'm not related to Nvidia nor LG
ChangeLog
03/20
1. fixed haptic feedback
03/22
1. fixed three annoying kernel WARNING/BUG messages
- irq wakeup warning with gpio-keys
- revert recent cpufreq_stat commit (already reverted in the lge-kernel-star)
- simplified platsmp.c (some parts of platsmp.c already included into the core code)
2. revert some part to original ramdisk.
- emmc/sdcard swap fix (for testing purpose)
- USB vendor ID fix included (for USB tethering)
3. included YAFFS (by vadonka with minor fix)
03/25
1. various minor bugs are fixed by pastime1971 (thanks~)
03/26
1. cleanup reboot/ram_console codes
03/27 (http://forum.xda-developers.com/showpost.php?p=24097273&postcount=243)
1. p99x: fix oops while shutdown (http://forum.xda-developers.com/showpost.php?p=24102050&postcount=249)
2. cleanup cnt32_to_63_clear()
3. [HACK] copy the warmboot information to the original reserved_buffer
area before shutdown.
03/28
1. star: fixup some minor bugs (various compiler warnings are fixed)
03/29 (http://forum.xda-developers.com/showpost.php?p=24181934&postcount=258)
1. star: add CONFIG_STAR_BATTERY_UNIT_UV to support voltage unit in uV
2. su660: adjust star_capacity_from_voltage_via_calculate()
- i think it is not su660 specifc. so Ive just applied it onto the P99x
- use star_capacity_from_voltage_via_calculate() to adjust battery capacity after singular 3G/BB/rild behavior to fix "999%" battery bug.
(there are so many posts exist on this issue e.g. http://forum.xda-developers.com/show...&postcount=211)
Source Code
https://github.com/wkpark/tegra-linux-3.0.y/tree/p99x-ics
Known Issues
* frequently boot fails with the external SD card.
- workaround : remove your external SD card.
Download
for SelfKANG3(by arcee) or it's variants. Owain's CM9 KANG custom rom.
P990
http://code.google.com/p/openstar2x/downloads/detail?name=boot-cm9-for-p990-3.0.8-vib-120320.zip for P990
http://code.google.com/p/openstar2x/downloads/detail?name=boot-cm9-for-p990-3.0.8-120322.zip for P990
P999
http://code.google.com/p/openstar2x/downloads/detail?name=boot-cm9-for-p999-3.0.8-120321.zip for P999 (not tested at all)
http://code.google.com/p/openstar2x/downloads/detail?name=boot-cm9-for-p999-3.0.8-120322.zip for P999 (not tested at all. feel free to feedback)
introduced to the G2X forum by missaellpzchvz - http://forum.xda-developers.com/showpost.php?p=23904261&postcount=1
SU660
http://code.google.com/p/openstar2x/downloads/detail?name=boot-cm9-for-su660-3.0.8-vib-120320.zip for SU660
http://code.google.com/p/openstar2x/downloads/detail?name=boot-cm9-for-su660-3.0.8-120322.zip for SU660
FAQ
Q: Does this mean we will have hardware acceleration anytime soon with ICS? (by der.einstein)
A: No. this is a ODM/NVRM based tegra kernel. all the handicap are same as the kernel 2.6.32
Nice work man!
Sent from my LG-P990 using xda premium
I just can follow owain´s attitude! Your progress on the kernel is really awesome
If you need a tester for your kernels, my smartphone is all time ready.
This sounds great!
Does this mean we will have hardware acceleration anytime soon with ICS?
Sent from my Optimus 2X using XDA
nice , i'll be trying this one out at friday oder saturday , I need the phone to be ready for day to day usage during the week
crazy_dj said:
nice , i'll be trying this one out friday oder saturday , I need the phone to be ready for day to day usage during the week
Click to expand...
Click to collapse
Most is already working. Just wifi is the big problem with this kernel but I think this will be soon fixed cause we have good developers on our side.
Very nice work! man!
works well for a first test, just had one total lockup so far, but who knows if it was even related to the kernel.
i do notice that switching between tasks seems a bit less responsive, even though 2d performance indeed seems a bit smoother.
very good for a first release! hope other devs will join in here soon
Sent from my LG-P990 using XDA
Thanks a lot for this kernel! The phone feels a lot snapier! My Wifi is working without problems but I have one question, is it possible to somehow mount the SD card as the main storage? So basicly like the standard CM Mount.
thx
wkpark said:
Since I had no permission to post a new thread, so Ive just posted a reply at the following link
from http://forum.xda-developers.com/showpost.php?p=23783120&postcount=1338
and I've made a forward ported P990/P999 based on the lge-kernel-star managed by arcee
(Please see http://forum.xda-developers.com/showpost.php?p=23831782&postcount=1351)
and finally
this is a bootable image for P990(under testing) and P999(not tested at all)
(See also http://forum.xda-developers.com/showpost.php?p=23834645&postcount=1353)
(all for CM9/ICS)
http://code.google.com/p/openstar2x/downloads
this is just first step toward the kernel 3.0
happy hacking~!
P.S.: I also have forward ported working (but less stable) kernel 2.6.35 (about ~7 days needed to boot up)
this encourage me to forward port kernel 3.0. and this is the result
FAQ
Q: Does this mean we will have hardware acceleration anytime soon with ICS?
A: No. this is a ODM/NVRM based tegra kernel. all the handicap are same as the kernel 2.6.32
Click to expand...
Click to collapse
I commend the excellent work and thank you so much for this new kernel, but I would love to know why choose a 3.0.x kernel with respect to a kernel 2.xx, I can understand a bit 'but I want better security
Robse86 said:
Thanks a lot for this kernel! The phone feels a lot snapier! My Wifi is working without problems but I have one question, is it possible to somehow mount the SD card as the main storage? So basicly like the standard CM Mount.
thx
Click to expand...
Click to collapse
Yeah, that would be awesome.
Thanks for your hard work.
I don't know exactly where, but there is a guide how to modify fstab to swap mounting just search
Odesláno z mého LG-P990 pomocí Tapatalk
My untrained eye makes me think this thing doesn't touch your vold.fstab.
If that wasn't your question and you actually want to change it, the file is located in \system\etc\vold.fstab and you can edit it with a text editor. Just swap the two lines around. (Aka, point at different targets. Any sensible person could work it out )
Edit: Also, should mention I'm flabbergasted this exists. Excellent work Mr. OP
When i flash this kernel my phone do not recognize my baseband and the battery is showing 999%. What am i doing wrong?
slebit said:
When i flash this kernel my phone do not recognize my baseband and the battery is showing 999%. What am i doing wrong?
Click to expand...
Click to collapse
It would be great if you say to us, which baseband, RIL and ROM you use
Impact7 said:
It would be great if you say to us, which baseband, RIL and ROM you use
Click to expand...
Click to collapse
I use owains kang 26 with 0824 baseband and ril 0824 (V21f, europe).
Sent from my LG-P990 using Tapatalk
slebit said:
I use owains kang 26 with 0824 baseband and ril 0824 (V21f, europe).
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
First, you can install the kernel again. But wipe dalvik cache.
Hope this fix it.
Dekudan said:
My untrained eye makes me think this thing doesn't touch your vold.fstab.
If that wasn't your question and you actually want to change it, the file is located in \system\etc\vold.fstab and you can edit it with a text editor. Just swap the two lines around. (Aka, point at different targets. Any sensible person could work it out )
Edit: Also, should mention I'm flabbergasted this exists. Excellent work Mr. OP
Click to expand...
Click to collapse
I checked this already, nothing changed there! Must be sth. else. Damned I want to use this kernel but all my stuff is on the externel SD card
Impact7 said:
First, you can install the kernel again. But wipe dalvik cache.
Hope this fix it.
Click to expand...
Click to collapse
Already done that, unfortunately it didn't solve it...
Sent from my LG-P990 using Tapatalk
Yes! Very good job indeed!
Very fluid, no wireless problem here, sdcard mounted as usual, I will keep it for a while..
Many thanks! Impressive job.
Hi Folks
I have been trying to solve the msm_hsic_host wake lock problem without introducing the data drop/lockup issues that have been introduced into other kernels by adding the patches from code aurora.
Disclaimer: The usual statements apply, I'm not responsible for your device being bricked, ebola outbreaks, nuclear war, etc... resulting from the use of this kernel, flashing this kernel should be done at your own risk, that being said I have been running various variations of this for the last few days without my phone having any issues.
All Versions now in post 2 below.
What's in this release?
4.2.1 versions: Simply the CM stock kernel pulled from their github here: https://github.com/CyanogenMod/lge-kernel-mako with patches from CAF that I cherry-picked in an attempt to fix the msm_hsic_host wake locks without causing 3G data problems.
4.2.2 versions: Stock AOSP pulled from the android-msm-mako-3.4-jb-mr1.1 repo at https://android.googlesource.com/kernel/msm/ with patches from CAF that I cherry-picked in an attempt to fix the msm_hsic_host wake locks without causing 3G data drops.
What do I do if I get a data drop?
Post here, be as detailed as possible, logs would be extremely helpful so I can see what's going on with your device, because these data drops seem to be somewhat random and don't affect everyone it's very difficult to actually reproduce them on another device on another network, as a result the more information you can give me the better.
My WiFi drops while the screen off resulting in delayed notifications!
To be clear, this is not the same issue, the issue with WiFi disconnecting while the screen off seems to be an Android 4.2.1 issue and exists on all kernels and even different devices running Android 4.2.1, this kernel doesn't do anything to address this issue, whether it fixes it or doesn't is entirely independent of the kernel. A potential fix for this is available from this thread: http://forum.xda-developers.com/showthread.php?t=2072930 Note: It would appear that this hasn't been fixed in 4.2.2 despite Google claiming that it has been, the fixes outlined in that thread still work however. Possible Fix in Post 2
The wakelock is reduced but my battery life is the same or not significantly improved
Well, without these patches the wakelock keeps the phone awake, but if the screen is off and nothing else is going on the kernel is just waiting for the USB bus to suspend so the CPUs are either offline or at their lowest clock speed so they aren't likely using that much power. That being said there should be some improvement in battery life over a 100-0 drain cycle, how much will depend on factors that are mainly not kernel related (time on WiFi, 3G signal strength, apps syncing in the background, etc...).
Wasn't this fixed in 4.2.2? My msm_hsic_host wakelock is way down.
Yes and no, Google took 2 patches that were included in the set I was using on 4.2.1, these two fixes significantly reduced the msm_hsic_host wakelock while on WiFi but not really while on 3G. So, if you use WiFi primarily your msm_hsic_host wakelock will be reduced but if you use your phone primarily on 3G it will continue to be high, though probably lower than it was on the stock 4.2.1 kernel.
Thanks to:
LG - for making such an awesome device
Google - for providing us with the AOSP sources
CyanogenMod - I used their kernel as a base
Code Aurora Forums - for solving the issue
Harsh - for pointing me in the right direction on which CAF patches I was missing
franciscofranco - additional CAF patches that might help
molesarecoming - for the color calibration halfbreed v4 settings.
Koush - the original anykernel format
_motley - the zip file for the anykernel version for N4
jakejm79 - for testing various builds with various patches for me and giving me good feedback
veyka - for testing this build and confirming that he doesn't have data issues with it
socali - for his testing and research on the WiFi delayed notification issue.
4.2.2 Version
Experimental WiFi Fix
Confused about all the fixes floating around? Maybe this will help: http://forum.xda-developers.com/showpost.php?p=40432746&postcount=578
Date: April 15, 2013
Download: hsic_fix_nexus4_wlan_v6.zip
MD5: 8ba0f874efc894c8aaa2e115c5fe2438
See here: http://forum.xda-developers.com/showpost.php?p=40340768&postcount=522
Revert Zip: wlan_revert.zip
MD5: 381013687035626bcb1cbaf609ea431
Note: Flash this if you have flashed any of the WiFi fix versions prior to switching to a different kernel.
Stable Version: (anykernel)
Date: March 04, 2013
Download (any kernel): hsic_fix_nexus4_4.2.2v1.zip
MD5: 17127c1ce03ce0489c49ed7377204a6c
Source: https://github.com/thracemerin/Mako (branch: jb-hsic-rel tag: release-v1)
4.2.1 Version (anykernel)
Date: Feb 04, 2013
Download (any kernel): https://hotfile.com/dl/192620778/4b1c43e/hsic_fix_nexus4_v2.zip.html
MD5: 22be4821f3c16087a04a8084cc0d5703
Source: https://github.com/thracemerin/lge-kernel-mako
Fingers crossed for this, will be testing tomorrow!
With this test kernel I got 11min of hsic wakelock in 11h, which is very simular to what I get on harsh's kernel. (when I was trying it out last night)
I also had no data stuck issue, where as on previous attempts I was always able to reproduce the problem within a few min!
Just to be clear, these patches reduce the hsic wakelock by a lot, while preventing the issue where data would get "stuck", signal would show, but nothing would go in or out.
Edit: as well as fixing the hsic issue, these patches should also reduce power consumption while on mobile data, a general win/win.
Sods law states that the moment we truly have this under control, google will push 4.2.2 with all these fixes anyway
Thanks a lot for bothering todo this!
Sent from my Nexus 4 using Tapatalk 2
Going to give it a try too, thanks for the work mate !
I'm wondering, does the CM team will merge these patches if all work properly ? I don't know the point of view of CM about CAF
Bluewall said:
Going to give it a try too, thanks for the work mate !
I'm wondering, does the CM team will merge these patches if all work properly ? I don't know the point of view of CM about CAF
Click to expand...
Click to collapse
Well, a bunch of the fixes got pushed initially to the CM kernel, but were reverted because of the 3G data stalls, if this works out and 4.2.2 doesn't drop soon or doesn't fix the problem I'd consider resubmitting them to Gerrit, I would want some solid evidence that this works before I go through the trouble however.
Can you please post a flashable zip?
Sent from my Nexus 4 using xda app-developers app
Hi,
It seems to be working.
I have about 6h on battery, 93% left and the msm_hsic_host used 15 m, 4%. No problems with 3g so far.
Firefox17 said:
Can you please post a flashable zip?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'll get on that later today.
In the mean time I had a few mins to repack it for stock, for the moment it's untested (my device is elsewhere atm), if you're brave feel free to try it, I'll post here later when I confirm it works unless someone beats me to it. Update: Confirmed Working
thracemerin said:
I'll get on that later today.
In the mean time I had a few mins to repack it for stock, for the moment it's untested (my device is elsewhere atm), if you're brave feel free to try it, I'll post here later when I confirm it works unless someone beats me to it. Update: Confirmed Working
Click to expand...
Click to collapse
Any kernel version is now in post 2, I've confirmed that it works on CM, but I can't see why it wouldn't work on other ROMs. Big thanks to _motley for the zip file I used.
Indeed I can also confirm this one really works I have tested for a few hours and the results are great.
Thank you
What is the build date of the CM kernel, just so I can match it with the same date nightly
jakejm79 said:
What is the build date of the CM kernel, just so I can match it with the same date nightly
Click to expand...
Click to collapse
1/15 I believe, the anykernel one that works with CM was built on 1/16, either should work on today's nightly as there were no modifications to the ramdisk in the CM repos.
thracemerin said:
1/15 I believe, the anykernel one that works with CM was built on 1/16, either should work on today's nightly as there were no modifications to the ramdisk in the CM repos.
Click to expand...
Click to collapse
Ok thanks, I will test tonight/tomorrow with the 1/17 nightly
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix
On MinCo v6 + Franco kernel r34, the zip is giving me bootloops. Tried twice, once on a fresh install.
Sent from my Nexus 4 using xda app-developers app
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix
spncrmoo said:
On MinCo v6 + Franco kernel r34, the zip is giving me bootloops. Tried twice, once on a fresh install.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Franco's kernel uses a non stock ramdisk which I gather from other threads is only compatible with his kernel, you will probably have to either flash the stockboot.img from here or use one of the reset kernels floating around the forums before flashing this.
Sent from my Nexus 7 using Tapatalk 2
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix
I haven't tested it fully yet but it really looks like I'm finally getting a normal deep sleep.
Sorry if this post is ignorant, but I just started using CyanogenMod for the first time having gotten a Nexus 4, and I'm not 100% familiar with it yet.
I've flashed your kernel and it is working great with no wakelocks, but will updating to the latest nightly flash the stock CyanogenMod kernel again? meaning I would to reflash yours? Not that it would be a problem given that I have the flashable zip, but just for future reference as to whether I need to reflash your kernel every time I update for nightlies.
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix
Yes you have to reflash everytime you flash a nightly.
Same here, seems to work great, good job !
Welcome to the EternityProject!
What do we have here?
CM10.2-EPRJ --- Or... EternityProject's CyanogenMod 10.2 for LG Optimus 4X!
What's the point in using CM10.2-EPRJ?
It contains various optimizations made at compile time. Moreover, it isn't being compiled with the default Android toolchain, but with a custom one that better handles and optimizes the code.
The CM10.2-EPRJ package will also automatically install our EternityProject Kernel 3.4.37.
Recommendations:
Patience is virtue.
Can I use a non-EternityProject Kernel on CM10.2-EPRJ?
For now, it's possible. Absolutely.
Features:
- All the standard CM10.2 Features are enabled
- New, custom toolchain for improved code optimization and better performance
- More to come
ROM Changelog:
Code:
20131007:
- CM repos synced
- New EternityProject optimizations (OMGFAST!)
- Featuring latest revision of EPRJ kernel 3.4
20130813:
- CM repos synced
- Mobile data is stabler
20130811:
- Stabler baseband
- External SDCard now accessible from file managers
- MTP finally working
20130810v2:
- Stability enhancements for Stagefright
- Other misc performance improvements
20130810:
- Synced with CM repos
- Smoother UI
20130808v2:
- Modified EPRJRIL recovery prop
- EternityProject RIL Recovery is now enabled by default.
- Trials to solve some people's problem with baseband
20130607:
- Sync'ed with CM repos on 07/06
- Added further EternityProject optimizations
- Solved Camera FC issue
- First try for solving the mobile data crash
20130602:
- First release.
Note: If you want to see the stock CM changelog, it's located at http://review.cyanogenmod.com/
How-To:
1. Copy the CM10.2-EPRJ and GApps packages on your internal memory
2. If you aren't coming from a previous version of CM10.2-EPRJ, wipe data and cache
3. Flash CM10.2-EPRJ, then flash GApps
4. Reboot
5. Enjoy!
Notes:
1. If you're looking for the Developer Settings menu, tap on "build number" N times (CM will say you when it's done)
2. This ROM doesn't work with CM10.1 kernels
3. (Temporary) If you want working SU/root: become developer (tap "Build number" 7 times in Settings > About phone), go to "Developer options" in settings and set "Root access" to "Apps and ADB".
So, what to download?
Everything is located on my website!
EternityProject's CyanogenMod 10.2 for LG Optimus 4X HD --- Click me!
Hey, and what about GPL?
Search on my GIT: Gitorious and/or EternityProject self-hosted GIT
Enjoy your "new" device!
The EternityProject Team Manager & Main Developer,
--kholk
many thanks dude,cant wait to try
AW: [ROM] EternityProject's CyanogenMod 10.1 for LG Optimus 4X HD
Thank you, nice job
Re: [ROM] EternityProject's CyanogenMod 10.1 for LG Optimus 4X HD
Wow! Can't wait to try this rom. Thanks kholk.
Sent from my LG-P880 using xda app-developers app
Awesome
R: [ROM] EternityProject's CyanogenMod 10.1 for LG Optimus 4X HD
Thanks man..!!! It's time to to unleash the Beast!!!
Sent from my LG-P880 using xda premium
Awesome ! Many thanks
OMG it's coming:victory:
Thx God Kholk :good:
Just one (silly??) question, stock recovery or CWM Recovery by Dexter for the Wipe ?
Use the CWM by Dexter for EVERYTHING prior and while installing CM10.1-EPRJ.
And I want to make something clear prior someone to complain...
....the package is a freshly compiled "untested" version. Everything should work like the one I'm running right now on my O4X, but anyway, I'd prefer for ONE of you to test it prior making it totally public.
Is there anyone brave enough to test and eventually KDZ back?
I just want to make sure I'm releasing the right one.
@ musklor
is it really necassary to quote his whole post,makes things messy
kholk said:
Use the CWM by Dexter for EVERYTHING prior and while installing CM10.1-EPRJ.
And I want to make something clear prior someone to complain...
....the package is a freshly compiled "untested" version. Everything should work like the one I'm running right now on my O4X, but anyway, I'd prefer for ONE of you to test it prior making it totally public.
Is there anyone brave enough to test and eventually KDZ back?
I just want to make sure I'm releasing the right one.
Click to expand...
Click to collapse
i'm willing to test:victory: but if it works why do i have to KDZ back?
I'm 99.9% sure it works, but I want to make things safe, so I want to eliminate that 0.1% of doubt.
friartuckme said:
@ musklor
is it really necassary to quote his whole post,makes things messy
Click to expand...
Click to collapse
OOps sorry, post edited.
kholk said:
I'm 99.9% sure it works, but I want to make things safe, so I want to eliminate that 0.1% of doubt.
Click to expand...
Click to collapse
if testing is as simple as flashing the build and reporting back what works and what doesn't, I'm in:fingers-crossed:
where is the download link
@tomanlam
I sent you the link for downloading and testing.
I will make it public once you tell me it's working
I can test, I have all the stuff at work to make a kdz back.
I can also test it... Cuz it's hard to wait
Suspense.....
Preface:
This is a custom 3.0.8 kernel developed for Android Jellybean 4.x and build for multiple Sony 2011 devices
It is based on CAF kernel and is kept as clean as possible while maintaining working hardware
Other Android versions are also bootable, but are not widely tested
Features:
Pure CAF 3.0.8 kernel
Full hardware support
Defaults:
IO scheduler: ROW
Requirements:
Unlocked bootloader
Fastboot
Install:
Backup
Download the kernel file for your device from the list that follows and flash it:
adb reboot bootloader
fastboot flash boot
fastboot reboot
Now you should be seeing the coolest kernel boot animation
Downloads:
3.0.8
anzu
Uninstall:
Flash back to stock using SUS or flash another kernel
Notes:
TODO
Sources:
The linux kernel is GPL'ed, everyone who does modifications should make them publicly available.
I accept patches any way possible. Basically I only read pms if they contain some suggestion or patch Credits go to the author obviously
https://github.com/nobodyAtall/msm7x30-3.0.x-nAa
Donate:
If you are enjoying my work please consider donating:
Donations are voluntary but allow me to spend more time on this device.
Disclaimer:
I can't be held responsible if this Kernel bricks your device or makes it explode in your hands! Use it at your own risk!
Changelog:
jb_chocolate:
TODO
ics_chocolate:
3.0.8-nAa-03 (6/5/03) @0f00b041b19c0b4a1eb
- Rebased on ics_chocolate branch
- Devices: smultron, coconut, haida, hallon, iyokan, mango, urushi, anzu, satsuma
- anzu: not undervolting display
- Increased pmem for hdpi devices
- leds: hardcode max_current
- leds: regrant users access to leds' real safe max current
- anzu: fix ALS
- cpufreq: ondemand and interactive governor fixes
- msm7x30: overclocking implementation - performance is greatly improved
3.0.8-nAa-02 (28/4/03) @566249c116bbb
- Devices: smultron, coconut, haida, hallon, iyokan, mango, urushi, anzu
3.0.8-nAa-01 (23/4/03)
- Test build for 3.0.8 for community feedback
- Devices: smultron, coconut, haida
Full feature changelog:
https://github.com/nobodyAtall/msm7x30-3.0.x-nAa/commits/ics_chocolate-nAa-master
...............
Only see release 02. Assume it is still uploading?
What has been changed since 02 release?
thank you and all the developers they work on this
to keep our old devices alive
:good: :good: :good:
Thanks! :beer:
Everything is working fine for me except for video recording, I am using Arc S + CM10 (fxp218)
Wi-Fi: OK
Bluetooth: OK
Video: When I press record, it hangs then I press record again then it will stop working.
Someone please try this, I may have flashed something.
Can someone report about 3.x kernels performance? Does JB work smoother? I'm interested in this since I exspected a performance boost. Can't test myself since I have no pc/laptop with me atm
danielstar13 said:
Everything is working fine for me except for video recording, I am using Arc S + CM10 (fxp218)
Wi-Fi: OK
Bluetooth: OK
Video: When I press record, it hangs then I press record again then it will stop working.
Someone please try this, I may have flashed something.
Click to expand...
Click to collapse
You installed release 02. Seems like the 03 release is not posted yet.
EDIT: 03 release now posted. Flash again and post findings.
stock
does this work on stock?
because doomlord reported that it was working on stock
thanks!
Oh! New version of kernel! But, I hope i can use it on ICS
Is this kernel usable on cm10.1 from shufu?
TheGreatSega said:
does this work on stock?
because doomlord reported that it was working on stock
Click to expand...
Click to collapse
it boots and doesn't FCs, but screen messed up.
if the screen is fixed, maybe we could explore more.
I still have the problem on video recording, im using 03. and the brightness got higher.
Another Bug: Bootlogo messed up, just trying on CM10.1 rel. 0505
Edit: Kernel does not boot with CM10.1, switching back
rofl022 said:
Another Bug: Bootlogo messed up, just trying on CM10.1 rel. 0505
Click to expand...
Click to collapse
Ive tried several times on cm 10.1 05 with 3.0.8 03+, latest release. It's stuck on kernels logo. Sbdy confirm this? Edit: Confirmed - not working for now.
One4EV3r said:
Ive tried several times on cm 10.1 05 with 3.0.8 03+, latest release. It's stuck on kernels logo. Sbdy confirm this?
Click to expand...
Click to collapse
Same here, as I wrote above.
No love for the iyokan ?
One4EV3r said:
Ive tried several times on cm 10.1 05 with 3.0.8 03+, latest release. It's stuck on kernels logo. Sbdy confirm this?
Click to expand...
Click to collapse
+1 tried 4 time
thnx for this relase,no problems so far on fxp 218 cm10
Featuring a new cpufreq interface, AbyssplugV2, intelliplug and a whole host of new additions that are not available in any other kernel for the x3.
Among them are updates only found in this kernel, saner defaults via config, better optimizations for the actual code and a rewritten version of devfreq.
It also have an updated baseband configuration and built in rather than to keep a module as it makes no sense to have a vital function as a module.
https://bitbucket.org/mourta/liquid_kernel_lge_p880-stable/
Kernel: http://www.mediafire.com/download/viy5a3dtaccd0gm/mourta-stable-08-23.zip
If there is a request for it i also have a ROM available based on grouper blobs, AD optimizations and a build around this kernel with a new dev tree.
For kernel install, it's anykernel, you can install it on any custom ROM, for stock and the lastest updates you will have to head over to Modaco and my original thread.
Note that this is a one time release, if you like it you'll have to head over to modaco to get updates.
it should be noted that the recommended settings is using intelliplug (you may need to use kernel tweaker or trickster mod for that if you're not running my ROM, and abyssplugv2, i also recommend ROW for a sheduler and Westwood for your congestion handling.
Note that you can now overclock to any frequency and it will feed the GPU chip with the needed volatage, this is great for cooking a roast beef but not for any practical use.
Quadrant scores are 8k and the last Antutu was at 16487, no overclocking but you won't reach that without using my ROM.
And with that... i'm done.
Thanks to the IODAK, Fransico, Adam77Root, Faux123 and others that provided code and/or input.
Oh, what I see here? The awesome kernel I'm testing with @ottomanhero and lucaarx and the great dev and friend @IcanhasLG coming back on xda? Let's rock hard&heavy, right now!
peppethustra said:
Oh, what I see here? The awesome kernel I'm testing with @ottomanhero and lucaarx and the great dev and friend @IcanhasLG coming back on xda? Let's rock hard&heavy, right now!
Click to expand...
Click to collapse
We'll see how this goes.
Thankfully i am in touch with a mod that will keep this drama free,
And for anyone wondering, peppethustra is head of my testing crew, you get stable releases because of them.
It should be noted that i'm still going to prefer the forum that greeted me over the one that shunned me from the get go, updates here will be sporadic at best but on time on the other forum.
It's great to see your work on XDA.Now everyone can experience your awesome work
P.S. you can find neccessary links in my signature
Great work, running your kernel now.
But Iodak was not updated since long ago and its sources does not contain many great fixes from cm11 kernel.
Thats why Demetris relased Cyodak kernel in Android development section. It's Iodak brought up to date with latest cm 11 kernel .
It would great to see Muorta Kernel based on Cyodak instead of old Iodak. We would have your exclusive features with up to date cm11 kernel upgrades. But maybe you already upgraded iodak's source, let us know
FunkyRasta said:
Great work, running your kernel now.
But Iodak was not updated since long ago and its sources does not contain many great fixes from cm11 kernel.
Thats why Demetris relased Cyodak kernel in Android development section. It's Iodak brought up to date with latest cm 11 kernel .
It would great to see Muorta Kernel based on Cyodak instead of old Iodak. We would have your exclusive features with up to date cm11 kernel upgrades. But maybe you already upgraded iodak's source, let us know
Click to expand...
Click to collapse
Obviously, the real necessary updated patches have been implemented yet ("continuation" means this, too), so it's not necessary nor in Mourta's plans to base it on cyodak (which really isn't the only way to find updated code for our device)
peppethustra said:
Obviously, the real necessary updated patches have been implemented yet ("continuation" means this, too), so it's not necessary nor in Mourta's plans to base it on cyodak (which really isn't the only way to find updated code for our device)
Click to expand...
Click to collapse
That's what I wanted to know, as OP didn't explicitly stated it. Thanks
FunkyRasta said:
That's what I wanted to know, as OP didn't explicitly stated it. Thanks
Click to expand...
Click to collapse
Outdated sources never are a good base for developing a fresh new kernel or ROM, if there is a new compatible code implementation ready to be merged into the code That's the first thing a good developer checks (and if you can, look at Mourta's bitbucket linked in the OP to view his commits, there will be all the principal news about new code implementations)
Tried this but I loose my modem every now and then and the screen won't wake sometimes.
baxtex said:
Tried this but I loose my modem every now and then and the screen won't wake sometimes.
Click to expand...
Click to collapse
Go to Modaco and find newer version (26/8/2014) . It will resolve problems like yours
Okay will do.
How's the deep sleep ?
Written from my Optimus 4X powered by Omni 4.4
LGaljo said:
Go to Modaco and find newer version (26/8/2014) . It will resolve problems like yours
Click to expand...
Click to collapse
this version, according to trickster mod, does not use deep sleep state and still screen won't wake up sometimes. so i dropped it for now.
greetings
peter
peter_altherr said:
this version, according to trickster mod, does not use deep sleep state and still screen won't wake up sometimes. so i dropped it for now.
greetings
peter
Click to expand...
Click to collapse
Can you give more info about your ROM, kernel settings, setup etc. and provide a logcat if possible? That's a rare issue you're having there.I've used my phone for 20 hours now, (%3 battery left) and it slept for about 15 hours, same version.
I suggest you to try flashing the kernel twice.I had such problems with iodak kernel back in the time and flashing it twice had fixed the deep sleep issue.
ottomanhero said:
Can you give more info about your ROM, kernel settings, setup etc. and provide a logcat if possible? That's a rare issue you're having there.I've used my phone for 20 hours now, (%3 battery left) and it slept for about 15 hours, same version.
I suggest you to try flashing the kernel twice.I had such problems with iodak kernel back in the time and flashing it twice had fixed the deep sleep issue.
Click to expand...
Click to collapse
+1
@peter_altherr And more important thing: have you at least wiped cache and dalvik before flashing the kernel? If yes, try wiping system partition too (no factory reset, you can leave /data partiton intact) then reflash ROM, gapps and kernel, and see how it goes..wait 3 or 4 minutes before trying to wake up device, after the first boot, and deep sleep would start without problems
I have tried the 26/8 version but that still gives me RIL problems, I get no signal whatsoever. I cannot grab a logcat as I need my phone to work right now but I'm Running latest beanstalk version.
baxtex said:
I have tried the 26/8 version but that still gives me RIL problems, I get no signal whatsoever. I cannot grab a logcat as I need my phone to work right now but I'm Running latest beanstalk version.
Click to expand...
Click to collapse
Wait for next version, great changes will come even about this issue
@peter_altherr you should unplug it from charger and try unplugged.
when charging cpu never reaching deepsleep.
@ whoever had freeze/sod problems with last kernel version: a new fixed release has been uploaded (it's a minor release: reverted GPU OC, which was causing the problem). Check official thread for the download link
my phone does not see SD card with 0902
and yes im 100% sure its kernel problem....recovery sees my sd, and so iodak kernel