If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
one more benchmark after the tablet was stabilized for 2 minutes
Hello,
When first running the benchmark I did it as soon as I turned on the tablet, did not wait for it to stabilize. I just re-ran the benchmark after tablet was up for 5 minutes, (3 times total and the benchmark is consistently AnTuTU 21082.
Hello,
When first running the benchmark I did it as soon as I turned on the tablet, did not wait for it to stabilize. I just re-ran the benchmark after tablet was up for 5 minutes, (3 times total and the benchmark is consistently AnTuTU 21082.
Those features were removed from these Pipo firmware releases. Maybe they will put them back in, eventually.
Randy Freaktab Developer, Product Reviewer, Moderator and "Flashaholic". Read my BIO Here
Be sure to donate to support Freaktab.com. If any of my development work makes a positive difference for you, please make a donation to support future RileyROM's. Donate here
Hello - I just noticed the screen resolution is set at 1536 * 1952 Did you change the display settings?
Maybe that is why I'm getting such high AnTuTu results.
Regards Brian
the res is still 2048x1536, the presence of the bottom bar make antutu to recognize a little bit wrong value!
Great result for your tablet on antutu!
With the very low kernel you will notice the battery lasts a little bit more too.
Hello, Giouncino, try to use your kernel. But looks like just can use carlo. any trick to use any others. every time I flashed your kernel just can get dark screen when boot. stock one antutu mark lower than your carlo. But carlo sometimes the button will freaze for a second. strange?
After booting to recovery, without doing any wipes or changes, I was unable to reboot the system (rebooting ended with retuening to TWRP screen). Had to reflash the ROM.
Hello, Giouncino, try to use your kernel. But looks like just can use carlo. any trick to use any others. every time I flashed your kernel just can get dark screen when boot. stock one antutu mark lower than your carlo. But carlo sometimes the button will freaze for a second. strange?
Please help.
You have a "not lucky CPU" you need more voltage to get the CPU stable at higher frequency.
The temporaneous freeze I think is not due to the kernel, because if the kernel is not ok for you the tablet will totally freeze or reboot.
You can try the kernel with the RAM overclock only (it should be the "kimmen" version). Probably is better to have the CPU stock voltage/freq in your specific case.
After booting to recovery, without doing any wipes or changes, I was unable to reboot the system (rebooting ended with retuening to TWRP screen). Had to reflash the ROM.
you needed only the misc.img file.
You can find it in the specific thread.
After booting to recovery, without doing any wipes or changes, I was unable to reboot the system (rebooting ended with retuening to TWRP screen). Had to reflash the ROM.
Getting a few issues with google play store now since the update.
Whenever i try to download an app on the store im getting:
'Update for "Quickoffice" could not be downloaded due to an error. (403)'
Says this with any app.
Tried clearing the app cache, no joy.
Any ideas?
Thanks
Update:
I cant seem to fix this issue at all actually.
I had exactly the same problem this morning after loading RR 1.8 for the first time, searched the web and there doesn't seem to be a simple fix for this issue. It seems google are aware of the problem but haven't fixed yet.
I tried 2 different accounts and got the same result (both known good accounts)on the tablet.
Tried my phone with my usual account to see if that was affected and it worked when i tried to download something from play store (no 403 error),so i went back to the tablet tried again with the same account and it worked no errors and all seems to be working again.
sorry this isnt a difinitive answer but this what worked for me, I can share your pain
PS I didnt reflash rom it seems to be a google problem not rom problem.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment