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.
Related
So a thought that has occurred to me since I got this phone is one of haret.exe on winmo phones. basically boot up past the bootloader and kernel(that are locked) then using either 2ndboot or kexec dump out of that kernel and launch out own kernel/filesystem
Sadly in looking around 2ndboot seems to require the phones kernel source(which we don't have, unless i'm totally wrong)
kexec on the other hand seems to be a much better way to accomplish it. Again this is mostly useless without a kernel BUT we could take our current kernel to use as a test bed for if (as is required) the release the kernel source.
Thoughts? anyone wanna join with me on trying to get this running and tested?
art3mis-nyc said:
So a thought that has occurred to me since I got this phone is one of haret.exe on winmo phones. basically boot up past the bootloader and kernel(that are locked) then using either 2ndboot or kexec dump out of that kernel and launch out own kernel/filesystem
Sadly in looking around 2ndboot seems to require the phones kernel source(which we don't have, unless i'm totally wrong)
kexec on the other hand seems to be a much better way to accomplish it. Again this is mostly useless without a kernel BUT we could take our current kernel to use as a test bed for if (as is required) the release the kernel source.
Thoughts? anyone wanna join with me on trying to get this running and tested?
Click to expand...
Click to collapse
I believe this was discussed already in the thread about cracking the bootloader, however, if you do manage to get this running I will gladly beta a new kernel as long as there is an SBF file available at the time to allow flashing back to stock.
Cheers
Ill gladly beta as well. So long as we have a method for recovery.
Sent from my MB860 using XDA App
Wondering why the bionic has a few roms out already and we dont? Do they have a fully working cwm? Am i missing something? Just curious. Thanks.
So far I've seen a deodexed stock rom and an early pre-alpha of CyanogenMod. What else has been posted for the Bionic?
The deodexed ROM is no different than stock for users and offers zero benefits.
The CM7 ROM was created by the lead CM team member of the Motorola Droid and Motorola Droid X (lots of experience with Motorola phones) and because he was donated a Droid Bionic. It's a completely useless ROM at this point as most of the hardware sensors do not work. It boots. Not much else.
Buy cpvcs a Droid 3, ship it to him and he will have a CM7 ROM booting on it within days of receiving it. It'll be just as useless as the Bionic's version....but it'll be there.
Give it time....it is going to be a while before a good solid/stable ROM is released.
First rule of XDA, don't ask for ETA's. If you want a custom ROM, nothing stopping you from trying to cook one your own.
Edit, hit the thanks instead of quote, they really should move that button
lordgodgeneral said:
First rule of XDA, don't ask for ETA's. If you want a custom ROM, nothing stopping you from trying to cook one your own.
Edit, hit the thanks instead of quote, they really should move that button
Click to expand...
Click to collapse
Where in my post does it ask for an eta???? I was asking why. Its a simple question.
heres the thing...waiting for CM7 will be worth the wait.. mmhmm.
..
They can flash, they're using the same flashing method that the D2, DX are using with 2nd init and hijacking. Hashcode hasn't enabled flashing on the D3 recovery yet because he's trying to do something a little different and a little safer from what I understand. From his explanation over in the clockwork recovery thread in development he's working more on a dualboot flashing system where we would basically leave the stock system intact and run the custom rom off a different partition/folder. This would allow us to boot to the stock rom if something happens during the flash process on the custom rom. Since using the 2nd init and hijack and not having an unlocked bootloader, CWR gets loaded into the preinstall partition along with the hijack files, so there's a chance these can get overwrote while flashing if something goes wrong and potentially soft brick the phone.
Don't worry the D3 is the flag ship phone that won't go to much longer with out some kick ass roms. But it is some BS that the bionic is getting roms right off the bat, while we wait. But I would be happy to send a d3 to those guys... if it would help or will bionic development and hacks work for the d3 as well????
Sent from my DROID3 using XDA App
Since when?
lordgodgeneral said:
First rule of XDA, don't ask for ETA's. If you want a custom ROM, nothing stopping you from trying to cook one your own.
Edit, hit the thanks instead of quote, they really should move that button
Click to expand...
Click to collapse
Since when has their been rules on topics asking ETA's on this forum, or any other forum in general? I know it's taboo to ask questions that have already been answered in several posts, but there are several forums specifically about speculating the ETA of not only just devices or OTA leaks, but about the cooking of roms on freshly rooted phones as well. The question of this post is legit, especially for users without the experience that more knowledgable users like tcrew and you (lordgodgeneral) have contributed to answering a question ALOT of people in the droid 3 community are wanting to know. Glad this topic existed, helped me out..
mmsomekid said:
Because the bootloader is still locked. The Bionic will probably get unlocked slightly faster than the D3 because they have more developers working on it, but theyre so similar that i would expect the D3 to get an unlock the same day as the Bionic. Unless Motorola finally unlocks the bootloaders but who knows when that day will come...
Edit: there is an UNL3ASH3D rom now available for the bionic, i didnt think they could flash yet in CWM?
Sent from my rooted Droid 3
Click to expand...
Click to collapse
It doesn't matter if the Bootloader is locked. It will probably never be unlocked.
Its been a rule since the devs on this particular forum specifically asked us not to ask for eta's. We have people cooking roms, were just waiting for our awesome version of CWM to be stable and safe to use. I'm as anxious as any of you, but don't hassle the devs that are working so hard to make our phones the best out there. Give them time.
sent from my ROOTED DROID3 from the XDA app
ROM Manager Premium Clockwork Recovery
Until now I have been more or less bemused by the complaints that the Droid 3 was being somewhat neglected in the development community in favor of the Bionic, assuming that there was more than a little exaggeration of the progress on the Bionic vs D3. Now, however, I am beginning to wonder if the complaints may not have been somewhat justified. I know no one owes the D3 owners anything on the dev side, but to see the Bionic now able to use ROM Manager while I sit with a previously paid app that does nothing on my phone is admittedly frustrating. I keep reading posts saying that any Bionic developments will be followed rapidly by similar progress on D3, so I hope I can use ROM Manager on my phone in a few days.
pgzerwer said:
Until now I have been more or less bemused by the complaints that the Droid 3 was being somewhat neglected in the development community in favor of the Bionic, assuming that there was more than a little exaggeration of the progress on the Bionic vs D3. Now, however, I am beginning to wonder if the complaints may not have been somewhat justified. I know no one owes the D3 owners anything on the dev side, but to see the Bionic now able to use ROM Manager while I sit with a previously paid app that does nothing on my phone is admittedly frustrating. I keep reading posts saying that any Bionic developments will be followed rapidly by similar progress on D3, so I hope I can use ROM Manager on my phone in a few days.
Click to expand...
Click to collapse
Droid 3 Bootstrap on Market: https://market.android.com/details?id=com.koushikdutta.droid3.bootstrap and direct download: http://download.clockworkmod.com//test/Droid3Bootstrap.apk (ROM Manager support as well)
bam
If you have already purchased Rom Manager, just install it and have it install the custom recovery for you...
Edit: Maybe not.. it shows it installed CWR but I can't boot into it..
A large PayPal donation to the first flashable Rom!
Sent from my DROID3 using Tapatalk
Rocinante said:
If you have already purchased Rom Manager, just install it and have it install the custom recovery for you...
Edit: Maybe not.. it shows it installed CWR but I can't boot into it..
Click to expand...
Click to collapse
You have to use koush's bootstrap...
Sent from my DROID3 using xda premium
Just curious, outside of no custom kernels nothing else has to be used from the stock system, correct? So custom roms with our 512 of ram will be more than enough.
Sent from my DROID3 using Tapatalk
ROM Manager Premium Clockwork Recovery
OK, I am a believer now. No more pathetic whining by me, at least for the next 5 minutes or so.
Androidsims said:
You have to use koush's bootstrap...
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Yeah, I'm guessing there is a special way it boots into recovery with the custom app because I can't get Rom Manager to boot into recovery..
So we have root, custom kernel, and now CWM. It is about time we have a custom ROM to flash. Still no developers with the device, but we have gotten this far with the help of other developers without the device. I was thinking we could get a list of requests and then contact the right people and provide them the files they need to modify.
I guess ill start with the most obvious ones.
[*] Root / SU / Busybox
[*] Zipaligned
[*] Deodexed
[*] Ad Blocking
[*] Browser tweaks
[*] Bloatware removal
[*] OC kernel?
[*] CWM 5.5.0.4 w/ .hidenandroidprogress built in
[*] Updated stock apps
[*] Extended Power Menu
[*] Theming? (not necessary)
[*] Tethering
Thats all I can think of for now. Once we get a list of things we can begin to find someone with the skills to do it.
Pretty much what you mentioned. And of course the obvious one. ICS is the big want and I know it will take some time. Preferably right now a cleaned up stock rom and themes would be cool.
So i installed linux on my netbook along with dsixda's ROM kitchen. I dont know much but ill see what i can do.
so yea.
so far i can create a ROM which is bloatware free, zipaligned, deodexed, rooted, CWM w/ hidenandroidprogress, updated system apps, with or without OC kernel, and with tethering. sweet.
basically teaching myself though so it may be a while.
I'm not really active on these forums, but I'm also available for testing on my i957. (Wasn't allowed to post in the dev forum until I hit 10 posts)
Yep all the above. the main thing is to get rid of this UI lag.
On my 8.9 LTE i just used another launcher and it was gone...
I'm using another launcher and it's almost gone. I still get forces. I really want to do a full restore of the original rom before any roots and try to push the OC and libs again. The stock ROM I was given by Croak only helps recover from issues but not the ones I mentioned. It never had force closes or any weird issues before. But since the OC it's been running kinda crazy.
Thanks Orlando for the initiative!
In addition to what you have written, If possible, I would also would love to have:
1. Icons representing cellular speed (2G,3G,H,H+,4G) as on my SGS2.
2. JKAY mod. I don't know if this mod is SGS2 only mod or not. , but if it is possible to port it to our tab it would be great.
Thanks
I am not a dev by any means. I just dont have the time to teach myself all of the ins and outs that sammy devs and AOSP devs do. I give them so much credit. Coming from years of a windows base and no programming experience, its tough. I cant make up for what real devs can do, but for now I think I can get a ROM out which will be decent until we can get some real help.
I thnk as soon as we get a good stable, flashable, deodexed base it will open up a lot more easily implimented possibilities for theming and adding/subtracting little odds and ends that differentiate some of the different major ROMS.
My suggestion is to just work on good stable base ROM with fully functioning basics first and let the community work it from there.
I really need to fix the update-binary and the update script in order for this to work in CWM.
but basically I just did simple automated tasks. Kitchened from my nandroid.
Rooted
Superuser
Busybox
Deodexed
Zipaligned
Da_G Overclock Kernel
NoFrills OC App
Custom Libs for OC
Asus Water Wallpaper
Asus Weather Widget
Titanium Backup
Rom Manager (Dont Use It)
Custom Boot Animation Enabled
Bash Shell Support
CWM 5.5.0.4 w/ .nandroidprogress
If it turns out that the nandroid wont work well, then the stock will have to be modified, which means basically just deodex, root, zipalign. thats about all I can do. I wish i knew more about the whole android system but sadly i dont. i am trying to teach myself but it is going to be slow, so i pray we get a real dev soon.
Whatever you can do man is much appreciated. I wish I had a coders heart and talent. Because spend enough time on a PC to be able to contribute if I could this type of coding.
I thought I had everything set and tried to flash and just got bootloops. Then I just took the stock ROM and made a flashable zip from the stock firmware and that didn't even boot. Really discouraging and it took forever to get my tab back to working. Might be better just to wait for someone who knows what they are doing.
Sent from my SAMSUNG-SGH-I727 using xda premium
Google Maps 6.2 Ownhere Mod is a most... For any rom...
Sent from my SAMSUNG-SGH-I957 using xda premium
orlandoxpolice said:
I thought I had everything set and tried to flash and just got bootloops. Then I just took the stock ROM and made a flashable zip from the stock firmware and that didn't even boot. Really discouraging and it took forever to get my tab back to working. Might be better just to wait for someone who knows what they are doing.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Take it easy... Did you took the $7 AT&T insurance for the tab? Usually the AT&T sales rep. does not even know that there is an insurance option for this tab. I went online and saw there was insurance... And mentioned it to the AT&T rep. when buying the tab and he said there was no insurance option... And I told him, yes there is! And he double check and finally realized there was insurance. I took it, because I know the feeling of converting into a brick a brand new shiny device, lol... And look where I am... Already rooted, O/C, flashed recovery and waiting for CM9 or any rom available, lol... Just taking the sidewalk on brick ave. Lol...
Sent from my SAMSUNG-SGH-I957 using xda premium
Gsm calls please
Sent from my GT-P7300 using XDA App
I am going to look into insurance today. if i can get it then ill keep flashing away
couldn't get logcat working though to figure out why the flashes went bad...
Got the insurance!
Sent from my SAMSUNG-SGH-I727 using xda premium
orlandoxpolice said:
Got the insurance!
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Great! so now... where can I download the orlandoxpolice ultimate kick ass rom? with all the features mentioned above with CM9 support, voice support for calls, that even unlocks tablet for any gsm sim card and all the latest versions of everything on the market? ahhh and everything in 4D of course... lol
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.
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