Can anyone explain to me why the netflix app doesn't work on this ROM. Nothing ever gets displayed. AOKP on droid 4 latest build.
Sent from my XT894 using xda premium
Are you on one of the ICS leaks, or still have a Gingerbread "unsafe" system?
The Gingerbreak/ICS frankenROMs don't have hardware acceleration working properly (due to mismatched kernel). Thus Netflix, Chrome, Opera and anything else like that won't work.
Yeah I have gingerbread/aokp installed right now. So it sounds like I can't have a non safe system, just the ics leak installed. Is that correct? I still can't deside if I want to flash the ics leak or not. AOKP is nice and all with all its extra features, but for whatever reason, they cannot get data to work. Its pretty ridiculous they still don't have 3g/4g working after several months. Should i just go ahead and flash the ics leak?
It really isn't their fault, it is because the kernel is locked. AOKP-based off of the leak (as opposed to the Frankbuilds based on GB) work much better.
I finally jumped to the leak and atm I'm actually using the stock leak and am pretty happy with it. That being said, if you move to the leak you have to be ok with the fact that you might be off the upgrade path forever. The chance of that happening looks to be pretty small, but nobody can rule it out...
I understand its not AOKP's fault. The stuff they are pulling off is pretty advanced. Its just very frustrating from a users end trying to get data to play nice. I dont want to go to stock ICS because I really love the features AOKP has thrown in. And I dont wont to be off the upgrade path either. So will AOKP ever have solid data or are they going to have to take the stock ICS kernal and build a new AOKP ROM from that?
whiteout7942 said:
I understand its not AOKP's fault. The stuff they are pulling off is pretty advanced. Its just very frustrating from a users end trying to get data to play nice. I dont want to go to stock ICS because I really love the features AOKP has thrown in. And I dont wont to be off the upgrade path either. So will AOKP ever have solid data or are they going to have to take the stock ICS kernal and build a new AOKP ROM from that?
Click to expand...
Click to collapse
Bottom line is: a locked Bootloader prevents developers from providing a proper Kernel to the device. So, you don't get the HW codecs with a Gingerbread based ICS ROM, therefore no Netflix. If you install any of the leaked ICS builds, Netflix runs just fine (I can confirm)
I guess Motorola says that it's to protect us "in the name of security", but nobody seems to realize that the root exploits in themselves, already breaks that so called "security", so why not just let us have an unlocked bootloader!
Hopefully with the Google acquisition, someone can revisit that policy, and clarify to us users what it actually means. Moto probably loses customers over that policy.
bgarlock said:
revisit that policy, and clarify to us users what it actually means. Moto probably loses customers over that policy.
Click to expand...
Click to collapse
This^
You CAN have a safe system with the ICS leaks installed. You just have to use the Safestrap v 2.00 and ICS Leak build of aokp. AFAIK Netflix and HW Acc. codecs work with the new ICS leak builds!
Sent from my DROID4 using xda premium
zPacKRat said:
This^
Click to expand...
Click to collapse
I would say they lose some of the die hard users, who *need* to have an unlocked boot loader. Just reading through other posts, I have seen many get so frustrated at the fact that Moto won't unlock the boot loader, that they say they won't buy moto products because of it.
I'm just thankful that people have found loopholes that allow us work arounds, but it certainly adds a lot of complexity, that wouldn't be necessary if they would just unlock the boot loader (as they said they would do).
I get Moto's stance that they need to provide support, and if people are loading custom overclocked kernels, it could certainly cause HW damage, if the chip is running at a speed out of specs, but why not have the users sign something giving up that warranty, so they can do with their devices as they wish.
I'm just saying I think they should reconsider their policy of locked boot loaders, and open up their phones to hacker enthusiasts. Heck, Jelly Bean has been announced, and most phones still don't have ICS! I would bet an unlocked boot loader would have gotten ICS into the hands of users much faster, and in this instance where there is a ICS ROM, but a GB kernel, it would actually provide for a much better user experience.
moah909 said:
You CAN have a safe system with the ICS leaks installed. You just have to use the Safestrap v 2.00 and ICS Leak build of aokp. AFAIK Netflix and HW Acc. codecs work with the new ICS leak builds!
Sent from my DROID4 using xda premium
Click to expand...
Click to collapse
OK now I'm confused. I've been using the aokp builds for a while and they are the ics build 40 then the date. I've been flashing those for a long time but data is just as bad if not worse on some builds. Can someone explain why even though I have the ics leak, data is still screwed up? I was told data was much better on these builds.
whiteout7942 said:
OK now I'm confused. I've been using the aokp builds for a while and they are the ics build 40 then the date. I've been flashing those for a long time but data is just as bad if not worse on some builds. Can someone explain why even though I have the ics leak, data is still screwed up? I was told data was much better on these builds.
Click to expand...
Click to collapse
Nevrmind figured it out
Sent from my XT894 using xda premium
Related
This was the tweet fromCvpcs!!! (We haz a booting "true" AOSP system with 0 blur! http://www.youtube.com/watch?v=PPqfIRZP7Mc Still very buggy but I'm working on it)
Sent from my DROIDX using XDA App
booyah! let get er done!
Sound like good news!
Still, could anybody explain what AOSP boot means? Will this enable us to boot a custom kernel on the x?
I have no idea what this means except 100% no blur sounds awesome!
AOSP essentially means it was built completely from source. Not built based on Moto's own build with their custom framework (blur) crap. It is a true complete Vanilla rom.
Android Open Source Project
http://source.android.com/
So they got an AOSP rom to run using the stock moto kernal? Because obv we can't change kernals at this point yet
Sent from my DROIDX using XDA App
If they got an aosp to run they should be able to modify the kernel no? Thought that was the while point of the exploit nenolod is working on.
Sent from my DROIDX using Tapatalk
this is too awesome.
Joe92T said:
So they got an AOSP rom to run using the stock moto kernal? Because obv we can't change kernals at this point yet
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No, from my limited understanding, this isn't using the Stock Kernel. They've figured out a way to get NVRAM into Engineering Mode..
Someone correct me if I'm wrong.
vonfeldt7 said:
No, from my limited understanding, this isn't using the Stock Kernel. They've figured out a way to get NVRAM into Engineering Mode..
Someone correct me if I'm wrong.
Click to expand...
Click to collapse
This AOSP has actually been running for a while now. Its being developed by cvpcs, the same guy who's been developing the Sapphire roms for Droid. I don't know if he's using the recent exploit that has made the rumor-mill lately. He claims its a true AOSP boot, which implies a custom kernel compiled from source. However, for all we know he could still be using the Moto 2.2 kernel, but replaced everything else in user space with fresh, compiled code.
Either way, its interesting. Despite Motorola's best attempts, it looks like the Droid X (and Droid 2 by implication) will soon be free of its eFuse prison, allowing us users the choice of what to run on this device.
We won't be getting rid of eFuse, as it's hard coded into the silicon itself in NVRAM, as I understand it. Its just that folks are working on getting the keys to the prison .
hi guys,
i am sniffle, a member of the CCRoms Team that produces Sapphire(Droid 1), Ruby(HTC Incredible), Obsidian(Droid X), Emerald(HTC Evo)
to clarify a few things.
this does NOT utilize the bootloader hack, it is a custom boot setup that initializes the boot process a second time to load the custom rom after the bootloader has ran all of its checks. It technically could be considered a second boot setup as it does initialize the boot process a second time.
it does NOT use a custom kernel, it uses the stock kernel, since the bootloader is not locked. the process to actually be able to use this rom is quite involved. When we are ready to release, there will be detailed instructions for flashing. If you aren't comfortable with ADB, terminal executions this rom will not be for you.
i will try to explain more as the questions come up, but for the most part that's all there is to say... other than to say that more is broken at this point than fixed. as more news comes available i will let you guys know.
sniffle said:
hi guys,
i am sniffle, a member of the CCRoms Team that produces Sapphire(Droid 1), Ruby(HTC Incredible), Obsidian(Droid X), Emerald(HTC Evo)
to clarify a few things.
this does NOT utilize the bootloader hack, it is a custom boot setup that initializes the boot process a second time to load the custom rom after the bootloader has ran all of its checks. It technically could be considered a second boot setup as it does initialize the boot process a second time.
it does NOT use a custom kernel, it uses the stock kernel, since the bootloader is not locked. the process to actually be able to use this rom is quite involved. When we are ready to release, there will be detailed instructions for flashing. If you aren't comfortable with ADB, terminal executions this rom will not be for you.
i will try to explain more as the questions come up, but for the most part that's all there is to say... other than to say that more is broken at this point than fixed. as more news comes available i will let you guys know.
Click to expand...
Click to collapse
Thank you guys for your hard work, I am sure that most of the community is as excited as I am to see your work make it to the X. I love the boot ani from the video, and even though this is my first android phone the things Ive read about your teams previous releases has me EXCITED for this to hit.
appreciate your update and clarification, sniffle!
OMG, aosp 2.2 for my droidx would be awesome. Nice to set someone working on it, props and kudoes.
Sent from my PC36100 using XDA App
i hear this is almost 100% working!
LT1UltraZ said:
i hear this is almost 100% working!
Click to expand...
Click to collapse
Heard the same this morning. Very excited!
dogswind said:
Heard the same this morning. Very excited!
Click to expand...
Click to collapse
Would love a source on this info.
Almost 100% is a bit too strong of a descriptor, there are still some major bugs like rebooting on sleep(hitting the power button to turn the screen off) and a few others on top of that. With our next sapphire and Ruby release we will be making the latest build publicly available for other development to help figure out a fix for these problems.
I know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel
EDIT: i meant leaks, stupid typo
The kernel is based on GB because of the locked bootloader. At least that's how I am to understand it. In other words I think that the custom ROMs can be improved using the leaked ROMs but they'll still have to remain based on the GB kernel. Unless you update your stock system to ICS that is. I think the biggest thing devs should focus on right now is a way to safely upgrade to ICS where downgrading is possible in order to stay on Verizons official upgrade path.
As it stands, the OTA will look for GB 219 when upgrading so those early adopters won't be able to get future upgrades. Unless devs find a way to downgrade or trick the update that is.
Everything I've said could be wrong however this is how I have come to understand it.
Sent from my DROID4 using XDA
Given that we have the fastboot files can't we just wipe and flash that to downgrade?
Sent from my DROID4 using XDA
azrael293 said:
Given that we have the fastboot files can't we just wipe and flash that to downgrade?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
No, this results in a brick. Fastboot refuses to flash older partitions over new ones.
Sent from my XT894 using xda premium
flamefangahs said:
The kernel is based on GB because of the locked bootloader. At least that's how I am to understand it. In other words I think that the custom ROMs can be improved using the leaked ROMs but they'll still have to remain based on the GB kernel. Unless you update your stock system to ICS that is. I think the biggest thing devs should focus on right now is a way to safely upgrade to ICS where downgrading is possible in order to stay on Verizons official upgrade path.
Click to expand...
Click to collapse
This is why you need kexec - you can load the ICS kernel dynamically, without corrupting your GB install.
Sent from my DROID4 using Tapatalk
highlandsun said:
This is why you need kexec - you can load the ICS kernel dynamically, without corrupting your GB install.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Actually, upgrading to ICS leak is probably the way to go. We can now upgrade from leak 200 to 206, giving us the ability to stay on the upgrade path. Since the XDA forums are dead for the Droid 4, I suggest everyone keep up at droidforums.
Here are the instructions for upgrading from leak 200 to 206:
http://www.droidforums.net/forum/droid-4-roms/209619-get-unstuck-ics-leak-200-aka-upgrading-200-206-instructions.html
Also, I believe Hashcode is working on bringing Safestrap 2.0 to the new ICS leak based on the new kernel, and will be working on getting our ROMs on the new kernel as well.
rumgool said:
Since the XDA forums are dead for the Droid 4, I suggest everyone keep up at droidforums.
Click to expand...
Click to collapse
droidforums is about as dead for the Droid 4 as is XDA. I am really surprised how little interest people have in this phone. I guess I am one of the few that still loves physical keyboards. Only drawback on this phone is the non-removable battery. Otherwise it is rock solid. Had the original Tilt, then TP and TP2. Had the G2 on T-mobile, but reception on that phone was not good and T-mobile Network in the US sucks.
GermanGuy said:
droidforums is about as dead for the Droid 4 as is XDA.
Click to expand...
Click to collapse
This is true, I was just mentioning since most of the recent information regarding the ICS leak has been on droidforums so checking it out would fill everyone in on whats going on. Because basically development for the GB kernel is probably going to come to a halt and future development will be based on the new ICS kernel, including the existing AOSP ROMs.
wait, the 206 version keeps you on the upgrade path?
dewhashish said:
wait, the 206 version keeps you on the upgrade path?
Click to expand...
Click to collapse
No, but 206 was supposed to require 219 as 200 did and the official one will and people have found ways around it.
Sent from my XT894 using xda premium
I have Hashcode's stuff running on my kindle fire. We will all be in for a treat once he starts focusing on D4. He's done really really good work on the kindle.
dewhashish said:
I know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel
EDIT: i meant leaks, stupid typo
Click to expand...
Click to collapse
They won't be able to do so. What they will be able to do is make their builds work off/with the new kernel/radios flashed by the leak.
So Hashcode will have two builds.
1) - works on phones running the current stock GB kernel.
2) - works on phones running the leaked ICS kernel.
There is still a locked bootloader so you can't flash unsigned kernels/boot.img. For the leaked "system" files to help you need the ICS kernel. The only way to get the ICS kernel is to flash the leak.
So the leaks are great news for people wanting an AOKP or CM9 build running fully functional....on their leak installed phones. Not much help for those who do not want to flash the leak.
I'll definitely flash the leak once root has been released for 4.0.4 (in case OTA rootkeeper doesn't work) and hashcode releases safestrap 2.0 for the leak.
I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.
So far it's working great, face unlock and the camera is working perfectly and GSM/WDCMA performance is awesome, I don't seem to have the problem of under-reported GSM signal like in the stock MotoBlur leak.
(Note that I'm in Canada and using Bell Mobility, not in the US on Verizon so I can't say if LTE is functioning properly).
I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
Won't be long before Hashcode puts up an official release, but I definitely recommend trying it out if you're up for it. If Hashcode doesn't mind, I could share a .zip of the build I made if anyone out there is interested.
Sent from my XT894 using xda premium
Rick#2 said:
I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.
Click to expand...
Click to collapse
Do you think you create a guide or go into more detail how you did this? I'm not quite sure what their git is.
Sent from my XT894 using xda premium
Rick#2 said:
...
I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
...
Click to expand...
Click to collapse
This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.
Sent from my Amazon Kindle Fire using Tapatalk 2
Hashcode said:
This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire
Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?
podspi said:
If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire
Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?
Click to expand...
Click to collapse
Right now, I'm treating the front buttons like they are a special portion of the touch screen (basically any touch past 960 pixels down is considered the "button row", and then I divided the width up into 4 spots for button presses: menu, home, back and search respectively. (This is in the recovery itself as well as the splashscreen which triggers off of menu)
If that fails, Ill just use hard keys for D4's Safestrap temporarily.
Sent from my DROID4 using Tapatalk 2
..or maybe the volume buttons (I bet it requires less modification than implementing support for the digitizer)
I just put up an updated Droid4 2.00 Safestrap for use w/ the new MotoICS leaks:
http://forum.xda-developers.com/showthread.php?t=1688610
BE SURE TO MAKE AN INITIAL BACKUP OF NON-SAFE SYSTEM BEFORE YOU DO ANYTHING.
You will use the "System" backup to restore back to stock .206 to update later.
I have the D4 CM9 / AOKP builds for the MotoICS leaks almost ready and I'll post those soon.
Hey Everyone, I have been pushing the ICS update away, kind of scared of all the bugs. But I'm wondering if theirs any decent Jelly Bean ROMS? With working Data (4G?) and Camera / Video?
I'm not expecting anything perfect, darn bootloader..
I don't think the bootloader is a concern at this point. A bunch of smart and dedicated developers have managed to get past that on the D3/D4/Bionic/RAZR. Now the difficulty is getting a kernel that works well. Anyway, to answer your question, no. It is a WIP ATM.
Yeah I don't really blame the bootloder, making a joke.
How can I download, learn more, keep track of the w.i.p.s? I know hashcode says stuff over twitter, which is probably keeping track of part. Though I don't understand twitter tweets replys.
And do I need to be on the new ICS update to flash them (with Safestrap 2?)
And whats a kexic build over a rom, or are they the same? differences? I know the kexic stuff is going pretty well.
TechTinker said:
Yeah I don't really blame the bootloder, making a joke.
How can I download, learn more, keep track of the w.i.p.s? I know hashcode says stuff over twitter, which is probably keeping track of part. Though I don't understand twitter tweets replys.
And do I need to be on the new ICS update to flash them (with Safestrap 2?)
And whats a kexic build over a rom, or are they the same? differences? I know the kexic stuff is going pretty well.
Click to expand...
Click to collapse
Hashcode's twitter feed is probably the best/only way to keep tabs on kexec right now.
You do need to be on stock ICS in order to use safestrap 2.11 which is needed to flash the newer ICS builds as well as the kexec builds.
Kexec refers to the kernel as opposed to the ROM. So you have ROMs right now that run off the stock phone kernel and you have kexec ROMs which run off the custom kexec kernel.
Droid 4 - AOKP Skyline
By any way is it possible that LG will upgrade it to JB, or is possible for xda developers to upgrade current stock ICS to JB?
Sent from my LG-P990 using xda app-developers app
CM10.x is JB...
LG's junk isn't needed and therefore it isn't even worth asking/waiting for. We finally got all we wanted from them, now enjoy CM10.
I think the best way for us is using CM10 ROM, such as in this post: http://forum.xda-developers.com/showthread.php?t=2058231
Just a tip. When you're upgrading to CM10 you should have installed CM7 at some earlier point. Easy fix for the SD card bug. Took me half a day to find this out.
Plus use new ICS bootloader, it fix slow charge and minimize call bug
Custom40 said:
LG's junk isn't needed and therefore it isn't even worth asking/waiting for. We finally got all we wanted from them, now enjoy CM10.
Click to expand...
Click to collapse
Well if we didn't have "LG's junk" RC wouldn't have been able to build CM10 as it is now
All you need to build a perfectly good JB ROM without any JB update are device-specific ICS source code and an unlocked bootloader. JB and ICS are still very much the same under the hood, much like the case with Froyo and GB. Back in those days you could also build GB ROMs out of Froyo sources I believe (the O2X got CM7 quite some time before its official GB update arrived).
CM10 is as good as JB can get on our device. I believe the only JB-specific feature we don't have is true vsync, aka no Project Butter, but that's not a deal breaker as it's hardly noticeable.
If you look at recent news, no OEM wants to bring JB to a 512 MB RAM device because their stupid skins like Sense/Touchwiz/LG UI eat up so much memory that allocating more for vsync would make performance atrocious. The only exception is the Nexus S simply because it doesn't have that bloat to deal with.
My problem is with CM10 I can not have 3G calls, FM radio, Polaris office etc.
fundoosite said:
My problem is with CM10 I can not have 3G calls, FM radio, Polaris office etc.
Click to expand...
Click to collapse
Use stock ics if you want those features
Sent from my LG-P990 using Tapatalk 2
I believe we will get a stable cm10 later.
better than any stock rom
i want to go back to ics. the jelly bean downsides are becoming a pain right now. what exactly would happen if i just reflashed with ics stock? will it brick and will it be recoverable? can anyone explain in depth the issue regarding this? or will i have to put my phone up for sale and obtain a replacement that still has ics?
the jb performance has been cool but i had everything working perfectly on ics. and the jb update is just significantly less than perfect for my setup and app needs. serves me right for rushing for the latest update i guess. but ive got to go back to ics. jb reminds me of windows millenium edition.
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
Sorry you aren't enjoying the upgrade. I'll throw out the obligatory suggestion of performing a factory reset on your phone if you haven't already done so since the upgrade. This will allow your phone to clear out old ics data and use pure jb. However, for some people, updates truly do kill their experience and that's a personal thing.
With official updates from Motorola, our devices also receive a new kernel in addition to a new version of android. JB uses a newer kernel than ICS, just as ICS used a newer one than Gingerbread. Unfortunately, because our devices have locked bootloaders, you cannot go back to the ICS kernel, meaning you can not downgrade. Trying to fastboot back will result in a brick, most likely permanent.
At this point, you would need to get a replacement still running ICS if you truly want to downgrade. Alternately, considering using custom roms, which at this point are all JB based, but far superior to the Motorola "Blur" version found on stock phones.
Sorry!
Sent from my XT894 using Tapatalk 2
thanks. looks like this d4 is going up for sale. i did the factory resets when i did the update. but some apps i really like dont work on on jb. id designated them lifelong companion apps. so jb being unable to run them means jb has got to go. my d4 completely suited my needs untilt this update. now it's incomplete. and without moto allowing the bootloader to be unlocked means athe d4 was just destroyed by this update imho.
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
Have you thought of emailing the app developers and asking them to update them to support JB?
Any and every new phone coming will be based on JB so that limits you to buying older, unsupported devices which will make newer apps as they come out unavailable to you.
thanks but i dont NEED anything else. this thing is totally unreliable. its not storing profiles and settings in some apps so i have to readd login details etc every time i launch the program, others forceclose to homescreen after launching without an error.
i thought about the email option.. but thereve been so many ppl clamouring about them since last summer im not putting any hope on that. i think they really screwed up with jb and took a few steps backwards. unfortunate but this d4 has got to go. cant sell it fast enough right now.
im really happy with the d4. dont see any need to upgrade for the next 10 yrs. great phone/multifunction device. ill buy 3 and keep em on ics with backup parts etc for repairs.
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
The Magician Type 0 said:
Sorry you aren't enjoying the upgrade. I'll throw out the obligatory suggestion of performing a factory reset on your phone if you haven't already done so since the upgrade. This will allow your phone to clear out old ics data and use pure jb. However, for some people, updates truly do kill their experience and that's a personal thing.
With official updates from Motorola, our devices also receive a new kernel in addition to a new version of android. JB uses a newer kernel than ICS, just as ICS used a newer one than Gingerbread. Unfortunately, because our devices have locked bootloaders, you cannot go back to the ICS kernel, meaning you can not downgrade. Trying to fastboot back will result in a brick, most likely permanent.
At this point, you would need to get a replacement still running ICS if you truly want to downgrade. Alternately, considering using custom roms, which at this point are all JB based, but far superior to the Motorola "Blur" version found on stock phones.
Sorry!
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
Or maybe flash one of the ICS kexec ROMs? Not sure if it would work butttt possible. I may just try it myself so I can play order and chaos again.
Sent from my XT894 using xda app-developers app
Have you factory reset your device (Settings/Privacy/Factory data reset) since taking the update to JB?
Apps should be retaining their configurations (logins, etc..) and the phone should be smoother/faster than when it was on JB.
More than likely since the update patched the ICS system files to bring them to JB versions...something is causing issues from the updating. I'd definitely try a factory reset and reconfigure your phone. It may just be needing a proper reset/setup...
Imagine a Windows PC running Windows XP being "upgraded" to Windows 7 vs. another identical PC with a fresh install of Windows 7. The fresh install W7 will run much better compared to the patched/updated XP-W7.
If you haven't factory reset your device in a while....it's gone from GB, patched to ICS then patched to JB....or Windows 95 patched to XP then patched to W7.
yeah i factory reset twice during initial upgrade and setup all from scratch. at first a couple programs cudnt run and found out they dont work with jb and everyones hoping for an upgrade that seems abandoned by the developer. that was.. bearable slightly if i could find alternatives. but im yet to find satisfactory alternatives to any of them. my guitar chord and scales program wont run anymore. its installed but wont show in the app drawer so i cant launch or uninstall it. lbe privacy throws the fone into a bootloop. motoprint was removed in jb and i loved it. i found an alternative called send2print.. it works is all ill say about that. but overall its just a pain in the rear now. i liked how i never had to worry about anything before. everything just worked. so thanks for the input guys but this phone is going. already put it up for sale.
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
Hi on my work to unbrick the droid i have flash the ics via droid ics utility but it dosend start i think it ist the kernel becouse if you are on JB you don't get ics roms to work but with the kexec kernel it's working so I think if we get the ics kernel working we get ics back
Sent from my DROID4 using xda app-developers app