Related
jdivic and me made a fix for wakeup lag on AUO panels but it needs more testing. We tested it on two devices with AUO panels and the wakeup lag should be reduced to the level of sharp ones.
I have attached the diff file and CWM update zip with modified Rafpigna 1.9OC kernel (non GB).
If you currently use Rafpigna kernel please try this version and report back.
Please report the wakeup time and type of panel.
Type of panel can be found with:
Code:
adb shell
dmesg | grep "Board id"
Tytung test kernel:
http://forum.xda-developers.com/showpost.php?p=16740691&postcount=23
Disclaimer: We are not responsible for any kind of damage to your phone or software installed. Use this kernel at your own risk.
mdebeljuh said:
jdivic and me made a fix for wakeup lag on AUO panels but it needs more testing. We tested it on two devices with AUO panels and the wakeup lag should be reduced to the level of sharp ones.
I have attached the diff file and CWM update zip with modified Rafpigna 1.9OC kernel (non GB).
If you currently use Rafpigna kernel please try this version and report back.
Please report the wakeup time and type of panel.
Type of panel can be found with:
Code:
adb shell
dmesg | grep "Board id"
Disclaimer: We are not responsible for any kind of damage to your phone or software installed. Use this kernel at your own risk.
Click to expand...
Click to collapse
thats realy great! but can it be flashed to typhoon rom with tytungs kernel?
Nice idea, will test
I don't think so, but for real I don't know. This is Raf's kernel for froyo, and is built for test purposes. If it will be confirmed working, I'm sure that tytung, raf and other kernel builders will incorporate our changes in their new bulids.
make it for clk GB and u got me as tester
WOW man! It works! Thank you guys.
As in screen wake up?
I'm running an AUO panel;
<4>[ 1.526947] panel type is 1 :board id is 4 : AUO
but on typhoon CM7 . . . . any chance you could compile for that build, I would think there are a lot of typhoon users who would appreciate this
mdebeljuh said:
jdivic and me made a fix for wakeup lag on AUO panels but it needs more testing. We tested it on two devices with AUO panels and the wakeup lag should be reduced to the level of sharp ones.
I have attached the diff file and CWM update zip with modified Rafpigna 1.9OC kernel (non GB).
If you currently use Rafpigna kernel please try this version and report back.
Please report the wakeup time and type of panel.
Type of panel can be found with:
Code:
adb shell
dmesg | grep "Board id"
Disclaimer: We are not responsible for any kind of damage to your phone or software installed. Use this kernel at your own risk.
Click to expand...
Click to collapse
Pretty excited about this, but I cant test as im using tytungs kernel
mdebeljuh said:
jdivic and me made a fix for wakeup lag on AUO panels but it needs more testing. We tested it on two devices with AUO panels and the wakeup lag should be reduced to the level of sharp ones.
I have attached the diff file and CWM update zip with modified Rafpigna 1.9OC kernel (non GB).
If you currently use Rafpigna kernel please try this version and report back.
Please report the wakeup time and type of panel.
Type of panel can be found with:
Code:
adb shell
dmesg | grep "Board id"
Disclaimer: We are not responsible for any kind of damage to your phone or software installed. Use this kernel at your own risk.
Click to expand...
Click to collapse
Hey , nice news.
Is there any possibility to do the same for tytung's kernel ?
Or would reading the diff help doing the same/similiar with tytung's kernel ?
thank you zz
speedyracer5 said:
Pretty excited about this, but I cant test as im using tytungs kernel
Click to expand...
Click to collapse
Can you tell me which version of tytungs kernel are you using. Tomorrow I will try to make a modified tytungs kernel.
Sent from my HTC HD2 using XDA App
probably http://nexus-hd2.googlecode.com/files/kernel_tytung_r10_update.zip
btw. What rom are you using, If I may know ?
zz
bender_007 said:
probably http://nexus-hd2.googlecode.com/files/kernel_tytung_r10_update.zip
btw. What rom are you using, If I may know ?
zz
Click to expand...
Click to collapse
Old one but stable MarkinuX HD 1.7.1
Sent from my HTC HD2 using XDA App
like people say "If it ain't broken, don't fix it"
Last question , what do you think how long will it take you to try to fix the same @ tytung's kernel
note that 99 % new roms are on "tytung's kernel v10"
If you need beta testers I think there are plenty of them here, including me.
Should be possible to "update" the kernel via cwr then.
thx for you effor. Hvala
zz
bender_007 said:
like people say "If it ain't broken, don't fix it"
Last question , what do you think how long will it take you to try to fix the same @ tytung's kernel
note that 99 % new roms are on "tytung's kernel v10"
If you need beta testers I think there are plenty of them here, including me.
Should be possible to "update" the kernel via cwr then.
thx for you effor. Hvala
zz
Click to expand...
Click to collapse
It is not difficult, I only need to download his sources, apply the patch and compile the new kernel. The problem is that i can't test the kernel.
Sent from my HTC HD2 using XDA App
bender_007 said:
like people say "If it ain't broken, don't fix it"
Last question , what do you think how long will it take you to try to fix the same @ tytung's kernel
note that 99 % new roms are on "tytung's kernel v10"
If you need beta testers I think there are plenty of them here, including me.
Should be possible to "update" the kernel via cwr then.
thx for you effor. Hvala
zz
Click to expand...
Click to collapse
I think it is one of the oldest part of the code, and I think it is just the same in all kernels, so, change to tytung kernel... it would take more time to pull the git repository and to compile it then to apply the change ...
Someone PM tytung into this thread
leaskovski said:
Someone PM tytung into this thread
Click to expand...
Click to collapse
I wanted to, but can't send him PM...
hehe
thx for quick response
looking forward to try this, although my screen is pretty responsive. Not on some rom's .
EDIT: well, if it's worth something to you, there are plenty of people here to test it )
zz
Thanks to mdebeljuh and jdivic.
I will compile a test kernel.
Presenting the latest development version of the TeamWin Recovery Project's touch recovery for the HTC Wildfire S. TeamWin Touch Recovery now has official builds available through TeamWin and GooManager for the Marvel. With any luck MarvelC support will soon follow. Please visit the TWRP and TeamWin pages for more information.
Compiled for and tested on the original GSM Marvel. Always awaiting more testing from CDMA Marvel users. This software is provided without support or warranty: use it at your own risk.
Known Issues:
Fails on a handful of new GSM Marvel devices with updated/incompatible hardware, locking at the initial HTC splash screen.
Change Log:
XX:XX XX/8/2012 - Initial release of TWRP v2.2.2.0: Upstream code changes resolve the issues with formatting SD-EXT and partitioning the SD-Card. Includes the initial release of a revised 320x480 default theme with cleaner action pages, slightly larger buttons and more spacious checklists. First stable, full-featured and issue free release of TWRP for the HTC Wildfire S. Previous buggy versions have been removed from the revision history and can no longer be downloaded.
17:35 19/08/2012 PDT - Second release of TWRP v2.2.1.5: Issues with offmode charging resolved thanks to kalaker.
23:32 17/08/2012 PDT - Initial release of TWRP v2.2.1.5: Upstream code includes changes that resolve issues with the system rebooting during backup operations.
03:00 06/08/2012 PDT - Initial release of TWRP v2.2.1.4: Upstream code includes a handful of nice little bug fixes including a resolution for the mount issues.
23:05 05/08/2012 PDT - Minor aesthetic tweaks to the new theme.
02:29 05/08/2012 PDT - Third release of TWRP v2.2.1: Includes a carefully scaled v2.2 theme enabling the latest release's advanced features.
22:59 28/07/2012 PDT - Second release of TWRP v2.2.1: Corrected a glitch in my build environment that could have lead to issues and then forked it for dedicated platform builds. First dedicated MarvelC build.
23:58 27/07/2012 PDT - Initial release of TWRP v2.2.1: Compiled from the most recent code provided by: TWRP, Cryptomilk and the CyanogenMod ICS-Release branch.
22:55 09/07/2012 PDT - Maintenance release of TWRP v2.1.8: Reconfigured and shrank the kernel in order to utilize a less aggressive form of compression than LZMA. Switched from the CyanogenMod ICS branch to ICS-Release.
12:35 09/07/2012 PDT - Initial release of TWRP v2.1.8: Built using the ICS branchs of the CyanogenMod and Cryptomilk Marvel sources. Oversized image required LZMA compression.
To Do:
Build flashable .ZIP
Download Links:
TWRP for GSM HTC Wildfire S (Marvel) v2.2.2.0 (Preview Release) - Image - Mirror
MD5: 34f201ec8c8b0f0d2eae64c88ac3d888
TWRP for CDMA HTC Wildfire S (MarvelC) v2.2.2.0 (Preview Release) - Image - Mirror
MD5: 7c4d137a37098900ff3b2a9412ee8994
This is not the place for support.
I apologize in advance for what may seem abusive but, as it has been laid down here in the RULES it stands to reason that I'm decently covered.
THIS IS NOT THE PLACE FOR YOUR QUESTIONS! THIS IS!
In my infinite generosity I've created a place where users can get answers to frequently asked questions and seek support from one another. As an added bonus it will save you from my wrath. Please limit all discussion in this thread to development issues. I've started you off with some installation instructions as that was the first issue. I will update and check in as necessary. Enjoy!
You need to have the HTC drivers installed.
Then in cmd type:
fastboot flash recovery recovery.img.
Place the img file in the same folder as the adb files, so you won't have to specify a path.
Good luck,
Awesome work btw. :laugh:
WoefulDerelict said:
I apologize in advance for what may seem abusive but, as it has been laid down here in the RULES and I CLEARLY stated there would be ABSOLUTELY NO SUPPORT in my original post, it stands to reason that I'm decently covered.
THIS IS NOT THE PLACE FOR YOUR QUESTIONS! Ignorance and stupidity will not be tolerated.
In my infinite generosity I've created a place where users can get answers to frequently asked questions and seek support from one another. As an added bonus it will save you from my wrath. I've started you off with some installation instructions as that was the first issue. Enjoy!
Click to expand...
Click to collapse
If you're not going to support this, then this dosent belong in the Dev section... it can go in the General section or Apps section. Only Supported work belongs in the Dev section.
He means he wont be answering any questions in this thread.............he created another thread for discussion in the general section
Semantics...
Red5 said:
If you're not going to support this, then this dosent belong in the Dev section... it can go in the General section or Apps section. Only Supported work belongs in the Dev section.
Click to expand...
Click to collapse
I believe the issue here is entirely one of semantics. In my lexicon support encompasses the magical realm of end-user hand holding. In no way do I feel it is necessary or reasonable to expect a user manual with warm and fuzzy walk-troughs of every possible thing you could want to do and some friendly advice with a hug every time the user has a problem with their FREE software. I certainly don't plan to offer any of the above.
I do; however, plan on maintaining my work. I'm quite interested in information that would allow me to improve the image or resolve a reproducible issue. I also have no qualms discussing the work with other developers, providing updates as the code base evolves, accepting proper issue reports or feature suggestions. I'd simply prefer to avoid getting bogged down by questions that could easily be answered by visiting the project's home page or querying Google. I find it quite counter productive to wade through user prattle when I'm trying to fix an issue or collaborate with another developer.
Hello.
Is this recovery version work on Marvel with black CWM Recovery effect (new graphics hardware) ??
I'm not sure what you're asking.
marchelius said:
Hello.
Is this recovery version work on Marvel with black CWM Recovery effect (new graphics hardware) ??
Click to expand...
Click to collapse
This should be compatible with any HTC Marvel based Wildfire S. I believe they are all based on the same SOC. The kernel should have support for all MSM7227 based graphics hardware.
WoefulDerelict said:
This should be compatible with any HTC Marvel based Wildfire S...
Click to expand...
Click to collapse
Should be, but it isn't. After flash, my phone stuck on white screen with green HTC logo after attempt to enter in recovery...
Works perfectly on my phone. Mine is the A510e.
The joys of platform fragmentation.
marchelius said:
Should be, but it isn't. After flash, my phone stuck on white screen with green HTC logo after attempt to enter in recovery...
Click to expand...
Click to collapse
SomeDudeOnTheNet said:
Works perfectly on my phone. Mine is the A510e.
Click to expand...
Click to collapse
I suppose the plus side is that I have some confirmation that the software works on other A501e devices. If you're going to report something as not working could you at least go to the trouble of including your device's identifying information? A510b/e, SPL and Radio versions would be a great start.
WoefulDerelict said:
I suppose the plus side is that I have some confirmation that the software works on other A501e devices. If you're going to report something as not working could you at least go to the trouble of including your device's identifying information? A510b/e, SPL and Radio versions would be a great start.
Click to expand...
Click to collapse
OK.
HTC A510e
Android 2.3.5
EQDKP v4.7
Kernel 2.6.35.10-ga66971c
47.23e.35.3038H_7.57.39.10M
S-ON, unlocked via HTCDev
Main branch broken with CM9 on Marvel since updating to 2.2 code.
TWRP updated their main branch to v2.2 today. While I was hoping for the resolution of current issues their changes break my build with CM9. I'm stepping through the changes presently to see if I reason out what changed between 2.2 and 2.1.8 to cause the issue and correct the it. Stay tuned for more updates.
More please...
marchelius said:
OK.
HTC A510e
Android 2.3.5
EQDKP v4.7
Kernel 2.6.35.10-ga66971c
47.23e.35.3038H_7.57.39.10M
S-ON, unlocked via HTCDev
Click to expand...
Click to collapse
Could I get the HBOOT, MICROP and Radio version from your SPL? Hold the volume rocker and power button down while turning on the device to access the bootloader for that information.
IF these Frankenstein devices exist I'm going to need a profile of the revised hardware in order to correct the issue along with some proud owners to test fixes as I don't have access to one. The Marvel I was given is based off the original hardware profile and TWRP2.1.8 works fine when built with CM9 and the cryptomilk.org MSM7227 kernel. I'll do what I can to fix it but, I'm currently trying to resolve build issues with the new 2.2 release. I'm hoping this new code base along with a revised kernel will resolve many of the current issues.
It's ALIVE!
The problem is it's behaving like I brought it to life with a couple bolts of lightning. To say that it has issues would be overly kind but, it boots and I can navigate around. I'm currently trying to track down all the shorts making 2.2 twitch. Stay tuned.
Fresh revision.
Finally managed a clean build from the latest source. I'd love for some brave MarvelC users to give it a test before building a flashable .ZIP for the general public.
WoefulDerelict said:
Finally managed a clean build from the latest source. I'd love for some brave MarvelC users to give it a test before building a flashable .ZIP for the general public.
Click to expand...
Click to collapse
Thanks but theres a few issues
1. Theme isn't updated
2. On-screen keyboard wont work due to current theme
3 l. Swipe to start backups/restoring wont work due the theme.
More or less this is just like the previous twrp until themes are resized etc
Sent from my Wildfire S A510e using Tapatalk 2
Yea, I knew that.
eoghan2t7 said:
Thanks but theres a few issues
1. Theme isn't updated
2. On-screen keyboard wont work due to current theme
3 l. Swipe to start backups/restoring wont work due the theme.
More or less this is just like the previous twrp until themes are resized etc
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
This was already noted in the original post as the last entry under the known issues header. I maintain this for a reason. Thankfully the themes are XML based and updating it shouldn't be ridiculously difficult. Once I've gotten the issue list stable and nailed down where they are all rooted I'll see what I can do to tackle this and the formatting errors as they seem to be the largest TWRP specific issues I could correct. I wager the XML theme business will be relatively quick and painless.
WoefulDerelict said:
This was already noted in the original post as the last entry under the known issues header. I maintain this for a reason. Thankfully the themes are XML based and updating it shouldn't be ridiculously difficult. Once I've gotten the issue list stable and nailed down where they are all rooted I'll see what I can do to tackle this and the formatting errors as they seem to be the largest TWRP specific issues I could correct. I wager the XML theme business will be relatively quick and painless.
Click to expand...
Click to collapse
Yeah the themes are XML based but the image editing will be the worst part
Sent from my Wildfire S A510e using Tapatalk 2
eoghan2t7 said:
Yeah the themes are XML based but the image editing will be the worst part
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
I'm trying to imagine that being easy. I'm not totally inept in Adobe or AutoCad products so I'm sure I can toss together something in a week or so. Depends on how much the real job needs my time and brain meats.
FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!
Credits:
MoltenMotherBoard!
Downloads:
MoltenMotherBoard mirror | AndroidFileHost
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
Changelog:
Nightlies
Code updates
20140928
Huge sources cleanup
Code updates
20140205
Mobile Data finally fixed from scratch (DNS correctly load properties and read correct iface)
Added support for arabic languages
Code updates
20131210
Included workaround for DNS (this should partially fix Mobile Data)
Included few UI sounds (this fix lock and unlock not-working audio effect)
Code updates
20130618
Adjusted RIL signal strenght indicator
Fixed RIL
Fixed Automatic Time Zone
Gapps updated to 2013.06.14
Fixed Browser issues
Fixed Bluetooth issues
Fixed Camcorder issues
Added SU binaries
Added Superuser
Added init.d support
Included Gapps by default
Code updates
20130606
Added FM Radio support
First release
Issues:
-----
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): p4c0
Review of the ROM:
Speed: The ROM is very fast and has no lag issues, it's the fastest rom I've ever had!
Antutu score on normal settings (800 MHz) is 3765!
It only has google's apps (nothing from Samsung), so it's very lightweight!
RAM usage only 60-70 MB!
Battery: Simply great, I can easily get through the day with normal usage because it's so lightweight!
Bugs: None found so far, tell me if you find any
Recommended tweaks: "[MOD]Disable CPU rendering/Full GPU rendering/Improve the performance of your GPU" makes scrolling a little bit smoother
Tell me if you know more or better tweaks for this rom!
If you want something added in this list please tell me!
LordJeremy said:
Thanks for the ROM, was looking for this!
I found a bug: FC when importing contacts
BTW, don't you want to add root access in the rom?
Click to expand...
Click to collapse
Dude, I only shared my first booting release!
I'll spend these days to improve it!
mackief said:
Dude, I only shared my first booting release!
I'll spend these days to improve it!
Click to expand...
Click to collapse
No problem, take your time.
Just wanted to help out a little.
Good luck with your works!
LordJeremy said:
No problem, take your time.
Just wanted to help out a little.
Good luck with your works!
Click to expand...
Click to collapse
Please, dude, for every issue you face in this rom, make a logcat and post it help. You'd be so helpful!
Actually , if you are reffering to importing contacts from .vcf , that works , for me at least.
Root doesn't work
bogdanwp said:
Actually , if you are reffering to importing contacts from .vcf , that works , for me at least.
Click to expand...
Click to collapse
And what make Contacts forcing close? :S
Desmaize38 said:
Root doesn't work
Click to expand...
Click to collapse
Root not included yet. You'll have it in next release!
Persian does not support
Not on the menu
Not on Keyboard
??
If you have a problem with us?
monaliza142003 said:
Persian does not support
Not on the menu
Not on Keyboard
??
If you have a problem with us?
Click to expand...
Click to collapse
No problem with you, Google made it, not us.
We're only porting it.
Anyway, describe me what you need, and I'll try to help you
Mh why is there a changelog already posted? Is the current next update being uploaded or something?
Desmaize38 said:
Mh why is there a changelog already posted? Is the current next update being uploaded or something?
Click to expand...
Click to collapse
The upper changelog (compared to last update) is the actual changelog, that will be active in next release.
How does it look like?
The same as cm7?
lukas12153 said:
How does it look like?
The same as cm7?
Click to expand...
Click to collapse
As stock GingerBread (because it is stock) just check how nexus one on gingerbread looks like
Its blazingly rom!
EvilKing009 said:
Its blazingly rom!
Click to expand...
Click to collapse
Ah yes also i forgot in my last post that it's faster than stock & cyanogenmod
MoltenMotherBoard said:
For general discussions, bug reports and FAQ, write HERE!
Credits:
MoltenMotherBoard!
Click to expand...
Click to collapse
Seems great! Really glad someone did this necessary step for our device! Hope I can test it soon! :laugh:
Yep i +1 with the extreme speed , to bad about not having so many options to play with but hey ... it is AOSP and it is Gingerbread after all
I checked it and I don't like it but for sure it's for this who like clean Android and I can say one, it's really fast and very light,
ps when ROM has no File manager how in other way we can install apk's?
WYPIERDAALAAC said:
I checked it and I don't like it but for sure it's for this who like clean Android and I can say one, it's really fast and very light,
ps when ROM has no File manager how in other way we can install apk's?
Click to expand...
Click to collapse
install one from google play.
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
Some hints:
1. Be sure you are on latest CWM or TWRP recovery!!!!!!
2. Not all gapps packages right now are nice working. You can try others but at least I know that the one linked here is working. If you have other gapps which are working you can link it here of course
3. Full wipe when coming from any 4.3 or 4.4 rom (as well format system manually please)
Reporting Bugs
When you submit a bug you want to make sure that nothing from your side is causing it. Otherwise your developer might be hunting a bug which doesn't really exist.
The best way to achieve this is by doing the following.
1. Make a nandroid backup.
2. Perform a full wipe (factory reset + wipe /system)
Now we have two different ways depending on what kind of problem you're having.
3a. When you're having a problem with a ROM function, flash just the ROM without GAPPS etc. and boot back into the system. You will boot directly onto the homescreen.
3b. When you're having a problem with a 3rd party app in combination with our ROM then flash the ROM and GAPPS.
Boot now back into the system. You will boot to the setup wizard.
Log in to your Google account but make sure that you untick "Restore from my Google Account to this phone/tablet".
Finish the setup and open the playstore and download only the app you're having problems with.
4. Start a logcat recording and reproduce the bug (if possible more than once) while taking the logcat. If you don't know how to get a logcat read this tutorial or this.
5. Post the logcat in a txt file (this is important because you otherwise clog up the threads with your log) in the correct thread.
Please also write detailed description how we can reproduce the bug.
6. Restore your backup from point 1 and wait for a fix (don't ask for ETAs).
Wifi works?
Reserved for me
Inviato dal mio Galaxy Nexus
Well done!!
google account manager working?
Is there are download link? Or am I missing something?
Vekhez said:
Is there are download link? Or am I missing something?
Click to expand...
Click to collapse
Op is currently making the download link in post 2.Please read next time
Sent From The Third Nexus
Omar1c said:
Op is currently making the download link in post 2.Please read next time
Sent From The Third Nexus
Click to expand...
Click to collapse
Lol, my connection only loaded half of the OP. calm down.
wifi works yes
google account manager no idea....you see to me
kufikugel said:
wifi works yes
google account manager no idea....you see to me
Click to expand...
Click to collapse
Saved my bandwidth just for kitkat.
You'll see a Bug report soon :good:
I'll try gapps as soon as the download finish
Inviato dal mio Galaxy Nexus
SiriS_CaC said:
Saved my bandwidth just for kitkat.
You'll see a Bug report soon :good:
Click to expand...
Click to collapse
I guess i have some testing to do lol
grtz from the crazy bastard from holland powered by supernova
Big thanks
is there some error in update-script??? or it is only me?
EDIT: fixed and booting... new bootanimation is awesome..
jeetBLswami said:
is there some error in update-script??? or it is only me?
EDIT: fixed and booting... new bootanimation is awesome..
Click to expand...
Click to collapse
whatdya do?
I just stole the boot.img and flashed that ontop of the other ROM.. but I would prefer the legit thing.
jeetBLswami said:
is there some error in update-script??? or it is only me?
EDIT: fixed and booting... new bootanimation is awesome..
Click to expand...
Click to collapse
I'm getting Status 7. Some metadata error. Tried re-downloading. How'd you solve it?
I'll try a different updater-script.
tommrazek01 said:
I'm getting Status 7. Some metadata error. Tried re-downloading. How'd you solve it?
Click to expand...
Click to collapse
I'm getting a status 7 too....
i have just changed the updater-script with previous builds
This thread is being consolidated. Please click on this link to go to the unified DevDB thread.
Thread is closed at OP's request..
shutdown while charging
Hi
I have a issue with the last kernel for my S3
When I'm charging my phone and I shutdown the device. I get the battery screen for somes seconds then I have the kernel splash screen and the led is not flashing anymore.
To turn on the device I have to unplug the charging cable first, otherwise the device vibrate once and the slash screen is back.
How can I fix it ?
Thank you
Hello
I have tested
KT747-AOSP-KK-D2LTE-10-14-2014+v2
it appears built in Torch for AOSP is broken.
I am using Gummy M4 Rom. on Galaxy S3 SGH-T999v
can confirm torch is working before installing kernel.
Other torches from playstore appear to be working.
When using liquid smooth 3.0 or slimkat 7.0 the 10/14 kernel has no APNs ...clean install on both of factory reset and /system format
Thread consolidated
This thread is being consolidated. Please click on this link to go to the unified DevDB thread.
Thread is closed at OP's request..