Tab 10.1 P7510 - CM10.1 Keyboard - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Know this is a known issue... keyboard crashes and so does Google Now. Fixed Google Now issue by changing default language to English (cananda) but even with all the auto correct settings disabled my keyboard still crashes.
I know I should have flashed the modified version of gapps but I did not find out about it until it was too late. Can I flash that modified version OVER my current version (latest from goo) ?
I dont want to wipe the device at this point if AT ALL possible.
thanks.

Don't know how I could help with your issue, but I will tell you that you would need to full wipe to fix it, including wiping system.

+1. You must wipe fully in order to clear out the offending bits of previous gapps stuff that would conflict. Sorry man.

djmatt604 said:
+1. You must wipe fully in order to clear out the offending bits of previous gapps stuff that would conflict. Sorry man.
Click to expand...
Click to collapse
Dang. is this going to maybe be fixed in an upcoming nightly?
PS- this ROM is absolutely incredible. My P7510 was DEAD with 4.0.4 and slow as can be. I have nothing but great hings to say about this. OTA nightly updates is just incredible.

Related

[ROM]Pc Zseni 4.0.4 ICS SGSII V1

V2 update:
fixed: MobilNET auto power on, screen flicker and quicker updated nightly CM9, faster, stable
Download, images:
http://pczseni.com/android-fejlesztesek.html
Preface: Based on Android 4.0.4 cm9 nightly, fast, stable system
Features:
- Multilanguage
- Cm9 kernel
- Rooted
- % battery display
-remove some app
- replaced bootanimation
- optimalize and modify framework
Download, images:
http://pczseni.com/android-fejlesztesek.html
Installation: Battery, preferably 100% charged - EFS and optionally save phone numbers, sms, etc. .. Factory, factory-based rom: CWM-CWM-CM7-installing from the zip install the rom from internal SD-WIPE (wipe data / factory reset wipe + cache partition) CM7, build to other ICS update: CWM-rom from the zip to install from the internal SD-WIPE (wipe data / factory reset wipe + cache partition) Install it at your own risk, for any errors We are not responsible!
FIRST, so uh, what's the difference between this and CM9? I mean how is your rom different than the CM9 that is available for us to download by Codeworkx?
Nasty_z said:
FIRST, so uh, what's the difference between this and CM9? I mean how is your rom different than the CM9 that is available for us to download by Codeworkx?
Click to expand...
Click to collapse
Example: Removed Settings apk cm mod version, cm static etc...
You're new here,right? this is your first rom? Will you update it to CMX any time?
Nasty_z said:
You're new here,right? this is your first rom? Will you update it to CMX any time?
Click to expand...
Click to collapse
Yes, I new user in Xda.This is the first phone model from the rubble and the ruins will be updated continuously.
Give proper credits to Codeworx and the rest of the team!!
Sent from my GT-I9100 using xda app-developers app
First of all, welcome to XDA.
Now, i recommend to you give more presentation to your OP, i know that you have a link to the screenshots and downloads but it's better if you have all the information on the thread. Also, the details of how it's different from CM9 would be better if are included on the OP too.
Good luck.
@OP
I cannot understand and read if it is not in English and please put all the ROM info in the op.
Thanks and good luck.
PS
Give proper credit to CM Team.
Downloading it right now. Is it right that the file is only about 140MB?
legola said:
Downloading it right now. Is it right that the file is only about 140MB?
Click to expand...
Click to collapse
Yes, 146*890*606 bytes
Question
Opinions?
okoska2 said:
Opinions?
Click to expand...
Click to collapse
Look man, I understand this is your first ROM. Now, as you already know, we have CM9, the only changes you made are de-bloating the rom. But, we can all already do that using Titanium Backup, I'd say you gotta add something to this ROM to attract users. Don't get me wrong, you've done a great job. I mean, I can't even do what you did. But all the same, these people won't try out the ROM unless they find something new or better in it.
Looking forward to something better from you. I know you got the potential.
If it was a suggestion you wanted, if you make a CM10 ROM, I'll definitely try it!
Cheers.
Nasty_z said:
Look man, I understand this is your first ROM. Now, as you already know, we have CM9, the only changes you made are de-bloating the rom. But, we can all already do that using Titanium Backup, I'd say you gotta add something to this ROM to attract users. Don't get me wrong, you've done a great job. I mean, I can't even do what you did. But all the same, these people won't try out the ROM unless they find something new or better in it.
Looking forward to something better from you. I know you got the potential.
If it was a suggestion you wanted, if you make a CM10 ROM, I'll definitely try it!
Cheers.
Click to expand...
Click to collapse
I mean, thank you have written. I was thinking is I think the only cm10 development is still very immature and 1-2 months you will have a usable condition.
V2 update
V2 update available!

[Q] Unfortunately Android Keyboard Has Stopped

So I have been running CM10 nightlies since they first came out for the I9100int.
Been loving them, they seem to work really well, however last night I started getting the error, "android keyboard (aosp) has stopped working"
Fortunately I have a second keyboard to use, but I was wondering if anyone else has had this error.
I cannot seem to find much about it anywhere, so I figured Ill ask the source.
I have cleared the keyboard cache, but that doesnt make any difference.
The last time this happened I had to do a full flash and I was hoping to avoid that.
even reverting to a backup hasnt seemed to fix it, so Im not sure if my backup had the issue too.
anyways, just thought Id throw this out there for any help.
Otherwise Id like to give a HUGE thanks to all the developers with this project, I love my S2 more and more with constant updates they provide.
Go into menu/system/apps and find android keyboard asop and CLEAR DATA Then do the same for Dictionary Provider and CLEAR DATA.
Sent from My SGH-I777 Running Red Reaper Rom
RockRatt said:
Go into menu/system/apps and find android keyboard asop and CLEAR DATA Then do the same for Dictionary Provider and CLEAR DATA.
Sent from My SGH-I777 Running Red Reaper Rom
Click to expand...
Click to collapse
SICK!!! thanks so much this worked perfectly..
T869
Awesome. Worked like a charm on my SGH-T869 running CyanogenMod Ver. 10-20121007--T869.
RockRatt said:
Go into menu/system/apps and find android keyboard asop and CLEAR DATA Then do the same for Dictionary Provider and CLEAR DATA.
Sent from My SGH-I777 Running Red Reaper Rom
Click to expand...
Click to collapse
On my Galaxy Note N7000 after an install of the current nightly CM10, some weeks later I get this message and the only way I can fix it is with a Factory Reset/wipe. This has happened a few times now. From the Settings app, I can get into System/Apps but there are no options like you mention above . .
It would be nice not to have to use the Factory Reset/wipe method . . is there a way of using your method on the N7000?
Thanks,
Phil.
cblock said:
SICK!!! thanks so much this worked perfectly..
Click to expand...
Click to collapse
I really can not find Dictionary Provider anywhere. Where is it??
Thanks in advance
RockRatt said:
Go into menu/system/apps and find android keyboard asop and CLEAR DATA Then do the same for Dictionary Provider and CLEAR DATA.
Sent from My SGH-I777 Running Red Reaper Rom
Click to expand...
Click to collapse
I have Sprint's S3 and when I flashed CM10 on it, I keep getting "android keyboard (aosp) has stopped working". I just flashed it so I don't have any other why to type or even get logged into the play store to download a new keyboard. Please help.
Subbu9 said:
I really can not find Dictionary Provider anywhere. Where is it??
Thanks in advance
Click to expand...
Click to collapse
I too cannot find "Dictionary Provider" anywhere. Any help would be appreciated. Thank you.
Galaxy Nexus
CM10
When you go setting/apps, make sure you swipe to the right so it says ALL at the top, not just downloaded, they're in there. I just had the same error hence my search here. Following the advice above worked for me on cyanogen mod
=deleted=
fozzy169 said:
When you go setting/apps, make sure you swipe to the right so it says ALL at the top, not just downloaded, they're in there. I just had the same error hence my search here. Following the advice above worked for me on cyanogen mod
Click to expand...
Click to collapse
Thanks for the reply fozzy --- I did a master reset/master clean and it fixed it all. Still can't see "Dictionary Provider" anywhere, incidentally...bizarre!
Appreciate it though. :good::good::good:
Woah, thanks!
Alright so I just got the CM10 update and I had the same error as you, and the fix worked well! Thanks c:
CommanderT1562 said:
Alright so I just got the CM10 update and I had the same error as you, and the fix worked well! Thanks c:
Click to expand...
Click to collapse
I can't see the dictionary app either. Anybody got any ideas why?
msimsie said:
I can't see the dictionary app either. Anybody got any ideas why?
Click to expand...
Click to collapse
Same problem here. I just flashed the Provision JB ROM and right away I can't use my keyboard at all. I cleared the data for the AOSP keyboard but I can't find the dictionary app.
same problem.. no dictionary provider. keyboards keeps on crashing (phone is Sk17i so bug is not related to phone itself)!
I've the same issue, even i can't type any letter !
I've cleared the data for Android keyboard ( from settings/apps.. ) , but it didn't work with me!
Also i can't find Directory provider in apps.
So, what to do?
I use SGT-P3100.
BRGRDS
I solved it by using gapps-jb-20120726-signed.zip
I faced the same issue yesterday when I installed cm10. I have xperia mini pro sk17i.
After a lot of trial and error, I solved the error doing:
wiping cache partition
factory reset
installing cm10 rom
installing gapps one version older: gapps-jb-20120726-signed.zip (I am new and unable to post a link, just google it.)
The main takeaway - use the older gapps and after install, update them using market. Maybe just doing this will solve the problem for you.
PS. I am using extender kernel by M66B
Even though I'm using the latest nightly for the samsung galaxy nexus I ran into this same issue. Cleared data for android keyboard but as others couldnt find the data dictionary so since I use a 3rd party keyboard anyways, I went back into android keyboard and disabled it. No more error for me, hope that helps.
The solution to this seems that the newes Gapps Version for JB is not compatible with 4.1.x. http://wiki.rootzwiki.com/Google_Apps#20121130.
So if your using Android 4.1.2 you have to stay with gapps 20121011.
20121130 is for Android 4.2 only. In that case a bad choice to stay with JB for the new release, as this cannot easyly be seen in the name of the zip package..
If you already installed 20121130 it should be sufficient to reinstall ROM and after that gapps version 20121011. If that doen't work you need to wipe..
miro279 said:
The solution to this seems that the newes Gapps Version for JB is not compatible with 4.1.x. http://wiki.rootzwiki.com/Google_Apps#20121130.
So if your using Android 4.1.2 you have to stay with gapps 20121011.
20121130 is for Android 4.2 only. In that case a bad choice to stay with JB for the new release, as this cannot easyly be seen in the name of the zip package..
If you already installed 20121130 it should be sufficient to reinstall ROM and after that gapps version 20121011. If that doen't work you need to wipe..
Click to expand...
Click to collapse
No luck, I needed to install a 3rd party keyboard. Strangely, the same method (flash rom+gapps) worked on a friend's phone.

Custom ROM for GTab, which one to start, which to sort out?

Hi.
I just got my GTab 7510 Wifi Only.
I'd like to install a CustomRom. On my Galaxy Nexus the Rubik ROM - PA with Linaro is working quite excellent.
As far as I have seen, there is no PA for the GTab.
Could you give me some hints, which (JB or not JB) Roms are good and well compiled and which to sort out?
Thank you
There is PA for galaxy tab. @kasper_h compiled it for us, but its currently in alpha stage. If you want to try it out, its in the development section. As for which ROM is the best, try them yourself. Everyone of them are great ROMs. Good luck.
Sent from my GT-P7500 using XDA Premium HD app
Ive been running some 4.2.2 ROM's but just yesterday I flashed this one..
http://forum.xda-developers.com/showthread.php?t=2055062
It's an ICS ROM so you may not get all the bells and whistles as an AOKP 4.2.2 but my opinion is this one is extremely smooth. The JB ROM's Ive tried were nice but didnt seem to be as smooth. Just my opinion
I'm running CM 10.1 on my tab and it's pretty good so far, but there are a few glitches, such as google now not working properly unless you uninstall the updates. Kind of a bummer, but I have google now on my phone so its not a huge deal. Other than that it's fairly smooth, a little glitchy here and there, but it doesn't bother me.
Prior to this I had CM 10 loaded on there and that was very smooth with no glitches whatsoever, but it doesn't have some of the features that 10.1 has obviously.
Prashramani12 said:
I'm running CM 10.1 on my tab and it's pretty good so far, but there are a few glitches, such as google now not working properly unless you uninstall the updates. Kind of a bummer, but I have google now on my phone so its not a huge deal. Other than that it's fairly smooth, a little glitchy here and there, but it doesn't bother me.
Prior to this I had CM 10 loaded on there and that was very smooth with no glitches whatsoever, but it doesn't have some of the features that 10.1 has obviously.
Click to expand...
Click to collapse
Google now does work.. Install the right gapps
DefQoN_BE said:
Google now does work.. Install the right gapps
Click to expand...
Click to collapse
I originally had the goo.im gapps which had the faulty google now. I then heard that the wingray gapps have a working google now even when updating the app, so I completely wiped my system and installed the wingray gapps along with reflashing cm 10.1. For whatever reason, google now still doesnt seem to be working.
If I did something wrong, or if you know of a different gapps that does work please let me know. I would really like to have a fully functioning gapps, and it would certainly benefit the OP as well
Prashramani12 said:
I originally had the goo.im gapps which had the faulty google now. I then heard that the wingray gapps have a working google now even when updating the app, so I completely wiped my system and installed the wingray gapps along with reflashing cm 10.1. For whatever reason, google now still doesnt seem to be working.
If I did something wrong, or if you know of a different gapps that does work please let me know. I would really like to have a fully functioning gapps, and it would certainly benefit the OP as well
Click to expand...
Click to collapse
gapps-jb-20130129-P75xx.zip http://www.mediafire.com/?44xhky6dyx4wlw2
DefQoN_BE said:
gapps-jb-20130129-P75xx.zip http://www.mediafire.com/?44xhky6dyx4wlw2
Click to expand...
Click to collapse
And this one works even after updating the google search app?
Prashramani12 said:
And this one works even after updating the google search app?
Click to expand...
Click to collapse
Unless i'm having a supertablet, it works?
DefQoN_BE said:
Unless i'm having a supertablet, it works?
Click to expand...
Click to collapse
Hmm maybe you do...
I completely wiped my tab (partition, cache, dalvik), flashed the June 16th nightly of CM 10.1 along with your gapps, and google search/now STILL doesn't work after I updated the app, it keeps force closing.
If you have any light to shed on why this doesn't work, let me know.
Thanks for the answers :fingers-crossed: :good:
I have installed Carbon from kaspar right now, but I must say... I am a bit disappointed.
It is a little ... not-snappy (don't know how to express that)
Could you tell me the difference between Infamous 4.0.4 and Carbon 4.2?
Both seem to have the same kernel, but the difference between 404 and 42?
nadastry said:
Thanks for the answers :fingers-crossed: :good:
I have installed Carbon from kaspar right now, but I must say... I am a bit disappointed.
It is a little ... not-snappy (don't know how to express that)
Could you tell me the difference between Infamous 4.0.4 and Carbon 4.2?
Both seem to have the same kernel, but the difference between 404 and 42?
Click to expand...
Click to collapse
Well...Kasper did say that carbon is still in alpha stage. There is a sh*tload of difference between infamous and carbon. Infamous is touchwiz based, carbon is aosp based. The kernel is different. The Infamous kernel is an older version of Mackay kernel, carbon uses the latest Mackay kernel by Kasper.
Sent from my GT-P7500 using XDA Premium HD app
eushaun99 said:
Well...Kasper did say that carbon is still in alpha stage. There is a sh*tload of difference between infamous and carbon. Infamous is touchwiz based, carbon is aosp based. The kernel is different. The Infamous kernel is an older version of Mackay kernel, carbon uses the latest Mackay kernel by Kasper.
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
Hi @eushaun99 , could I ask if you know the difference between the Infamous AOKP (JB) and Carbon (now currently in Beta). I'm now on Carbon Beta with my p7500. I was previously on CM10.1 and I do find Carbon less laggy than CM10.1..the nightly I was on previously was very laggy in fact. But currently my GPS doesn't seem to work..or takes ages to get a fix on Carbon. Same problem on the previous CM10.1 also. Any chance it works better on Infamous AOKP?
quarian said:
Hi @eushaun99 , could I ask if you know the difference between the Infamous AOKP (JB) and Carbon (now currently in Beta). I'm now on Carbon Beta with my p7500. I was previously on CM10.1 and I do find Carbon less laggy than CM10.1..the nightly I was on previously was very laggy in fact. But currently my GPS doesn't seem to work..or takes ages to get a fix on Carbon. Same problem on the previous CM10.1 also. Any chance it works better on Infamous AOKP?
Click to expand...
Click to collapse
Infamous AOKP is AOKP-based. Carbon is actually a mixture of CyanogenMod, AOKP and ParanoidAndroid. So in Carbon you get all the special features from all 3 ROMs. For your GPS problem, I honestly don't know.
Sent from my GT-P7500 using Tapatalk HD
eushaun99 said:
Infamous AOKP is AOKP-based. Carbon is actually a mixture of CyanogenMod, AOKP and ParanoidAndroid. So in Carbon you get all the special features from all 3 ROMs. For your GPS problem, I honestly don't know.
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
@eushaun99 Thanks so much! I hope you don't mind me asking you more qns:
1) What rom are you using now for p7500? Why did you pick that rom in the end?
2) I realise now that I didn't do a full clean install. I did not format system under "mounts and storage". Can I check with you, where do I save the rom zip and the gapps zip so that it's safe even when I do the wipe data and format system.Currently I put the rom zip and gapps zip into the sdcard folder which is in / (which I understand refers to my internal sd). What folder does format system clean? Is it just the "system" folder?
thanks in advance!
quarian said:
@eushaun99 Thanks so much! I hope you don't mind me asking you more qns:
1) What rom are you using now for p7500? Why did you pick that rom in the end?
2) I realise now that I didn't do a full clean install. I did not format system under "mounts and storage". Can I check with you, where do I save the rom zip and the gapps zip so that it's safe even when I do the wipe data and format system.Currently I put the rom zip and gapps zip into the sdcard folder which is in / (which I understand refers to my internal sd). What folder does format system clean? Is it just the "system" folder?
thanks in advance!
Click to expand...
Click to collapse
1) I'm using InfamousAOKP right now. For me, its one of the best ROM available for our tab. Smooth, silky,great battery life. Also I love the fact that AOKP has an option for a dark-themed ROM. Makes my keyboard look so damn nice.
2) The downloaded files will be stored in /data/media which is symlinked to /sdcard, not /. If you format system, only /system will be wiped. If you format data, everything in /data will be wiped except /data/media, so don't worry.
Sent from my GT-P7500 using Tapatalk HD
eushaun99 said:
1) I'm using InfamousAOKP right now. For me, its one of the best ROM available for our tab. Smooth, silky,great battery life. Also I love the fact that AOKP has an option for a dark-themed ROM. Makes my keyboard look so damn nice.
2) The downloaded files will be stored in /data/media which is symlinked to /sdcard, not /. If you format system, only /system will be wiped. If you format data, everything in /data will be wiped except /data/media, so don't worry.
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
I just flashed to Infamous AOKP last night. It was a clean flash with system wipe and factory reset but I now get a System UIDs do not match error when booting up. It still manages to get to home screen once I click "I'm feeling lucky" (which is the only option when the error msg pops up anyway). But my GPS is still not working. It wasn't working properly on Carbon rom either (took ages to detect and kept losing signal) or CM 10.1.
quarian said:
I just flashed to Infamous AOKP last night. It was a clean flash with system wipe and factory reset but I now get a System UIDs do not match error when booting up. It still manages to get to home screen once I click "I'm feeling lucky" (which is the only option when the error msg pops up anyway). But my GPS is still not working. It wasn't working properly on Carbon rom either (took ages to detect and kept losing signal) or CM 10.1.
Click to expand...
Click to collapse
What the hell? I'm feeling lucky? Lol. I don't know, wipe again? Did you wipe dalvik cache? Can you get a screenshot? I want to see that error lol.
Sent from my GT-P7500 using Tapatalk HD

Crash on screen orientation

Hi,
I hope I'm in the right section for this.
Since I updated to Android 4.3 (latest HellyBean build), my phone crashes after a few screen orientation changes.
Does anyone know what the reason for this strange behaviour could be?
Thanks for your help!
Da Bozz said:
Hi,
I hope I'm in the right section for this.
Since I updated to Android 4.3 (latest HellyBean build), my phone crashes after a few screen orientation changes.
Does anyone know what the reason for this strange behaviour could be?
Thanks for your help!
Click to expand...
Click to collapse
You did full wipe before flashing the rom?
If this happening again and again then flash the rom again to check
Thanks for your response!
Yes, I did a full wipe, but I will try flashing it again.
Could this probably relate to build.prop mods?
Edit: Seems like a broken design was the problem. Activating the stock one fixed it, at least until now.

[ROM] [Project ] Pure AOSP 5.0.2+Google Updates (1/01/2015)

The idea behind this project is to compile a Pure AOSP ROM. The difference is I have been little by little including and testing new changes and fixes added to the AOSP code from Google that has not yet been tagged or added to the release branch and will most likely be added into a future Lollipop update., hence the reason for 5.0.2_Plus. The only change added that was not committed by Google is that the ZIP can be flashed in TWRP without replacing TWRP with the Stock Recovery and that is it.
There is more coming but would like to first verify my testing on what has been done so far. The idea is to stay ahead of the curve with fixes and updates coming down from Google before they are released. As offered in the development Q&A Thread I started with this idea is that anyone who is able is welcome to jump on and help. All and all is just sifting over the AOSP Master branch adding new commits that have not yet been tagged as part of a release branch. Thought of the idea after reading a statement from Google true or not that allot of bug fixes have already or are in the process of being added into ASOP. These commits all come from the master branch developers do not build from and is more of a staging ground for future releases. A few of these commits are less than a week old. Anyhow so Instead of this being my Rom I would like us to just all have the most updated code base to work with so let me know and will give full permission to the Github organization. We wiil just need to set up separate branches for testing to insure our Master branch is stable at all times so it can be used and trusted by all our devs to use in their Roms. I am sure we can gather a team of testing volunteers. Otherwise this is again 100% AOSP code without any modifications outside what has been committed by Google and planned on keeping it this way. Although I am posting like stated above would not like to think this is my Rom but more for the community in general so our Developers have the latest stable code to work with when creating Roms and am not just posting because as Google has proven with Lollipop the more testers the better as we all have different set-ups and use are devices differently but I also wanted to give the project/idea a bit of attention.
A Few Added Update Examples.
https://github.com/Android-AOSP/And...mmit/a05556633ae5a6d1db164597b93f8b6cbbdf2608
https://github.com/Android-AOSP/And...mmit/e6beb1369165f97a4df24a1d1966c41e392c44e7
https://github.com/Android-AOSP/And...mitM/be42994b5a42914071adddfd5d989950e8e47bd9
https://github.com/Android-AOSP/And...mmit/0c89e1b9395093f71cf73508553d5e4058093ec0
https://github.com/Android-AOSP/And...mmit/4c53a7872b1f37ec184801f16d39584ca3b9bcce
https://github.com/Android-AOSP/And...mmit/9d2f14442f2e1d1507dbdc6cc7b9348513a907f9
https://github.com/Android-AOSP/And...mmit/905c6e72ecdc6e170744649b78e8fbb919f71efd
https://github.com/Android-AOSP/And...mmit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/And...mmit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/Android-AOSP_bionic/commit/eaf5aa7d22bd2f6b2eae4c81a60950f89e2d7df4
https://github.com/Android-AOSP/And...mmit/74574e8aa5a2de32e10364fd2f495023fff2a267
https://github.com/Android-AOSP/Android-AOSP_build/commit/49657b7a459ee90b3635bef989f8f9728d564068
https://github.com/Android-AOSP/Android-AOSP_build/commit/1df3707a04651966ca17796f321d23ab3ed6ed2e
https://github.com/Android-AOSP/And...mmit/6fe9c73738e9da0192971576d120802d4c094556
https://github.com/Android-AOSP/And...mmit/44c1c3235d29095c4d987d19155c7260d1a33e0f
https://github.com/Android-AOSP/And...mmit/33baf53861712c3f84606a017943e36bdc680b50
https://github.com/Android-AOSP/And...mmit/a975a08cfb30ad6b2994647c0c6f09e2abd20e28
https://github.com/Android-AOSP/external_protobuf/commit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/external_protobuf/commit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/frameworks_base/commit/cc50afe3bdcc3adfa0f4121bf461996996e69a3e
https://github.com/Android-AOSP/frameworks_base/commit/1be740dd60f4d95e1f9ac4aac7e4d6148e3b2dd1
https://github.com/Android-AOSP/frameworks_base/commit/1cca2282dc9a3b7ecc08729af201923842ddfc86
https://github.com/Android-AOSP/frameworks_base/commit/7db1192e72b45111556631dba125a635edff3235
https://github.com/Android-AOSP/frameworks_base/commit/b29136581cc3181e59193e0b6448f0c3f5990081
https://github.com/Android-AOSP/build/commit/de655233a4308340fc71490e86fd0f218cc7fec4
https://github.com/Android-AOSP/build/commit/ab6f841841a0930c7e178a949ada39152e24540f
https://github.com/Android-AOSP/hardware_libhardware/commit/9ede7f730bca338cd3ccad8962e253f28ae17976
https://github.com/Android-AOSP/hardware_libhardware/commit/d4f431fec4136f6eeee919ac3190762fba832942
https://github.com/Android-AOSP/hardware_libhardware/commit/898bcd96e3d80e99d9200cceb4af754bae6d5f4a
https://github.com/Android-AOSP/bionic/commit/d90f39af35c1f2a9972198f92e803e3ca73ac910
Downloads
Download Rom
aosp_hammerhead-ota-5.0.2_plus_r4.zip - 191.35 MB
aosp_hammerhead-ota-5.0.2_plus_r3.zip - 191.35 MB
aosp_hammerhead-ota-5.0.2_plus_r2.zip - 191.34 MB
aosp_hammerhead-ota-5.0.2_plus.zip - 191.34 MB
PA-Gapps
http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
So far I have been using the "Mini Modular package" for testing without any issues.
Root
Root is optional but recommend SuperSU
http://forum.xda-developers.com/showthread.php?t=1538053
Have had version 2.37 in storage and had been using without issue but updated to 2,40 with last test without any issues. What can I say Im lazy that way so unless having an issue just used what works but figured most would grab the latest so thought it best to give it a test before posting.
Kernel is also %100 stock but including a shameless plug for my Starship Kernel as in testing have worked well together and is the only other Kernel verified though am sure you should not have any problem with other AOSP/Stock Kernels.
Starship Kernel
Starship-lollipop_Kernel-3.4.36_r1.zip - 7.65 MB
Starship Kernel Source
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/tree/lollipop
As usual I am not responsible for your device and you are using anything posted in this thread at your own Risk.
Is %100 pure AOSP so no screen shots as am sure you are aware what it looks like at this point.
Change Log 5.0.2_plus_r4
Removed the below commit "Add ip6-localhost to /system/etc/hosts."
https://github.com/android/platform_system_core/commit/25147416bb105914c3cdf8fd65ca7cc20dae0f3e
Looks like a few apps are not fans of having an ip6 entry for localhost. Transparent Weather Widget for example can not find the device location with the enty included.
In looking for the cause of the above issue also reverted.
https://github.com/android/platform_frameworks_base/commit/e4ec09da0b4a31e23f1a19bdd1ea99e0f87cadac
Honestly reverted looking for the cause and did not remember to restore once identifying the cause. Overall is an old commit and dont think will make any difference whatsoever or would have been tagged for use in a past release so not going to bother.
Before the ip6-localhost commit issue had been identified by a user from the Nexus 4 version of this project was testing newer commits. The following few had been in testing at the time and included with the N4 Mako build. They are just a few of what was intended but because updating to r4 for the bug fix these are included in the r4 release.
Add missing <string.h> includes.
https://github.com/Android-AOSP/and...mmit/718568d982f92a93da19bfb8d4ea6dd996913e25
Add missing <string.h> includes.
https://github.com/Android-AOSP/and...mmit/8cb6a047d89479e4f65e0bcfa1642b4891463c04
Fix missing parenthesis.
https://github.com/Android-AOSP/android_aosp_build/commit/49657b7a459ee90b3635bef989f8f9728d564068
Remove superfluous OpenSSL include paths.
https://github.com/Android-AOSP/and...mmit/b9e7a844fc751b9fdda7d452dee361f15815199b
Besides this am about %80 done Starship L Rom and have offered to join a development team so lots going on but plan to keep this up and finish my new Starship L rom. Otherwise looking very much foreword to once again working as part of a team as since I started developing 3 years ago these last few month of Nexus ownership has been the first time I have worked alone and so much more prefer having a team to work with and discuss things with. Love my cat but pretty sure he doesn’t understand what I am talking about and my friends although interested are intimidated believing developing is so over their heads they could never do it .
woot woot
Vero good
Why 2014
Good ROM, but since I am a Sprint user, the update-device.zip fix doesn't seem to work on this ROM, nor does the update profile/prl zip fix, which is important for calls.
Like the idea! Only complaint us that you could hide some text like the github picks and downloads under a spoiler
Edit. Oh and first page woot woot!
Sent from my Nexus 5 using XDA Premium 4 mobile app
The only thing bothers me is the aosp dialer icon, so anti-material, can someone solve that out?
Any bugs?
iamterence said:
Good ROM, but since I am a Sprint user, the update-device.zip fix doesn't seem to work on this ROM, nor does the update profile/prl zip fix, which is important for calls.
Click to expand...
Click to collapse
I am on T-Mobile and looks like neither Google or myself had been thinking about Sprint users. Needs to take a look
chairshot215 said:
I am on T-Mobile and looks like neither Google or myself had been thinking about Sprint users. Needs to take a look
Click to expand...
Click to collapse
Much appreciated, good sir. If nothing can be done, all will still be well. Still appreciate your efforts.
iamterence said:
Much appreciated, good sir. If nothing can be done, all will still be well. Still appreciate your efforts.
Click to expand...
Click to collapse
Think if rooted with bussybox installed fix may then work. Otherwise think would need to either build the fix in before compiling or build non block based and add files into the zip. Took a quick look and the fix I downloaded called on bussybox in the update-script when flashing so installing bussybox may fix the sprint fix, lol. Otherwise does not look like a hard fix taking a quick look at cm12. Have a meeting at 1:00 and look into some time after.
Any other download mirror ?
It is hardly possible for me to download the rom from dev-host
hunzhang said:
It is hardly possible for me to download the rom from dev-host
Click to expand...
Click to collapse
?????????
chairshot215 said:
Think if rooted with bussybox installed fix may then work. Otherwise think would need to either build the fix in before compiling or build non block based and add files into the zip. Took a quick look and the fix I downloaded called on bussybox in the update-script when flashing so installing bussybox may fix the sprint fix, lol. Otherwise does not look like a hard fix taking a quick look at cm12. Have a meeting at 1:00 and look into some time after.
Click to expand...
Click to collapse
Forgive my noobness, as I'm usually on point with this stuff, but how can I root WITH busybox? Would I need to boot up and then download the app from the store? Because if so, I can't get past the setup screen without constant update device FC's.
Now, what IS interesting is that if I just flash the ROM and update-device.zip, o don't get the FCs. But as soon as I flash gapps, that's when things start to head south.
iamterence said:
Forgive my noobness, as I'm usually on point with this stuff, but how can I root WITH busybox? Would I need to boot up and then download the app from the store? Because if so, I can't get past the setup screen without constant update device FC's.
Now, what IS interesting is that if I just flash the ROM and update-device.zip, o don't get the FCs. But as soon as I flash gapps, that's when things start to head south.
Click to expand...
Click to collapse
Sorry maybe bad word placement on my part but had meant root the Rom and then install busybox which requires root. You should be able to download SuperSU and then flash it in recovery. Once SuperSU is installed can download busybox installer from playstore.
This is the version of SuperSU I have used the last few builds.
https://www.dropbox.com/s/1y5m5vvtp55o4f0/BETA-SuperSU-v2.44.zip?dl=0
Still may be hard if you are having FC issues on setup. I am honestly not an expert but would not think being on Sprint would cause FC issues but again I don’t really know. If you are experiencing FC issues would try a full wipe including data if not done so previously and install again. Not sure its the case but I first tried a dirty flash from 5.0 stock to an AOSP build and all my Google Apps which I believe set-up wizard is included but was OK for me would not work, Not the best solution but ended up un-installing and reinstalling all my Google Apps. After that everything was OK. Think the issue was caused by having flashed different versions of the Google Apps that did not vibe with the updates from the play store. After I dirty flashed again from 5.01 to 5.02 using same version of Gapps and did not have any issues. Not saying is the case but not doing a data wipe can cause some strange bugs not always seeming to be related to the bugs experienced. I once had an issue back in the days og GB that my wifi had stopped working. Had been on forums and bugging out for a few days and then for some unrelated reason wiped the MMS app data in application settings and performed a reboot. First thing I noticed was wifi was working. How bad data from the MMS app could have broke wifi is still an unsolved mystery but just to be sure restored a Nandroid with the bad wifi twice and was able to reproduce the fix both times by wiping MMS data.
Otherwise let me know if anyone else has experienced a FC during set-up but only if you have wiped the data partition. I have otherwise flashed about 15 times so far and have yet seen an app FC on me.
kowalsfee said:
The only thing bothers me is the aosp dialer icon, so anti-material, can someone solve that out?
Click to expand...
Click to collapse
Yeah not all of AOSP is Material. I myself after flashing download a root file explorer and remove the calendar, voice dialler, music and MSS apk's and then download Google Calender and the new Google Messenger apps from the play store. I also install the Google Calender and have been using Google Inbox in place of Gmail. Otherwise not much else from Google as I also have an N7 and N9 so in general keep the phone slim and load up the now N9. Was not a fan at first but now a days can no longer use the N7. Only thing about the N9 that still bugs me is they copied Apple with the 4:3 aspect ratio. Is awesome for old TV shows on Netflix but all others pretty much take the same space they would have on the N7 making the larger screen pretty much null and void. Otherwise had been pretty disappointed at first but has grown on me big time.
Added a bunch more updates. Still working on a fix for sprint users but have a good idea what needs to be done.
Also had added from Google a record bug report option with power off seems I forgot to remove before building but all it does is dump a bug-report in storage. Has no other effect. Otherwise smooth a butter and bug free.
Any chance for a Mako port? I have a Nexus 5 myself, but someone I know has a nexus 4 that's acting up (SoD) and so i thought that this might help them out.
I just flashed over to this ROM from stock 5.0.1 I am hoping that this build will fix the memory leak I've had on the official build. So far everything seems to work well except for the security settings. Anytime I try to open it settings simply force closes. Does anyone else have this issue? I usually use smart lock so I am sad to see this broken. I have a unlocked nexus 5 running on AT&T and I did a full wipe before flashing. I also flashed the recommended GApps package. Thanks in advance
Yeah thats my bad uploaded the wrong .zip including a stock file experementing for Sprint Users. Will recompile and post correct build. Everything else should be the same so once fix is posted should be ok to just wipe system & cache before install. Just need to also reflash same gapps package as before.
Also going to post manifest so can build for all Nexus devices. Can also build it special if needed. If you guys are seeing improvments with the Updates let me know and can start posting builds for all Nexus devices. I only have the 7 (2013), 9 and 5 for testing. I see a few big improvmets but curious what others think before starting to build for every Nexus. Know a few apps like messaging are still not material and was surprised to see old school Music first time building pure AOSP but wanted purity so have laft those things be.
Is r2 the release build with the Sprint fixes?

Categories

Resources